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 comment was this first option should not exists, unless you are just testing in your local sandbox.
On Wed, Apr 11, 2012 at 12:58 PM, Rajwinder Makkar <[email protected]>wrote: > 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 <[email protected]> wrote: > > > 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, Rajwinder Makkar > > <[email protected]>wrote: > > > > > 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 done by removing delete permissions in > artifactory > > > but then that causes another problem. In multi module maven project if > > one > > > module changes then either dev need to modify version on all artifacts > ( > > > which doesnt make sense ) or then need to modify individual pom and > > publish > > > only the artifact that is changes * which again is not manageable ) > > > > > > So need some advice on how this can be handled ? > > > > > > I have couple of thoughts : > > > > > > - Before running mvn command , write some thing custom to go through > all > > > pom's and query artifactory is version of artifact exist. if yes then > > dont > > > compile. Basically compile only artifacts who version doesnt exist in > > > artifactory using "mvn -pl " > > > > > > - Try Jenkins , I know jenkins is aware of modules in project , but not > > > sure if it intelligent enough to compile only those which are changed ? > > > > > > Please advice > > > > > > -Raj > > > > > >
