Am 29.08.2011 17:45 schrieb "Eric Kolotyluk" <[email protected]>: > > On the command line in in the project with the POM I showed I use > > P:\Intersystem\main\platform.Java\intersystem-jni4net>mvn validate > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building intersystem-jni4net 0.0.2-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [WARNING] The POM for com.kodak.jni4net:jni4net-maven-plugin:jar:0.0.1-SNAPSHOT is missing, no dependency information available > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 0.139s > [INFO] Finished at: Mon Aug 29 08:42:31 PDT 2011 > [INFO] Final Memory: 4M/368M > [INFO] ------------------------------------------------------------------------ > [ERROR] Plugin com.kodak.jni4net:jni4net-maven-plugin:0.0.1-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.kodak.jni4net:jni4net-maven-plugin:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.jni4net:jni4net-maven-plugin:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1]
^^^^^^^^^ Maven does not only cache found artifacts, but also the fact that a certain artifact is *not* available. This is what you can configure as "not found ttl" or similar for nexus repositories of type "proxy". Maven itself caches this information in your local m2 repo. To override the "not found ttl", do one of the following: * run maven with -U command line switch * add <updatePolicy>always<updatePolicy> to the <snapshots> element of your plugin repository in your settings.xml Regards, Ansgar > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException > P:\Intersystem\main\platform.Java\intersystem-jni4net> > > > On 2011-08-29 8:27 AM, Hilco Wijbenga wrote: >> >> On 29 August 2011 07:32, Eric Kolotyluk<[email protected]> 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? >> >> How are you calling your plugin? In a POM? Or on the command line? You >> need to make sure Maven knows the group id for the plugin so just >> invoking (e.g.) mvn jni4net:proxygen is not going to work. Well, not >> without extra work anyway. >> >>> 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? >> >> A global repository? You may have heard of Central? :-) >> >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >> >> --------------------------------------------------------------------- >> 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] >
