For a newcomer (and us), building FraSCAti is currently the most cumbersome step of building EasySOA, see tdelprat's experience at #80 & #87 "Improve build system".
See current problems and workarounds at https://github.com/easysoa/EasySOA/wiki/Building-easysoa and https://github.com/easysoa/EasySOA/wiki/Releasing-EasySOA .
EasySOA currently relies on FraSCAti's latest development version to benefit quickly from new INRIA patches and improvements. Main problems are :
1. FraSCAti maven repositories cleanup
Cleaning up FraSCAti build by putting as much as possible dependencies in a "good" maven repository, Sonatype's Central if possible (or OW2 but that would go against Maven good practice), especially old / unmaintaned ones like OpenArchitectureWare's
2. providing nightly builds.
(note that it doesn't solve transitive dependencies though, see above)
That could be done using FraSCAti CI (http://bamboo.ow2.org/browse/SCA) and a snapshot repository. Possible snapshots repository are :
3. smaller EasySOA-targeted FraSCAti build
going further towards having a smaller EasySOA-targeted FraSCAti build with only things (repositories, artifacts) we require :
- no petals,
- no OAW if possible.
This can be done by a separate build, a maven profile, or further rethinking the top of the FraSCAti build.
Note that having our own bootstrap - WebExplorer's actually - already goes this way, as does the long term goals of making FraSCAti more modular.
For a newcomer (and us), building FraSCAti is currently the most cumbersome step of building EasySOA, see tdelprat's experience at #80 & #87 "Improve build system".
See current problems and workarounds at https://github.com/easysoa/EasySOA/wiki/Building-easysoa and https://github.com/easysoa/EasySOA/wiki/Releasing-EasySOA .
EasySOA currently relies on FraSCAti's latest development version to benefit quickly from new INRIA patches and improvements. Main problems are :
LATER Another related topic : making Fractal build easier.
What are INRIA's ideas ? Here are mine :
1. FraSCAti maven repositories cleanup
Cleaning up FraSCAti build by putting as much as possible dependencies in a "good" maven repository, Sonatype's Central if possible (or OW2 but that would go against Maven good practice), especially old / unmaintaned ones like OpenArchitectureWare's
2. providing nightly builds.
(note that it doesn't solve transitive dependencies though, see above)
That could be done using FraSCAti CI (http://bamboo.ow2.org/browse/SCA) and a snapshot repository. Possible snapshots repository are :
3. smaller EasySOA-targeted FraSCAti build
going further towards having a smaller EasySOA-targeted FraSCAti build with only things (repositories, artifacts) we require :
This can be done by a separate build, a maven profile, or further rethinking the top of the FraSCAti build.
Note that having our own bootstrap - WebExplorer's actually - already goes this way, as does the long term goals of making FraSCAti more modular.