Maven would be much better, but the compiler uses some JARs which are probably
not available in public repositories.
Maven's "coolest" feature is it's weakest link.
In my experience the dependencies of a project almost always end up
being unorthodox.
Say there is one nasty bug in some lib which you fix in your own copy
but maybe the project is not accepting your update (the project might be
dead and there is nobody updating). Or it might take a year for the
update to be published or most likely you don't have the time to share
your update upstream.
That's why it's best to stick with your own local copies of dependencies.
But what I think might be a good thing is dependency management in general.
And there is a separate project for that in apache called ivy.
Also I quess maven can be used without resorting to public dependency
repositories.
I am not sure because I have my own personal build system (for better
AND worse).
- rami
On Jan 21, 2010, at 4:15 AM, Max Carlson wrote:
+1 from me. Anything we can do to use more modern libraries is a win. It would
be even better if we could switch to Maven and take advantage of the sweet
automatic JAR dependency management - but that's a much larger job.
Regards,
Max Carlson
OpenLaszlo.org
On 1/20/10 6:45 PM, P T Withington wrote:
I have a nifty solution for http://jira.openlaszlo.org/jira/browse/LPP-8503 but
it depends on updating our ant, rhino, and bsf versions and adding
commons-logging to our ant/lib/ jars.
I need to run:
Apache Ant version 1.6.5
Rhino 1.7 release 2
and update bsf.jar to 2.4.0, which requires adding commons-logging.jar 1.1.1
Is this going to be a problem for developers?
In theory these are all fairly stable publicly available tools, so there should
not be an issue with updating our dependencies, but I thought I should check
before I do.
