continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-156) should validate that an updated pom doesn't change too drastically
Date Wed, 02 Apr 2008 07:03:59 GMT

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

Brett Porter closed CONTINUUM-156.
----------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: Future)

I think we no longer automatically take in SCM updates to the POM

> should validate that an updated pom doesn't change too drastically
> ------------------------------------------------------------------
>
>                 Key: CONTINUUM-156
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-156
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Core system
>            Reporter: Brett Porter
>
> I added maven-core's POM, which is using a post -alpha-2 technique of inheriting the
SCM connection URL and appending the artifact ID.
> This resulted in the new SCM URL being different and so it checked out the root POM and
proceeded to checkout all of maven/components/trunk.
> IF the group ID/artifact ID of the POM changes on update, I think this needs to go into
an error state that requires user intervention to either accept it has changed, or find out
what is wrong.

-- 
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

        

Mime
View raw message