[
http://jira.codehaus.org/browse/CONTINUUM-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed CONTINUUM-1249.
---------------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
Fix Version/s: (was: Future)
It isn't a Continuum bug
> Remote repository JAR manifest not updated if dependancy scope is changed
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1249
> URL: http://jira.codehaus.org/browse/CONTINUUM-1249
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.0.3
> Environment: Windows XP
> Reporter: Mark Jeffery
> Assignee: Emmanuel Venisse
>
> 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.
--
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
