Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.1
-
Fix Version/s: 2.2-beta-1
-
Component/s: None
-
Labels:None
-
Environment:Win XP, Java 1.5
-
Number of attachments :
Description
Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp ex. api-authorisation-4.00-20060502.150651-20.jar. Would it be possible to offer a flag on the plugin so that this behaviour could be turned off and the file could remain as api-authorisation-SNAPSHOT.jar?
The renaming of the files causes the files to become invalid when compiling native or CSharp binaries inside of maven.
Thanks,
Chris Stevenson
Issue Links
- duplicates
-
MASSEMBLY-67
assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}
-
Brett,
I've checked this issue:
http://jira.codehaus.org/browse/MASSEMBLY-67
And it says that the problem has been resolved but for myself and possibly the guy who is using the native plugin this is still a problem.
The problem is that when you are bring down dependencies for a library to distribute and one of your deps is at snapshot, instead of the jar being included in the archive as foo-SNAPSHOT.jar it gets included as foo-2006-04-08-01.....jar. This shouldn't cause a big issue with Java apps but causes a massive issue with C# apps, as the name of the file is burnt into the binary on compilation.
Is there anyway to have an attribute ex <timeStampedSnapshots> which is defaulted to true but can be turned off when using native or dotnet libraries?
Many thanks,
Chris