Re: [VOTE] All examples in one project, Java 5 required
Martijn Dashorst wrote: I propose to make the examples projects Java 1.5 dependent. Everyone said yes, so I assume this is going ahead. Has there been any progress on this? I'm wanting to fiddle with Maven 2 build procedures and things prior to getting the 1.3 beta out, and if you have tons of outstanding commits with this, it may be tricky. :-) Al
Re: [VOTE] All examples in one project, Java 5 required
This is one for after the current release... Putting them into one project and making it beautiful just takes longer. Will be ready for final I hope. Martijn On 3/8/07, Al Maw [EMAIL PROTECTED] wrote: Martijn Dashorst wrote: I propose to make the examples projects Java 1.5 dependent. Everyone said yes, so I assume this is going ahead. Has there been any progress on this? I'm wanting to fiddle with Maven 2 build procedures and things prior to getting the 1.3 beta out, and if you have tons of outstanding commits with this, it may be tricky. :-) Al -- 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
Re: [VOTE] All examples in one project, Java 5 required
Martijn Dashorst wrote: [ ] No, I object! Java 1.4 examples are the thing I live and die for [X] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Al
[VOTE] All examples in one project, Java 5 required
This is a vote that I came to after some long hard thinking. Our examples projects have grown and put a burden on the release procedure. We already discussed merging them into one project and iirc the concensus was to make it so. The problem lies with the Wicket 1.x branch where we have Java 1.4 projects and Java 1.5 projects. In order to stop the proliferation of the examples projects *and* avoid a split into a Java 1.4 and Java 1.5 examples project, I propose to make the examples projects Java 1.5 dependent. This doesn't mean that Wicket, Wicket Spring and Wicket extensions become Java 5 dependent, only the one examples project that rules them all (insert evil laughter here). [ ] No, I object! Java 1.4 examples are the thing I live and die for [ ] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Martijn -- 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
Re: [VOTE] All examples in one project, Java 5 required
(non-binding) [ ] No, I object! Java 1.4 examples are the thing I live and die for [x] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/
RE: [VOTE] All examples in one project, Java 5 required
[ ] No, I object! Java 1.4 examples are the thing I live and die for [x] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Stefan Lindner
Re: [VOTE] All examples in one project, Java 5 required
everyone can test on java5 to look how it works so that shouldn't be any problem: +1 for java5 On 2/27/07, Martijn Dashorst [EMAIL PROTECTED] wrote: This is a vote that I came to after some long hard thinking. Our examples projects have grown and put a burden on the release procedure. We already discussed merging them into one project and iirc the concensus was to make it so. The problem lies with the Wicket 1.x branch where we have Java 1.4 projects and Java 1.5 projects. In order to stop the proliferation of the examples projects *and* avoid a split into a Java 1.4 and Java 1.5 examples project, I propose to make the examples projects Java 1.5 dependent. This doesn't mean that Wicket, Wicket Spring and Wicket extensions become Java 5 dependent, only the one examples project that rules them all (insert evil laughter here). [ ] No, I object! Java 1.4 examples are the thing I live and die for [ ] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Martijn -- 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
Re: [VOTE] All examples in one project, Java 5 required
Martijn Dashorst wrote: This is a vote that I came to after some long hard thinking. Our examples projects have grown and put a burden on the release procedure. We already discussed merging them into one project and iirc the concensus was to make it so. The problem lies with the Wicket 1.x branch where we have Java 1.4 projects and Java 1.5 projects. In order to stop the proliferation of the examples projects *and* avoid a split into a Java 1.4 and Java 1.5 examples project, I propose to make the examples projects Java 1.5 dependent. This doesn't mean that Wicket, Wicket Spring and Wicket extensions become Java 5 dependent, only the one examples project that rules them all (insert evil laughter here). [ ] No, I object! Java 1.4 examples are the thing I live and die for [ ] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Is it possible to have some kind of annotation as to whether a specific sample might expect to work on 1.4/1.5? Otherwise, folks might waste time on 1.5 only projects when they have a 1.4 dependency. Needn't be anything more than a note on the web pages themselves. Regards, Upayavira
Re: [VOTE] All examples in one project, Java 5 required
[ ] No, I object! Java 1.4 examples are the thing I live and die for [X] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
Re: [VOTE] All examples in one project, Java 5 required
[ x ] Yes, make one examples project to rule them all, and by all means, make it Java 1.5 dependent Eelco
