Am 29.08.2011 17:25 schrieb "Eric Kolotyluk" <[email protected]>: > > OK, this is what I have in my settings.xml > > <profile> > <id>nexus</id> > <!--Enable snapshots for the built in central repo to direct --> > <!--all requests to nexus via the mirror --> > <repositories> > <repository> > <id>central</id> > <url>http://central</url> > <releases><enabled>true</enabled></releases> > <snapshots><enabled>true</enabled></snapshots> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>central</id> > <url>http://central</url> > <releases><enabled>true</enabled></releases> > <snapshots><enabled>true</enabled></snapshots> > </pluginRepository> > </pluginRepositories> > </profile> > > Do I need to configure something else?
Yes. <mirrors> The URL you configured for repository "central" is invalid, so the only way to get this working is to either specify a mirror redirecting all artifact requests to your repository manager *or* correcting the "central" url. Furthermore, make sure that the mirror url points to a content group which contains at least central *and* your hosted snapshot repo. Best regards Ansgar > > Cheers, Eric > > > On 2011-08-29 7:53 AM, Ron Wheeler wrote: >> >> I am not sure but I think that you are deploying to the SNAPSHOT repo but maven is looking for plugins in the repo that you have defined as your plug-in repo. >> Check your settings.xml to see where you tell Maven to find plugins. >> >> Ron >> >> On 29/08/2011 10:44 AM, Eric Kolotyluk wrote: >>> >>> This is what I have in my POM >>> >>> <distributionManagement> >>> <downloadUrl>http://nexus:8081/nexus/content/groups/public</downloadUrl> >>> <repository> >>> <uniqueVersion>false</uniqueVersion> >>> <id>nexus</id> >>> <name>Kodak Release Repository</name> >>> <url>http://nexus:8081/nexus/content/repositories/releases</url> >>> <layout>default</layout> >>> </repository> >>> <snapshotRepository> >>> <id>nexus</id> >>> <name>Kodak Snapshot Repository</name> >>> <url>http://nexus:8081/nexus/content/repositories/snapshots</url> >>> <layout>default</layout> >>> </snapshotRepository> >>> </distributionManagement> >>> >>> Is there something else I need to configure? >>> >>> Cheers, Eric >>> >>> On 2011-08-29 7:40 AM, Ron Wheeler wrote: >>>> >>>> Just a wild guess until someone smarter comes along. >>>> Do you have your settings looking for plugins in your SNAPSHOT repo? >>>> I think that the plugin repo is defined separately from the artifact repos. >>>> >>>> Only a guess. >>>> >>>> Ron >>>> >>>> On 29/08/2011 10:32 AM, Eric Kolotyluk wrote: >>>>> >>>>> OK, I'm trying to get my first mojo working. >>>>> >>>>> I created a project with the maven-plugin archetype and used the default mojo that is there, but I cannot seem to get it to run. >>>>> >>>>> The first time I tried to run it maven complained it could not find the plugin. So then I ran a maven install, but it still could not find it because it would only look in Nexus for it - why doesn't it just look in the local repository? Then I ran a maven deploy, so the plugin project artifacts are definitely in Nexus now, but maven is still complaining it cannot find the POM for the plugin. >>>>> >>>>> I suspect the problem is my plugin is version 0.0.1-SNAPSHOT but the files in Nexus are like >>>>> >>>>> nexus/content/repositories/snapshots/com/kodak/jni4net/jni4net-maven-plugin/0.0.1-SNAPSHOT/jni4net-maven-plugin-0.0.1-20110829.135006-1.pom >>>>> >>>>> and the POM I am trying to run the plugin from looks like >>>>> >>>>> <plugin> >>>>> <groupId>com.kodak.jni4net</groupId> >>>>> <artifactId>jni4net-maven-plugin</artifactId> >>>>> <version>0.0.1-SNAPSHOT</version> >>>>> <executions> >>>>> <execution> >>>>> <phase>validate</phase> >>>>> <goals> >>>>> <goal>proxygen</goal> >>>>> </goals> >>>>> </execution> >>>>> </executions> >>>>> </plugin> >>>>> >>>>> Does anyone have any advice? >>>>> >>>>> By the way, if I want to share this plugin with the open source community, how would I go about learning how to do that? Is there some global repository I can submit it to (because I do not want to have to publish a repository from our corporate intranet on the internet)? jni4net comes from SourceForge - perhaps that would be the best place to start? >>>>> >>>>> Cheers, Eric >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >>> >>> >>> --------------------------------------------------------------------- >>> 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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
