-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.
johanOn 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
