jt400 is now at 6.1. I asked to jt400 developpers about maven repository, but it was no done.
I will fix the pom and upload the 6.1 to repo1 >2008/1/15, Doug Bateman <[EMAIL PROTECTED]>: > The website for the jt400 can be inferred from the net.sf.jt400 group name: > http://jt400.sourceforge.net/ > > It's sourceforge page is: > http://sourceforge.net/projects/jt400/ > > Technically, anyone with an Internet connection and a command-line version > of Maven can deploy a file to the central maven repositories. However, it's > usually best to first inquire on the project mailinglist if anyone is > managing that responsibility. While sometimes someone on the project > actually does do the maven deployments upon each release, more commonly than > not it's a user like yourself who notices the need who does so. To deploy a > file to a maven repository, you need a pom (which can be created by adapting > the current one, updating the version number, dependencies, ), an Internet > connection, and the Maven deploy plugin which comes with Maven: > > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html > > Doug > > -----Original Message----- > From: Henri Gomez [mailto:[EMAIL PROTECTED] > Sent: Monday, January 14, 2008 4:59 PM > To: [email protected] > Subject: Re: [m2eclipse-user] m2Eclipse plugin remains unusable without > install support > > 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-instal > > l-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 > > > --------------------------------------------------------------------- > 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
