I did again it this way
mvn install:install-file
-Dfile=D:\Projects\libs\maven-was-plugin-1.0-SNAPSHOT.jar
-DgroupId=com.davidkarlsen.maven.plugins -DartifactId=maven-was-plugin
-Dversion=1.0-SNAPSHOT -Dpackaging=jar
And maven told me that all is ok.
Also I drop the dependency and left only plugin tag
<plugin>
<groupId>com.davidkarlsen.maven.plugins</groupId>
<artifactId>maven-was-plugin</artifactId>
</plugin>
And maven still tells me that
The plugin 'com.davidkarlsen.maven.plugins:maven-was-plugin' does not exist
or no valid version could be found
And I cannot understend what is -Dpackaging=maven-plugin?
I also used with this parameter, but mistake it the same.
-----Original Message-----
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 9:26 PM
To: Maven Users List
Subject: Re: Problem with plugin discovery
Hi,
Denis Bessmertniy schrieb:
> Here is the part of my POM file
>
> <?xml version="1.0"?><project>
> .....
>
> <dependency>
> <groupId>com.davidkarlsen.maven.plugins</groupId>
> <artifactId>maven-was-plugin</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
This dependency is not needed, as just the build and not your project itself
depends on the plugin. This is the first reason your build possibly will
fail.
A plugin has a packaging of 'maven-plugin' (look in the pom in the
repository you got it from) and if you installed it correctly it will have
this packaging in your repository too. As you have not given a
<type>maven-plugin</type> element in the dependency declaration maven is
searching a 'jar' type dependency, and will fail.
> </dependencies>
> <build>
> <plugins>
> <plugin>
> <groupId>com.davidkarlsen.maven.plugins</groupId>
> <artifactId>maven-was-plugin</artifactId>
> <configuration>
> <script>C:\Program
> Files\IBM\Rational\SDP\6.0\runtimes\base_v6\bin\ejbdeploy.bat</script>
> </configuration>
> <executions>
> <execution>
> <goals>
> <goal>deploy</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
>
> </plugins>
> </build>
> </project>
>
Continuing from the explanation above, when you installed the plugin not
correctly it will have a packaging of type jar in your local repository
while maven is looking for an artifact with the type 'maven-plugin' for the
plugin declared in your pom and will fail again.
> As you see I need maven-was-plugin. I downloaded it and installed it
> manually. But maven tells me that it cannot locate this plugin
How did you install it? Have you used the original pom? Or have you given
the correct packaging via the '-Dpackaging=...' system property?
Did you use install:install-file at all or did you just copy the files?
I hope the explanation given is understandable.
-Tim
> [INFO] The plugin 'com.davidkarlsen.maven.plugins:maven-was-plugin'
> does not exist or no valid version could be found
>
> But I have it in my repository
>
> Why it so?
>
>
> ---------------------------------------------------------------------
> 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]
