Re: Wicketstuff core 1.4.0 release preparations
On Thu, Aug 13, 2009 at 8:46 PM, Erik van Oosten wrote: > Maarten, you just beated me to it. > > Is the jazzyplugin still needed after your changes? Hi Erik, I did not try to remove the dependency, so it's still needed. I just downloaded the jar and installed in my local maven repo. Maarten > > Regards, > Erik. > > > Erik van Oosten wrote: > >> Hi, >> >> Unfortunately tinymce does /not/ compile. It fails with a missing >> dependency to jazzyplugin:jazzyplugin:jar:0.2.1. >> >> Regards, >> Erik. >> >> > > -- > Erik van Oosten > http://www.day-to-day-stuff.blogspot.com/ > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wicketstuff core 1.4.0 release preparations
Maarten, you just beated me to it. Is the jazzyplugin still needed after your changes? Regards, Erik. Erik van Oosten wrote: Hi, Unfortunately tinymce does /not/ compile. It fails with a missing dependency to jazzyplugin:jazzyplugin:jar:0.2.1. Regards, Erik. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicketstuff core 1.4.0 release preparations
Hi, Unfortunately tinymce does /not/ compile. It fails with a missing dependency to jazzyplugin:jazzyplugin:jar:0.2.1. Regards, Erik. Jeremy Thomerson wrote: To those who have written me volunteering to help: thank you. I will try to do the release this weekend. Here's what you can do to help before then. 1 - check out wicketstuff-core trunk 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only do this locally - don't commit that change - since trunk should run on trunk) 3 - build it to make sure it all works 4 - test the release process by doing following: mvn release:prepare -DdryRun=true If all of that is working fine (no build errors, etc), then let the list know. That will make it much easier to do the release. And I'll try to document the process so that someone else can perform the next one easier. -- Jeremy Thomerson http://www.wickettraining.com -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Yes, that did it. Running the dryRun in wicket-stuff/wicketstuff-core/yui-parent/yui succeeds. I repeated this for yui-examples. yui-parent, yui and yui-examples are ready to go! Regards, Erik. Erik van Oosten wrote: There is actually one more thing I could have tried: execute the release:prepare goals in de yui sub-sub modules. Igor Vaynberg wrote: mvn clean package release:prepare -DdryRun=true -igor On Thu, Aug 13, 2009 at 8:33 AM, Erik van Oosten wrote: Hi Jeremy, I am afraid I do not understand what to do. I set out to test the yui-parent module: I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah! However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent sub-directory just downloads a yui snapshot instead of compiling it localy. Running it one directory up fails because prepare:release does not accept diffs with the SCM and I changed the wicketstuff-code pom (I commented out all modules except for yui-parent). What else can I do? Or must one do the whole thing at once? BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT? Regards, Erik. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
Igor, release:prepare automatically also does clean and package. There is actually one more thing I could have tried: execute the release:prepare goals in de yui sub-sub modules. Regards, Erik. Igor Vaynberg wrote: mvn clean package release:prepare -DdryRun=true -igor On Thu, Aug 13, 2009 at 8:33 AM, Erik van Oosten wrote: Hi Jeremy, I am afraid I do not understand what to do. I set out to test the yui-parent module: I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah! However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent sub-directory just downloads a yui snapshot instead of compiling it localy. Running it one directory up fails because prepare:release does not accept diffs with the SCM and I changed the wicketstuff-code pom (I commented out all modules except for yui-parent). What else can I do? Or must one do the whole thing at once? BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT? Regards, Erik. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
mvn clean package release:prepare -DdryRun=true -igor On Thu, Aug 13, 2009 at 8:33 AM, Erik van Oosten wrote: > Hi Jeremy, > > I am afraid I do not understand what to do. I set out to test the yui-parent > module: > > I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah! > > However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent > sub-directory just downloads a yui snapshot instead of compiling it localy. > Running it one directory up fails because prepare:release does not accept > diffs with the SCM and I changed the wicketstuff-code pom (I commented out > all modules except for yui-parent). > > What else can I do? Or must one do the whole thing at once? > > BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT? > > Regards, > Erik. > > > > Jeremy Thomerson wrote: >> >> To those who have written me volunteering to help: thank you. I will >> try to do the release this weekend. Here's what you can do to help >> before then. >> >> 1 - check out wicketstuff-core trunk >> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only >> do this locally - don't commit that change - since trunk should run on >> trunk) >> 3 - build it to make sure it all works >> 4 - test the release process by doing following: >> >> mvn release:prepare -DdryRun=true >> >> If all of that is working fine (no build errors, etc), then let the >> list know. That will make it much easier to do the release. And I'll >> try to document the process so that someone else can perform the next >> one easier. >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff core 1.4.0 release preparations
The release:prepare will also check if there are no SNAPSHOT dependencies IIRC, or turn them into timestamped dependencies. If mvn install works, then yui-parent is good to go I think. Martijn On Thu, Aug 13, 2009 at 5:33 PM, Erik van Oosten wrote: > Hi Jeremy, > > I am afraid I do not understand what to do. I set out to test the yui-parent > module: > > I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah! > > However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent > sub-directory just downloads a yui snapshot instead of compiling it localy. > Running it one directory up fails because prepare:release does not accept > diffs with the SCM and I changed the wicketstuff-code pom (I commented out > all modules except for yui-parent). > > What else can I do? Or must one do the whole thing at once? > > BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT? > > Regards, > Erik. > > > > Jeremy Thomerson wrote: >> >> To those who have written me volunteering to help: thank you. I will >> try to do the release this weekend. Here's what you can do to help >> before then. >> >> 1 - check out wicketstuff-core trunk >> 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only >> do this locally - don't commit that change - since trunk should run on >> trunk) >> 3 - build it to make sure it all works >> 4 - test the release process by doing following: >> >> mvn release:prepare -DdryRun=true >> >> If all of that is working fine (no build errors, etc), then let the >> list know. That will make it much easier to do the release. And I'll >> try to document the process so that someone else can perform the next >> one easier. >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicketstuff core 1.4.0 release preparations
Hi Jeremy, I am afraid I do not understand what to do. I set out to test the yui-parent module: I can confirm that /yui-parent/ builds fine (with +mvn install+). Yeah! However, +mvn release:prepare -DdryRun=true+ executed in the yui-parent sub-directory just downloads a yui snapshot instead of compiling it localy. Running it one directory up fails because prepare:release does not accept diffs with the SCM and I changed the wicketstuff-code pom (I commented out all modules except for yui-parent). What else can I do? Or must one do the whole thing at once? BTW, should wicketstuff-core not change from 1.4-SNAPSHOT to 1.4.0-SNAPSHOT? Regards, Erik. Jeremy Thomerson wrote: To those who have written me volunteering to help: thank you. I will try to do the release this weekend. Here's what you can do to help before then. 1 - check out wicketstuff-core trunk 2 - change the wicket dependencies from snapshot to 1.4.0 (note: only do this locally - don't commit that change - since trunk should run on trunk) 3 - build it to make sure it all works 4 - test the release process by doing following: mvn release:prepare -DdryRun=true If all of that is working fine (no build errors, etc), then let the list know. That will make it much easier to do the release. And I'll try to document the process so that someone else can perform the next one easier. -- Jeremy Thomerson http://www.wickettraining.com -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org