I'd like to keep them as well, for the following reasons: a) Until last week: maven setup from scratch required the developer to copy half a dozen of libraries into the local maven repo because maven did not find them in the repo configured. I copied them from /lib into the local repo..
b) I use maven only to do *final* validation and to create a wicket-snapshot.jar to be used in the examples e.g.. Until this final validation I develop everything in Eclipse (others may use Idea). Not having the lib-directory means that the eclipse project is no longer self-contained, as the libs must now be configured to be from maven-repo.. That means, that every developer downloading Wicket has first to modify his eclipse project settings to fit to his local maven repo (which he might not have or even want because he is using ant). This is another hurdle, which I think, we should not impose. Juergen On Sun, 19 Dec 2004 18:00:27 -0800, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > i hear your arguments and agree with them in the abstract. however, i > really dislike the idea of making wicket dependent on installing maven > if we can prebuild things so they work with ant. 99% of java developers > know ant and have it installed. it may be the best tool in the world, > but maven is not ubiquitous and we'll definitely lose some portion of > our audience if we require maven to build. can we have some compromise > like rigging the ant script so that the default build target will use > maven if it's installed to drag down new libs, but have everything still > work by default? > > Martijn Dashorst wrote: > > > Hi, > > > > I wanted to stir up a discussion on the committing of dependend > > libraries in CVS. Currently all projects have their dependencies (i.e. > > concurrent.jar, etc.) also in the lib directory in CVS. I consider > > this to be wrong. This is not necessary for building a release, nor > > building wicket. Maven is *the* build tool of choice to build wicket > > (and/or its sub projects) from CVS. When releasing wicket into a ZIP > > file, the libraries are included using a maven script which will copy > > all relevant jars from the local maven repository into the lib folder. > > This ensures that the dependencies are always in par with the > > documented dependencies. > > > > Why am I opposed to putting the dependencies also in CVS? because it > > creates an additional burden on keeping these libraries in synch with > > the project.xml. When a library (for instance wicket-xxx.jar) is > > upgraded in the project.xml when performing a release, the > > releasemanager has to keep track of the lib directory as well. This is > > not good, as many errors can be made in the process. > > > > I urge all project maintainers to remove the lib directories from CVS > > and to keep it that way. > > > > There is 1 exception to this rule: clover, as it is a special library > > with a license included, which can not be obtained through the default > > maven repository. > > > > With regards, > > > > Martijn Dashorst > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > Wicket-develop mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Wicket-develop mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
