[jira] Updated: (CONTINUUM-156) should validate that an updated pom doesn't change too drastically

2005-09-29 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-156?page=all ]

Brett Porter updated CONTINUUM-156:
---

Fix Version: (was: 1.0-beta-1)
 1.1

 should validate that an updated pom doesn't change too drastically
 --

  Key: CONTINUUM-156
  URL: http://jira.codehaus.org/browse/CONTINUUM-156
  Project: Continuum
 Type: Improvement
 Reporter: Brett Porter
  Fix For: 1.1



 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



[jira] Updated: (CONTINUUM-156) should validate that an updated pom doesn't change too drastically

2005-08-21 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-156?page=all ]

Brett Porter updated CONTINUUM-156:
---

Assign To: (was: Jason van Zyl)

 should validate that an updated pom doesn't change too drastically
 --

  Key: CONTINUUM-156
  URL: http://jira.codehaus.org/browse/CONTINUUM-156
  Project: Continuum
 Type: Improvement
 Reporter: Brett Porter
  Fix For: 1.0-beta-1



 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