I'm somewhere in the middle. There is something to say for [a] as long as we let sourceforge move them and not loose too much history, though I think I agree with Laurent ([b]) that if we are not complient, the only thing we probably have to do is to set those dirs in a properties file or however that works in maven 2.
Currently slightly in favor of [b] as that seems the easiest, immediate solution. Eelco On 12/19/05, Laurent PETIT <[EMAIL PROTECTED]> wrote: > I know I'm not a core dev so this poll may not concern me, but as a > both a wicket "client" and a maven user, please note what I think : > > [X] b. Try to create custom maven build and keep directories as they are > > Following the dirs convention names has never been a maven > requirement. Maven is supple enough to adapt to particular dirs > schemes. > > It is -to me- much more important to ensure a good versioning history > from cvs than to move 4 directories in order to avoid the writing of > some lines of code in the pom.xml. > ( note that if the scm had been svn instead of cvs, I would not have > made the same answer) > > The directory scheme adopted by the maven team is good enough, even if > it does not anymore comply with the *new defaults* suggested by the > maven team. > > My 0.02 EUR, :-) > > -- > Laurent > > > On 12/18/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > [a] lets become compliant with maven reqs if we are going to use it. > > > > -Igor > > > > > > On 12/18/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > +1 on what the build will make easier. Moving (the cvs dirs itself on the > > server) is one time a bit of pain but not to hard. > > > > > > johan > > > > > > > > > > > > > > > On 12/18/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > All, > > > > > > > > In order to comply with maven 2 standards, we should move some > > directories around. I want to do this through a sourceforge ticket, but the > > timing is not known in advance. So here's the deal: > > > > > > > > from to > > > > src/java src/main/java > > > > src/test src/test/java > > > > src/xdocs src/site/templates or > > src/site/resources > > > > xdocs src/site/xdoc > > > > > > > > I'd like to propose a vote for this... > > > > > > > > [ ] a. Move these directories and become 'maven compliant' > > > > [ ] b. Try to create custom maven build and keep directories as they are > > > > [ ] c. Other option? > > > > > > > > Another question to ask is: should we provide maven 1 support after we > > have moved to maven 2? > > > > > > > > BTW moving the directories ourselves is not an option: CVS then keeps > > track of these files in attic directories, which will always be queried when > > updating, thus slowing cvs down. Furthermore, we'd loose all versioning > > information (logs, revisions, etc) when we do it ourselves. > > > > > > > > Martijn > > > > > > > > -- > > > > Living a wicket life... > > > > > > > > Martijn Dashorst - http://www.jroller.com/page/dashorst > > > > > > > > Wicket 1.1 is out: > > http://wicket.sourceforge.net/wicket-1.1 > > > > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&opclick > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
