While I'm certainly in favor of going back to an ant-based build
system, another solution to this problem might be hardcoding specific
plugin versions in maven as stated by Dain.
On 3/14/07, Andrus Adamchik <andru..bjectstyle.org> wrote:
> I'll try to find time this weekend and revert the build system to Ant
> (based on 2.0 but following the new project structure). If I can do
> it in two days, then bye-bye Maven. Later we can improve it with Ivy,
> etc. For now I am planning manual dependency handling.
> One question though - are we allowed to have LGPL dependencies in
> SVN, if we don't release them? Anyone knows that?
> On Mar 13, 2007, at 11:59 PM, Aristedes Maniatis wrote:
> > On 14/03/2007, at 5:21 AM, Andrus Adamchik wrote:
> >> While I am on that pessimistic Maven rant ... Continuous
> >> integration (the maven way) somehow includes the underlying build
> >> system made of dozens of plugins constantly updated by multiple
> >> third parties. Maybe we should revert to Ant ?
> > Firstly, I found this: https://maven-repository-
> > importer.dev.java.net/source/browse/*checkout*/maven-repository-
> > importer/maven-repository-importer/doc/index.html
> > This is a plugin which supposedly makes it easy to publish to maven
> > repositories from ant. But I haven't tried it, so I don't know how
> > workable it is.
> > Secondly, Cayenne dependencies are pretty simple aren't they? Is it
> > as simple as having a /lib folder and a VERSIONS.txt file which
> > tracks what version of each lib we are using? Or is there something
> > more complex involved here? If so, I've ready some nice things
> > about the Apache Ivy project for dependency management in ant.
> > Ari
> > -------------------------->
> > Aristedes Maniatis
> > phone +61 2 9660 9700
> > PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
This archive was generated by hypermail 2.0.0 : Wed Mar 14 2007 - 12:28:32 EDT