Unless I'm mistaken, there is no "M1 to M2 converter". There is only a "M2 to M1 converter".
So probably the M2 project pom itself should be updated. File a JIRA bug in MEV (Maven Evangelism) with the fixed pom attached. Wayne On 5/17/06, Paul Spencer <[EMAIL PROTECTED]> wrote:
Dennis, It sounds like a bug in the "Maven1-to-Maven2 repo converter". Is this something I should report? If so, who should I report it to? Paul Spencer Dennis Lundberg wrote: > Paul Spencer wrote: > >> I am getting the following error when Maven is downloading >> commons-logging-1.1.pom from repo.mergere.com >> >> [WARNING] POM for 'commons-logging:commons-logging:pom:1.1:compile' is >> invalid. It will be ignored for artifact resolution. Reason: Parse >> error reading POM. Reason: expected start tag name and not / >> (position: START_DOCUMENT seen </... @1:2 >> ) >> >> >> I also get a "XML Parsing Error: not well-formed" error when viewing >> the pom in a browser. >> >> http://repo.mergere.com/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.pom > > > > The Maven 2 pom for commons-logging is created automatically by the > Maven1-to-Maven2 repo converter. It seems that the pom in question does > not have the xml declaration on a line of its own. > > Here's what the first two lines look like: > > <?xml version="1.0" encoding="UTF-8"?><project> > <modelVersion>4.0.0</modelVersion> > > That should really be three lines like this: > > <?xml version="1.0" encoding="UTF-8"?> > <project> > <modelVersion>4.0.0</modelVersion> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
