assembling dependencies uses timestamp instead of snapshot jars

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None

Description

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.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-67 assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
Ryan Sonnek added a comment -

my local snapshots must have been out of date, because rerunning the assembly after rebuilding my projects put the right jars in the assembly.

Show
Ryan Sonnek added a comment - my local snapshots must have been out of date, because rerunning the assembly after rebuilding my projects put the right jars in the assembly.

People

  • Assignee:
    Unassigned
    Reporter:
    Ryan Sonnek
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: