wondering where nexus is looking to resolve dependencies? I'll try <scope>provided</scope> for nexus-core
(re)posted to nexus-...@sonatype.org Thanks Stewart Martin > Subject: Re: Sonatype plugin question? > From: mccu...@gmail.com > Date: Sun, 23 Feb 2014 00:37:17 +0000 > To: dev@maven.apache.org > > On 23 Feb 2014, at 00:08, Martin Gainty <mgai...@hotmail.com> wrote: > > I *think* the sonatype folk went home for weekend so I'll ask maven gurus > > Odd assumption, why didn’t you at least try asking this question on > nexus-user or nexus-dev? > > > Close to getting a plugin working but when i start wrapper.exe the > > wrapper.log displays this error: > > > > "The following plugins were processed: > > jvm 1 | ... > > org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: > > action=ACTIVATE result=BROKEN > > Is this your own plugin? You should ideally choose a groupId that matches > your organization/company > > > jvm 1 | Reason: Plugin artifact "com.sonatype.nexus:nexus-core:2.7.0::jar" > > not found! > > Looks like your pom.xml has a bad dependency - nexus-core has a groupId of > org.sonatype.nexus and should be a provided dependency > > In fact you should really just depend on nexus-plugin-api as explained in > http://books.sonatype.com/nexus-book/reference/plugdev.html > > > Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? > > > > local repo? > > some undisclosed maven repo? > > > > classpath? > > > > HELP! > > Best way to get help is to ask this on either of the nexus mailing lists > (http://www.sonatype.org/nexus/participate) - paste a copy of your plugin > pom.xml > > > Martin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
