[jira] Updated: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

2007-03-28 Thread John Casey (JIRA) 

 [ 
http://jira.codehaus.org/browse/MASSEMBLY-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey updated MASSEMBLY-67:


Fix Version/s: (was: 2.2)
   2.2-beta-1

 assembling dependent jars or snapshots uses timestamp formatted version 
 instead of ${version}
 -

 Key: MASSEMBLY-67
 URL: http://jira.codehaus.org/browse/MASSEMBLY-67
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Reporter: Mark J. Titorenko
 Assigned To: John Casey
 Fix For: 2.2-beta-1

 Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt


 I'm using the jar plugin to add my dependencies to the manifest.  I'm also 
 using the assembly plugin to package all dependencies into one archive.  The 
 problem is that the jar manifest adds my dependencies as foo-SNAPHOT and 
 the archiver adds them as foo-20041113.jar.
 This causes my snapshot classes to not be found at runtime.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

2006-07-14 Thread John Casey (JIRA) 
 [ http://jira.codehaus.org/browse/MASSEMBLY-67?page=all ]

John Casey updated MASSEMBLY-67:


Fix Version: 2.2

 assembling dependent jars or snapshots uses timestamp formatted version 
 instead of ${version}
 -

  Key: MASSEMBLY-67
  URL: http://jira.codehaus.org/browse/MASSEMBLY-67
  Project: Maven 2.x Assembly Plugin
 Type: Bug

 Reporter: Mark J. Titorenko
  Fix For: 2.2
  Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt


 I'm using the jar plugin to add my dependencies to the manifest.  I'm also 
 using the assembly plugin to package all dependencies into one archive.  The 
 problem is that the jar manifest adds my dependencies as foo-SNAPHOT and 
 the archiver adds them as foo-20041113.jar.
 This causes my snapshot classes to not be found at runtime.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

2006-07-07 Thread Baerrach bonDierne (JIRA) 
 [ http://jira.codehaus.org/browse/MASSEMBLY-67?page=all ]

Baerrach bonDierne updated MASSEMBLY-67:


Attachment: MJAR-28-TestCases-Patch.txt
MJAR-28-Notes.txt

 assembling dependent jars or snapshots uses timestamp formatted version 
 instead of ${version}
 -

  Key: MASSEMBLY-67
  URL: http://jira.codehaus.org/browse/MASSEMBLY-67
  Project: Maven 2.x Assembly Plugin
 Type: Bug

 Reporter: Mark J. Titorenko
  Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt


 I'm using the jar plugin to add my dependencies to the manifest.  I'm also 
 using the assembly plugin to package all dependencies into one archive.  The 
 problem is that the jar manifest adds my dependencies as foo-SNAPHOT and 
 the archiver adds them as foo-20041113.jar.
 This causes my snapshot classes to not be found at runtime.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira