afair the release plugin tags/branches each project separately. This is not good imo. We don't release each project separate, but the whole branch in one go. I've used the release plugin in the maven 1 days and it was nothing but a big pain in the rectum.
Why is the root pom version 1-SNAPSHOT and the jdk* poms 1-3-incubating-SNAPSHOT? Can't we just put the version in the root pom and be done with that? Another thing I want to remove from the pom's are the contributor, developer list. These are rather dynamic and don't add much. The poms don't need to change and be released when these things are modified. Last thing for the moment: inherit the top parent from org.apache/apache/4.0, this way you get the organization and some other things for free. Martijn On 3/8/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
How does the nested projects work with Eclipse? afaiu eclipse's workspace needs to be a flat structure... Martijn On 3/8/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > <AlMaw> svn checkout > https://svn.apache.org/repos/asf/incubator/wicket/branches/al-test-wicket-1.3.x > <AlMaw> cd al-test-wicket-1.3.x > <AlMaw> mvn install > <AlMaw> Done. > <AlMaw> In theory, we should be able to go: > <AlMaw> cd jdk-1.4 > <AlMaw> mvn release:prepare > <AlMaw> ... > <AlMaw> mvn release:perform > <AlMaw> cd ../jdk-1.5 > <AlMaw> mvn release:prepare > <AlMaw> ... > <AlMaw> mvn release:perform > <AlMaw> And we'll be done. > <AlMaw> It'll need a little tweaking. > <AlMaw> And you'll probably want to run the jdk-1.4 stuff using a 1.4 JDK. > <AlMaw> But check out how much neater the poms all are. > -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
-- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
