On 04/27/2015 09:40 AM, Jacques Le Roux wrote:
You can already compile components separately by using the specific
build files
Yeah, I know, and it's a pain in my side. I actually like being able to
*compile* each component separately, by changing to that folder, and
running ant. I haven't yet been able to get maven to make that possible.
What I think Ron meant, is that it'd be nice to be able to checkout out
*just* one component, and have all it's
dependants(jars/other-components) downloaded automatically. Then, work
can be done on *just* this component, in isolation. For this, maven
works great.
ps: Note Ron's phrase of "breaking the project up".
pps: But, even then, other projects have multiple released artifacts per
checkout, so maybe all of framework is one repo, and each
application/specialpurpose/hot-deploy component becomes separate.
Jacques
Le 24/04/2015 06:26, Ron Wheeler a écrit :
+1
Any change of breaking the project up into components that are
compiled separately?
Ron
On 23/04/2015 11:42 PM, Scott Gray wrote:
+1
Regards
Scott
On 21 January 2015 at 00:41, Jacopo Cappellato <
jacopo.cappell...@hotwaxmedia.com> wrote:
In my opinion it would be nice to review how we organize the code
in our
components and switch to a directory layout that is more inline
with what
other projects are doing, for example:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
More specifically I would like to switch from, for example:
script/org/ofbiz/product/
src/org/ofbiz/product/
src/org/ofbiz/product/test/
to:
src/main/java/org/ofbiz/product/
src/main/minilang/org/ofbiz/product/
src/main/groovy/...
src/test/java/org/ofbiz/product/
What do you think?
Jacopo
