Using a local repository? But then every developer has to add this to their local repository?? And it gets even more messy to get this working with automatic builds?
Or do you mean that I should add another hosted repository in nexus? (usually "local" repository refers to the repository on your own machine?) Again, the central part was just an example, the question was more: If I have a nexus server, WHERE should I install it? http://localhost:8081/nexus/content/repositories/thirdparty -DrepositoryId=thirdparty<http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central>? (since a "thirdparty" hosted repository is already defined in the default nexus setup?) And by the way, why IS there a -DrepositoryId if that is part of the URL anyway? 2008/6/12 Ed Hillmann <[EMAIL PROTECTED]>: > On Wed, Jun 11, 2008 at 4:59 PM, Kent Närling <[EMAIL PROTECTED]> > wrote: > > Actually, I tried to upload this plugin manually to our nexus repository, > > but cannot get it to install properly... > > > > Trying the command: > > b-plugin\1.1>mvn deploy:deploy-file -DgroupId=com.sun.tools.xjc.maven2 > > -DartifactId=maven-jaxb-plugin -Dversion=1.1 -Dpackaging=maven-plugin > > -Dfile=maven-jaxb-p > > lugin-1.1.jar -Durl= > http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central > > > > But only get the error: > > [ERROR] BUILD ERROR > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Error deploying artifact: Failed to transfer file: > > > http://localhost:8081/nexus/content/repositories/central/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.jar > . > > Return code is: 401 > > > > Guess I probably use the wrong URL, but the documentation regarding which > > URL to specify is.... well, non-existing? > > Should it point to the nexus root? (would be logical considering you > specify > > -DrepositoryId etc) tried this too, doesn't work... > > > > //Kent > So, you are trying to deploy an artifact to your mirror of central? I > don't know if you can do that or not. But taking an uneducated guess > I'd think you couldn't do that. Wouldn't you be better off having a > local repository called "third.party" and use that as repository of > third party artifacts that are manually deployed to your Nexus server? > Then, you can include the third.party repository in the public group > and it's available. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
