[CONTINUUM-1249] Remote repository JAR manifest not updated if dependancy scope is changed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0.3
• Component/s: Integration - Maven 2
• Environment: Windows XP
• Assignee: Emmanuel Venisse
• Reporter: dandare100
• Created: 23/Apr/07 02:00
• Updated: 31/Jul/07 17:03
• Resolved: 31/Jul/07 17:03

Description

If Maven2 dependancy scope is changed from the default to provided, and the "clean install" goals are run everything is fine. The referenced jars manifest entry is removed and the jar is installed in the local repository.

If you run a "clean deploy" straight afterwards, the project state has not changed and the resulting jars are not deployed to the remote repository.

So the problem is that the jars deployed on a previous "clean deploy" are still in the repository with incorrect manifest entries. (Still referencing the "provided" dependancy.

If the pom is updated and a "clean deploy" is done straight away, it works fine.