Actually the "new" names are a way of handling the versioning which is "recommended by Maven". See - we were doing it in a wrong way till now :-) Just like many other things maven.
It does have some value actually - it distinguishes SNAPSHOT builds between releases, and hints at what the next release version will be. But I am fine if we don't follow it, and go back to our old naming. Just thought we'd try something Maven-standard for once :-) Andrus On Sep 12, 2011, at 10:29 PM, Dzmitry Kazimirchyk wrote: > On 9/12/2011 9:37 PM, Andrus Adamchik wrote: >> I think we have pattern matching settings in Jenkins, not compatible with >> our new (maven-compliant) way of tagging the releases ? >> >> On Sep 12, 2011, at 9:34 PM, Apache Jenkins Server wrote: >> >>> ERROR: No artifacts found that match the file pattern >>> "trunk/framework/cayenne-client/target/cayenne-client-3.1-*.jar,trunk/framework/cayenne-server/target/cayenne-server-3.1-*.jar,trunk/framework/cayenne-lifecycle/target/cayenne-lifecycle-3.1-*.jar". >>> Configuration error? >>> ERROR: 'trunk/framework/cayenne-client/target/cayenne-client-3.1-*.jar' >>> doesn't match anything: 'trunk' exists but not >>> 'trunk/framework/cayenne-client/target/cayenne-client-3.1-*.jar' >>> Build step 'Archive the artifacts' changed build result to FAILURE > > Do we actually need to switch our development trunk version pattern to > something like '3.1M4-SNAPSHOT'? > I like more the old name: '3.1-SNAPSHOT'. '3.1M4-SNAPSHOT' is suggested by > maven release plugin but for me it seems too complicated and little bit > unusual. > And of course preserving the old name also solves this particular issue with > Jenkins :) > > Dzmitry >
