yes that is a much harder question and solution!
On Wed, Apr 11, 2012 at 4:38 PM, Rajwinder Makkar
wrote:
> True .. but the issue is how to restrict it from happening when it comes to
> formal builds.
>
> -Raj
>
> On Wed, Apr 11, 2012 at 4:03 PM, mike digioia wrote:
>
> > Sorry but I looked at t
True .. but the issue is how to restrict it from happening when it comes to
formal builds.
-Raj
On Wed, Apr 11, 2012 at 4:03 PM, mike digioia wrote:
> Sorry but I looked at this-
>
> *8
> You're describing the two possible solutions. Either bump the version
> on all
Sorry but I looked at this-
*8
You're describing the two possible solutions. Either bump the version
on all artifacts produced, or just deploy the artifact that has
changed (with a new version number). Which way to go depends on
My c
I think suggestion is "not" to bump version of all the artifacts. And also
Ron explained the approach they took to manage diff artifact version ( if u
understood it correctly ).
-Raj
On Mon, Apr 9, 2012 at 12:57 PM, mike digioia wrote:
> Hi
>
> Maybe I don't understand the recommendation here!
Hi
Maybe I don't understand the recommendation here! One should never
change/bump the rev number of anything that has not changed, including
artifacts, especially if they are known elsewhere with the original rev. If
use cases require this, then it is broken.
On Sat, Apr 7, 2012 at 10:27 PM, Rajw
We started by changing the versions of everything but as we got to 70
modules for the application we stopped.
We stepped back and started to look at our code in the same way that we
looked at third party (Apache, Spring, etc.) libraries that we used.
We were perfectly able to use the same version
True .. personally i am also not in favor of bumping version of all
artifacts when only one artifacts has changed in the project. This also
leads to addition of extra space in artifactory or any repo manager as the
same artifact will be stored with just diff version number without any
need. Consume
Your described scenario is the common scenario for Maven. You should
never change (or delete) a release. Your repo manager should always be
configured to deny that.
You're describing the two possible solutions. Either bump the version
on all artifacts produced, or just deploy the artifact that has
Here is a dev scenario :
We are using maven 3 + artifactory + microst TFS server
We dont want to over write an existing version of an artifact in our
company repo , so the the consumers of artifacts should not be surprised
all the sudden when producers update artifact.
Now this can simply be don
