[
http://jira.codehaus.org/browse/MNG-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215108#action_215108
]
gesha commented on MNG-4301:
----------------------------
@deckrider
thankx for valuable tipps :/ Result is attached>
+ Error stacktraces are turned on.
Error reading settings.xml: end tag name </all> must be the same as start tag
<put> from line 28 (position: TEXT seen ...</params>\r\n </all>...
@35:17)
Line: 35
Column: 17
Error stacktrace:
org.apache.maven.SettingsConfigurationException: end tag name </all> must be
the same as start tag <put> from line 28 (position: TEXT seen ...</params>\r\n
</all>... @35:1
7)
Line: 35
Column: 17
at org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:432)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:202)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag
name </all> must be the same as start tag <put> from line 28 (position: TEXT
seen ...</params>\r\n
</all>... @35:17)
at
hidden.org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1708)
at
hidden.org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1143)
at
hidden.org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1105)
at
hidden.org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:179)
at
hidden.org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:86)
at
org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.parseServer(SettingsXpp3Reader.java:1062)
at
org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.parseSettings(SettingsXpp3Reader.java:1158)
at
org.apache.maven.settings.io.xpp3.SettingsXpp3Reader.read(SettingsXpp3Reader.java:1579)
at
org.apache.maven.settings.DefaultMavenSettingsBuilder.readSettings(DefaultMavenSettingsBuilder.java:122)
at
org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:163)
at
org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:154)
at
org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:142)
at org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:423)
... 10 more
> Invalid checksums on deploy when using webdav without extension
> ---------------------------------------------------------------
>
> Key: MNG-4301
> URL: http://jira.codehaus.org/browse/MNG-4301
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 2.2.1
> Environment: n/a
> Reporter: Kevin Shekleton
> Priority: Blocker
>
> With maven 2.2.1, our deployments via webdav are producing invalid checksums,
> similar to the issue reported in MNG-4235.
> From maven 2.0.8 and previous, the following build extension was required to
> deploy via webdav:
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-webdav</artifactId>
> <version>1.0-beta-2</version>
> </extension>
> </extensions>
> Starting with maven 2.0.9 (see MNG-3418), webdav was included by default and
> the aforementioned build extension must be removed from the project. If it
> was included in the project the deployment would fail as Maven would report
> multiple versions of wagon-webdav present.
> With maven 2.2.0, our deployment suffered from invalid checksums reported in
> MNG-4235.
> With maven 2.2.1, we still see the invalid checksums on deployment as
> reported in MNG-4235. However, I've found that if you add the above build
> extension into the project, we don't experience this issue (of generating
> invalid checksums). Is this workaround an intentional change brought about
> by the fix of MNG-4235?
--
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
