I fixed the pom on my archiva directory. BTW, I don't know who is managing the maven setup for jt400.
2008/1/14, Doug Bateman <[EMAIL PROTECTED]>: > Maven 2.0.x has always whined for me about the misspelling of licenses in > that pom. But it always did so as a warning, not an error. It does seem > the Maven 2.1 embedder is more strict about invalid poms, which isn't > necessarily a bad thing. The trick here is to fix the jt400 pom. The quick > fix is to edit the cached pom in your local repository. The real fix is to > coordinate with the jt400 project and deploy the very latest version of the > driver (which fixes some pretty major bugs) using a valid pom that doesn't > have the misspelling of licenses. > > > > On 1/14/08, nhhockeyplayer <[EMAIL PROTECTED]> wrote: > > > > Ok, I'm back for this week. > > > > Having put in a week+3 in revealing fresh install issues and launch > issues. > > > > Is anything being looked into for this? > > > > Is there a time frame? > > > > > unleashed the fiery Russian vitriolic open source drop kick of death > > This is kinda scary. > > > > ----- > > Best regards > > Ken in nashua > > -- > > View this message in context: > http://www.nabble.com/m2Eclipse-plugin-remains-unusable-without-install-support-tp14697346s177p14802700.html > > Sent from the Maven Eclipse - User mailing list archive at Nabble.com. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
