You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/07/31 09:41:13 UTC
[jira] Updated: (MRM-19) Make repoclean transform the m1 poms
although jar files didn't change
[ http://jira.codehaus.org/browse/MRM-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-19:
----------------------------
Fix Version/s: (was: 1.0.x)
Future
> Make repoclean transform the m1 poms although jar files didn't change
> ---------------------------------------------------------------------
>
> Key: MRM-19
> URL: http://jira.codehaus.org/browse/MRM-19
> Project: Archiva
> Issue Type: Improvement
> Components: repository converter
> Reporter: Carlos Sanchez
> Priority: Minor
> Fix For: Future
>
>
> When changing or creating a pom in m1 repo it doesn't propagate to m2 repo if the jar timestamp is not updated or doesn't exist
--
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