I agree with you.
I have already committed to bilingualism in my development and system
administration processes.
Once we get through this discussion, I might put out an argument for an
installer like IzPack that can make deployment into different
environments with the appropriate seed data loaded a bit less
transparent and more user friendly.
Ron
On 28/04/2015 12:45 PM, Jacques Le Roux wrote:
Le 28/04/2015 15:22, Ron Wheeler a écrit :
On 28/04/2015 3:31 AM, Jacques Le Roux wrote:
Le 27/04/2015 16:52, Adam Heath a écrit :
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.
Yikes, that would be a Maven only solution (no Ant) blocker :/
Jacques
Why would Ant have trouble with a different project structure?
No I meant if ever we would head to Maven only (no Ant build in the
project) then it would be a blocker.
Ant is the ultimate in flexibility.
The change will affect the existing Ant processes but I find it hard
to imagine how it would prevent Ant from building OFBiz.
I would be tempted to look at providing alternative Ant builds.
I'm undecided on this, but it seems redundant to me and duplicate to
maintain.
It might be nice to have a simple final assemble with Ant that pulls
jar files from Maven Central and uses these jars to build OFBiz
http://andreafrancia.it/2010/04/how-to-download-from-jars-from-mavencentral-with-ant-without-ivy.html
This is interesting, now I wonder if Jacopo still think the same than
at
https://issues.apache.org/jira/browse/OFBIZ-5464?focusedCommentId=13947664
Having Ant scripts that build individual components or groups of
components should be pretty simple.
That exists already
It is also possible to deploy artifacts built with Ant to Maven Central.
http://central.sonatype.org/pages/apache-ant.html
I don't see Ant support as a difficult part of a move to Maven but if
there is a real demand to support the use of Ant for 100% of the
development tasks, it can be part of the move to Maven and any
reorganization of the applications.
This will require a high level of cooperation between the experts in
the Ant build scripts and the experts promoting Maven.
I think, if ever we go the Maven way, we will still need Ant around
and ready
Jacques
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
