[jira] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160323#action_160323 ] John Casey commented on MNG-3961: - sounds fine. > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160297#action_160297 ] Jason van Zyl commented on MNG-3961: My reasoning here is that we've not talked about how to actually deal with this so I think it would be best to roll it back. > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160296#action_160296 ] Jason van Zyl commented on MNG-3961: How about we just make an issue to address custom profile activation and take this out for now? So that we can keep the model version the same. > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160283#action_160283 ] John Casey commented on MNG-3961: - This was added probably two years ago in trunk, but it was intended to be part of an incremented modelVersion, not as part of 4.0.0...I just hadn't rewritten the project builder to accommodate the new versions yet, so I didn't bump it at that time. If we have another approach for handling custom profile activators, let's remove this. If not, maybe we need to look more closely at custom profile activation. > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160035#action_160035 ] Paul Benedict commented on MNG-3961: What about aligning the XSD version jump with Maven's major version? Maven 2 -> XSD 4.0 Maven 2.1 -> XSD 4.1 Maven 3 -> XSD 5.0 > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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] Commented: (MNG-3961) Update the version of the XSD
[ http://jira.codehaus.org/browse/MNG-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160031#action_160031 ] Jason van Zyl commented on MNG-3961: Do you know when this was added and for what? > Update the version of the XSD > - > > Key: MNG-3961 > URL: http://jira.codehaus.org/browse/MNG-3961 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 3.0-alpha-1 >Reporter: Vincent Siveton > Fix For: 3.0-alpha-2 > > > Since the model adds new field (ActivationCustom), I think the xsd version > should be 4.0.1 or 5.0. -- 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
