Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca0555319321336712104!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Since we haven't hit 1.5.0 officially yet, and this isn't a release candidate, we need to call it 'beta'. Mostly to be clear to the users that it is unstable. I think it could be useful however to have a SNAPSHOT version of each new release, even if it is the same as the 'beta' or 'RC' version that was just released.
Brent Owens
(The Open Planning Project)
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Yeah, that's what I was figuring the answer was.
I am definitely +1 for moving to 1.5.<next-version-to-be-released>-SNAPSHOT in the svn repo, and then marking the releases with real version numbers (and tags in svn). This also seems to be what geotools does.
--saul
Justin Deoliveira wrote:
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
As long as the version numbers are there for the official releases, then yeh having -SNAPSHOT is a good idea.
We can of course keep the running version number in the web admin UI.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca0555319321336712104!
Yeah, this is the "standard practice" for maven projects. And from what I can tell you can setup the maven release plugin ( which we dont use ) to automate this for you. It used to be a bit flaky which is why we dont use it but i am pretty sure it is better now.
-Justin
Brent Owens wrote:
As long as the version numbers are there for the official releases, then yeh having -SNAPSHOT is a good idea.
We can of course keep the running version number in the web admin UI.Brent Owens
(The Open Planning Project)Justin Deoliveira wrote:
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca0e045701527717022!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Bah - when it is a mistake like this no need to vote 
Please just fix the problem (and thanks for the catch Saul). Justin you will find that Brent documented the release numbers to follow maven conventions a short time ago.
Cheers,
Jody
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca0555319321336712104!
Its not a mistake Jody. Its a choice between using a standard maven convention, or not using it. I don't see anywhere where it says that we can simply change anything in the project as long as its maven standard practice.
Jody Garnett wrote:
Bah - when it is a mistake like this no need to vote
Please just fix the problem (and thanks for the catch Saul). Justin you will find that Brent documented the release numbers to follow maven conventions a short time ago.
Cheers,
JodyGood point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca1da820711665516417!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Hi Justin.
Brent brought this up last year - and changed GeoServer conventions at the time to bring them in line with Maven. I could be wrong on this ... Brent?
Jody
Its not a mistake Jody. Its a choice between using a standard maven convention, or not using it. I don't see anywhere where it says that we can simply change anything in the project as long as its maven standard practice.
Jody Garnett wrote:
Bah - when it is a mistake like this no need to vote
Please just fix the problem (and thanks for the catch Saul). Justin you will find that Brent documented the release numbers to follow maven conventions a short time ago.
Cheers,
JodyGood point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca1da820711665516417!
It was discussed a bit, but we rejected some of the maven practices such as -M# (milestones), and decided to include 'beta'. But it wasn't very specific.
I think for official releases that go on the geoserver.org site we should not use Maven naming conventions, they make no sense to users. But for living in the repository it would be beneficial to have our intermediate versions be labeled SNAPSHOT (replacing beta and RC), and still have the real versions stick with their version names.
examples:
Download Maven
1.5.0-beta2 1.5.0-SNAPSHOT
1.5.0-rc1 1.5.0-SNAPSHOT
1.5.0 1.5.0
1.5.1 1.5.1
Brent Owens
(The Open Planning Project)
Jody Garnett wrote:
Hi Justin.
Brent brought this up last year - and changed GeoServer conventions at the time to bring them in line with Maven. I could be wrong on this ... Brent?
Jody
Its not a mistake Jody. Its a choice between using a standard maven convention, or not using it. I don't see anywhere where it says that we can simply change anything in the project as long as its maven standard practice.
Jody Garnett wrote:
Bah - when it is a mistake like this no need to vote
Please just fix the problem (and thanks for the catch Saul). Justin you will find that Brent documented the release numbers to follow maven conventions a short time ago.
Cheers,
Jody
Good point Saul.
Right now its not that important as no one really downloads geoserver libraries via maven. But as we move more toward a platform, people will.
I would be +1 for moving to 1.5.0-SNAPSHOT, and just setting the actual version numbers for release. We could do this pretty simply with a property in the pom.
-Justin
Saul Farber wrote:
Currently the 1.5.x branch is creating <version>1.5.0-beta2</version> as it's maven deployment version.
Should this be 1.5.0-SNAPSHOT? Or 1.5.x-SNAPSHOT? Or 1.5.1-SNAPSHOT? Or is it fine the way it is?
I know it got set to 1.5.0-beta2 when the beta2 release got cut, but isn't there some special meaning to the SNAPSHOT in the version? Doesn't it indicate to any projects which depend on geoserver that they should download the latest version always, rather than do a version check?
--saul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:1004,45ca1da820711665516417!
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
