See this Stack Overflow answer for more information why using RELEASE
is bad, and for better alternatives:
http://stackoverflow.com/a/1172371
On Wed, Apr 30, 2014 at 10:39 AM, Rob Audenaerde
rob.audenae...@gmail.com wrote:
Is there a reason why 7.0.0.-M1 is used as RELEASE? I use
Is there a reason why 7.0.0.-M1 is used as RELEASE? I use
versionRELEASE/version to get released version as soon as possible, but
M1 somewhat feels like an RC.. ?
On Tue, Apr 29, 2014 at 10:22 PM, Martin Grigorov mgrigo...@apache.orgwrote:
I've renamed version 7.0.0 to 7.0.0-M1.
It will be
First of all, M1 is a milestone release, not a release candidate.
Second of all, we need to provide releases to a larger community to
ensure our ideas for 7.x are solid before we can finalise our API.
I have no idea what RELEASE means. If it is use the latest released
version then I think you set
probably a good idea... Does that make it more difficult to track what
went into 7.0 as a whole? Or do we collapse m1-mX when 7.0 goes final?
Martijn
On Sun, Apr 27, 2014 at 8:15 PM, Martin Grigorov mgrigo...@apache.org wrote:
Should we change the Fix version from 7.0.0 to 7.0.0-M1 for better
+1
On Sun, Apr 20, 2014 at 10:44 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
WOW. This is the first of many votes to come for our first Wicket 7
release train. It took some work, but I managed to manipulate our
projects, Maven and its release plugin to generate the right release
Our first 7.0 milestone can be released... thanks for voting!
Martijn
On Tue, Apr 29, 2014 at 8:59 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
+1
On Sun, Apr 20, 2014 at 10:44 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
WOW. This is the first of many votes to come for
We need one more binding +1 vote to pass or a -1 with a reason why to fail
the release.
Please vote!
Martin Grigorov
Wicket Training and Consulting
On Wed, Apr 23, 2014 at 11:37 PM, Martin Grigorov mgrigo...@apache.orgwrote:
+1 to release
tested:
- build from source (mvn clean install)
-
+1 if the problem with demo application has been solved.
We need one more binding +1 vote to pass or a -1 with a reason why to fail
the release.
Please vote!
Martin Grigorov
Wicket Training and Consulting
On Wed, Apr 23, 2014 at 11:37 PM, Martin Grigorov mgrigo...@apache.orgwrote:
+1 to
Yes, it does - https://issues.apache.org/jira/browse/WICKET-5572
But the fix will be in the next release
Martin Grigorov
Wicket Training and Consulting
On Sun, Apr 27, 2014 at 8:42 PM, Andrea Del Bene an.delb...@gmail.comwrote:
+1 if the problem with demo application has been solved.
We
+1 to release
Yes, it does - https://issues.apache.org/jira/browse/WICKET-5572
But the fix will be in the next release
Martin Grigorov
Wicket Training and Consulting
On Sun, Apr 27, 2014 at 8:42 PM, Andrea Del Bene an.delb...@gmail.comwrote:
+1 if the problem with demo application has been
Should we change the Fix version from 7.0.0 to 7.0.0-M1 for better
tracking what will be in the next release ?
Martin Grigorov
Wicket Training and Consulting
On Sun, Apr 27, 2014 at 9:13 PM, Andrea Del Bene an.delb...@gmail.comwrote:
+1 to release
Yes, it does -
+1 to release
tested:
- build from source (mvn clean install)
- random wicket-examples
- run grunt to test the JS
- wicketstuff (mvn clean test)
- wicket-bootstrap
-- mvn clean install PASSES
-- the demo application fails with:
java.lang.IllegalStateException
at
+1 to release
-igor
On Sun, Apr 20, 2014 at 1:44 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
WOW. This is the first of many votes to come for our first Wicket 7
release train. It took some work, but I managed to manipulate our
projects, Maven and its release plugin to generate the
WOW. This is the first of many votes to come for our first Wicket 7
release train. It took some work, but I managed to manipulate our
projects, Maven and its release plugin to generate the right release
version numbers for the right projects.
Known issue:
Wicket Atmosphere version mismatch
14 matches
Mail list logo
