Thanks people, I guess the issues that some of us have raised are valid enough
to drop this proposal. I’ll see if somehow we can fix our packaging to
automatically accommodate changes in version string without dropping -SNAPSHOT.
Regards.
On 28-Oct-2014, at 5:18 am, David Nalley da...@gnsa.us
Hi Hugo and Nate,
I look forward to your comments on my replies on this thread. If we’re in
agreement, I would like to start a voting thread.
Regards.
On 23-Oct-2014, at 3:03 pm, Hugo Trippaers h...@trippaers.nl wrote:
I’m -1 on dropping the SNAPSHOT tag.
Snapshots are an integral part of
Sorry for not responding sooner, I took a few days off to lay 300 sqft of
tile.
I have a local Artifactory server that I'm publishing to based on builds
that are triggered from key branches in the ACS repo. I'm not using
something that is publicly available. For CCP, it is primarily the same
We used to publish snapshots to https://repository.apache.org for much
that same reason:
i.e:
https://repository.apache.org/service/local/repo_groups/snapshots-group/content/org/apache/cloudstack/cloud-console-proxy/4.1.0-SNAPSHOT/cloud-console-proxy-4.1.0-20130125.154919-473.jar
However, we
Hi,
On 22-Oct-2014, at 7:12 pm, Pierre-Luc Dion pd...@cloudops.com wrote:
Does packages from j.bac.o will have a -SNAPSHOT or -date suffix in
packages and acs version from the API ?
If you add -SNAPSHOT, -date or any suffix it will be packages names (the
deb/rpm file etc) but no in
I’m -1 on dropping the SNAPSHOT tag.
Snapshots are an integral part of maven building the project. A snapshot is
mavens way of telling that a particular release is still in development and
causes different behavior in how it resolves artifacts. For a developer working
only local the problem
Hi Hugo,
On 23-Oct-2014, at 3:03 pm, Hugo Trippaers h...@trippaers.nl wrote:
Snapshots are an integral part of maven building the project. A snapshot is
mavens way of telling that a particular release is still in development and
causes different behavior in how it resolves artifacts. For a
The jars are used when developing plugins outside of the core repo. My
company develops plugins which are self contained jars for our customers.
We do this without modifying the core code so that we aren't forking ACS in
the process and to support CCP. So while Apache doesn't ship shared library
Hi Nate,
On 24-Oct-2014, at 2:28 am, Nate Gordon nate.gor...@appcore.com wrote:
The jars are used when developing plugins outside of the core repo. My
company develops plugins which are self contained jars for our customers.
We do this without modifying the core code so that we aren't
Rohit,
Does packages from j.bac.o will have a -SNAPSHOT or -date suffix in
packages and acs version from the API ? I don't think the suffix addition
should be to user discretion but be there by default when using documented
build procedure. also, if I compare to lot of other free software dev,
Rohit, I would much prefer something like Nate suggestions, at least when
working with cloudstack build from git source is easy to know using the
cloudstack version api call and rpm packages name.
Rohit, just be sure, what you are suggesting is ,as example, for branch 4.5
until 4.5.0 is GA, the
Unfortunately maven's concept of multi-module projects requires that the
sub projects define the version of the parent that they want. So it is
scattered throughout all the pom files, but there is a handy maven plugin
that can update them all for you. I think the bigger problem is around the
os
Hi,
On 21-Oct-2014, at 9:40 pm, Nate Gordon nate.gor...@appcore.com wrote:
Unfortunately maven's concept of multi-module projects requires that the
sub projects define the version of the parent that they want. So it is
scattered throughout all the pom files, but there is a handy maven plugin
Hi,
Background:
Whenever we start on a new release and cut its release branch, for example 4.5
branch, we add the -SNAPSHOT string to the version string in pom.xmls,
debian/changelog and elsewhere. Just this mere action adds a divergence between
release and master branches and between two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/2014 12:33 PM, Rohit Yadav wrote:
Hi,
Background:
Whenever we start on a new release and cut its release branch, for
example 4.5 branch, we add the -SNAPSHOT string to the version
string in pom.xmls, debian/changelog and elsewhere.
+1 as well
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Wido den Hollander w...@widodh.nl
To: dev@cloudstack.apache.org
Sent: Monday, 20 October, 2014 11:35:14
Subject: Re: [PROPOSAL] Remove SNAPSHOT from versioning and keep tags
On Oct 20, 2014, at 12:35 PM, Wido den Hollander w...@widodh.nl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/2014 12:33 PM, Rohit Yadav wrote:
Hi,
Background:
Whenever we start on a new release and cut its release branch, for
example 4.5 branch, we add the -SNAPSHOT
When working with multiple environments with various installation of
Cloudstack (in labs) the -SNAPSHOT tell me that it's the non released
version currently running. That's helpful once the release is GA to know
if's the the GA version in place or not.
Having the -SNAPSHOT remove the confusion
Keep in mind there is a maven issue here. It is mainly in the devs env so
not really important there but in a operators lab like Pierre-Luc's it is
an added inconvenience. Like him I won't -1. It would solve what I have
been solving with rc branches of the release branch.
On Mon, Oct 20, 2014 at
Hi Pierre,
Thanks for sharing. I think in your use case, if you’re using debian packages
you can take the source and add a package release with suitable names in
debian/changelog; in case of rpms you can add a tag/build-version (like
4.4.1.20141020). What I’m proposing is to remove using
I'll chime in from a purely build engineer/maven user perspective. Adding
-SNAPSHOT to the version indicates a certain perspective on the part of the
build system. If you are using a system like Artifactory to store the
output artifacts it allows tracking how many snapshot versions to keep, if
On Oct 20, 2014, at 6:07 PM, Nate Gordon nate.gor...@appcore.com wrote:
I'll chime in from a purely build engineer/maven user perspective. Adding
-SNAPSHOT to the version indicates a certain perspective on the part of the
build system. If you are using a system like Artifactory to store the
That's right Nate tech decisions (not releases) are open for everyone so
thanks for your opinion.
I'd rather have the build process add the -SNAPSHOT then have it hardcoded
in our sources.
On Mon, Oct 20, 2014 at 6:38 PM, sebgoa run...@gmail.com wrote:
On Oct 20, 2014, at 6:07 PM, Nate Gordon
On Mon, Oct 20, 2014 at 12:33 PM, Rohit Yadav rohit.ya...@shapeblue.com
wrote:
Hi,
Background:
Whenever we start on a new release and cut its release branch, for example
4.5 branch, we add the -SNAPSHOT string to the version string in pom.xmls,
debian/changelog and elsewhere. Just this
24 matches
Mail list logo
