Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-906 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-906 Summary: scm:prepare-release makes unwelcome changes to project.xml Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other Versions: 1.0-rc1 Assignee: Reporter: Joe Germuska Created: Tue, 7 Oct 2003 6:23 PM Updated: Tue, 7 Oct 2003 6:23 PM Environment: Mac OS X 10.2.8; cvs 1.11.8; java -version: java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-69.1) Java HotSpot(TM) Client VM (build 1.4.1_01-24, mixed mode) Description: When executing scm:prepare-release, the transform to project.xml results in some unwelcome changes. Specifically, the root 'project' element is changed to: <project xsi:schemaLocation="file:///opt/maven/maven-project.xsd"> followed by the bare text line: file:///opt/maven/maven-project.xsd After this change, any call to a maven goal results in the following stack trace: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:schemaLocation" is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1527) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:201) This can be corrected by adding an "xmlns:xsi" declaration to the root element, but I don't want to do that, because my teammates may not have their maven-project.xsd in the same location. We could probably use a URL for the schemaLocation and then have a version which is shareable, but then I don't know what would happen if I needed to do an offline build. I don't think any of this is relevant, but Brett asked me to include the contents of my extensions directory, so just in case; % ls -1 $JAVA_HOME/lib/ext/ apple_provider apple_provider.jar ldapsec.jar localedata.jar sunjce_provider.jar I just reproduced this for a second time on a different project. I haven't tried it on a project file which has the schemalocation already defined. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
