Hi,
since restlet is becoming popular in geoserver, what about moving
the dependency versions to the root pom, along with the repository
declaration?
Moreover, what about upgrading from 1.0.5 to 1.0.8?
Cheers
Andrea
Hi,
since restlet is becoming popular in geoserver, what about moving
the dependency versions to the root pom, along with the repository
declaration?
Moreover, what about upgrading from 1.0.5 to 1.0.8?
Cheers
Andrea
+1 from me. While we are at it how about moving all the individual geoserver module versions to the root pom as well. This would save use having to specify the version in all dependencies.
Andrea Aime wrote:
Hi,
since restlet is becoming popular in geoserver, what about moving
the dependency versions to the root pom, along with the repository
declaration?Moreover, what about upgrading from 1.0.5 to 1.0.8?
Cheers
Andrea-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47f49e74246381804284693!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira ha scritto:
+1 from me. While we are at it how about moving all the individual geoserver module versions to the root pom as well. This would save use having to specify the version in all dependencies.
Hum, that looks like a good idea.
Maybe make it so that the dependency management uses ${project.version},
this way you don't have to update the values there either (when switching versions for a release, that is).
Cheers
Andrea
Thats the plan, less version numbers to change :).
Andrea Aime wrote:
Justin Deoliveira ha scritto:
+1 from me. While we are at it how about moving all the individual geoserver module versions to the root pom as well. This would save use having to specify the version in all dependencies.
Hum, that looks like a good idea.
Maybe make it so that the dependency management uses ${project.version},
this way you don't have to update the values there either (when switching versions for a release, that is).Cheers
Andrea-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47f4fb2972772085621377!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com