There is the same problem with maven-war-plugin overlay which skip
locally resolved dependencies because it unknows archive extension.
The plugin not produce error but it doesn't work.
11/21/08 2:53:43 PM CET: [INFO] [war:exploded]
11/21/08 2:53:43 PM CET: [INFO] Exploding webapp
11/21/08 2:53:43 PM CET: [INFO] Assembling webapp[noe-war] in
[D:\wks\framework\Noe\noe-war\target\webapp]
11/21/08 2:53:43 PM CET: [WARN] Dependency[Dependency
{groupId=noe.commons, artifactId=noefwk-war, version=1.0-SNAPSHOT,
type=war}] has changed (was Dependency {groupId=noe.commons,
artifactId=noefwk-war, version=1.0-SNAPSHOT, type=war}). If it was
included in the build as an overlay, consider cleaning the target
directory of the project (mvn clean)
11/21/08 2:53:43 PM CET: [INFO] Processing war project
11/21/08 2:53:43 PM CET: [INFO] Copying webapp
resources[D:\wks\framework\Noe\noe-war\src\main\webapp]
11/21/08 2:53:44 PM CET: [INFO] Processing overlay[ id
noe.commons:noefwk-war]
11/21/08 2:53:44 PM CET: [WARN] Skip unpacking dependency
file[D:\wks\framework\NoeFwk\noeFwkWar\target\classes with unknown
extension[]
11/21/08 2:53:44 PM CET: [INFO] Webapp assembled in[1500 msecs]
I doesn't find bug report about this in maven-war-plugin JIRA.
Regards,
Arnaud.
Igor Fedorenko a écrit :
Sorry, no good recommendation here.
Most of m2e value for the work that I do comes from workspace
dependency resolution, so I never considered this option. If you can
do without it, than yes, disabling workspace resolution will solve the
problem.
If you can afford running locally compiled maven-dependency-plugin,
then there is a patch attached to MDEP-187.
You can also play with your pom.xml files and/or goals that get
executed by m2e to disable maven-dependency-plugin execution.
Unfortunately, these are the only alternatives I only, and they are
not pretty.
--
Regards,
Igor
Mohan K R wrote:
So, what's the recommendation. Disable WS resolution? Thanks, facing
the same issue
On Tue, Nov 18, 2008 at 9:16 AM, Igor Fedorenko <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Currently, maven-dependency-plugin is not compatible with workspace
artifact resolution. There is a bug report
(http://jira.codehaus.org/browse/MDEP-187) and I was told the fix is
scheduled for maven-dependency-plugin 2.1.
--
Regards,
Igor
europheus wrote:
Hello,
I'm running into a build error when I force clean on my
eclipse project. During the process-test-resources phase, I
need to
copy a dependency jar into a folder for my test cases to find
and link
with. This configuration works fine using maven at the command
line,
but using m2eclipse v 0.96 and 0.97 I am getting this error:
11/14/08
11:19:42 AM EST: Build errors for content;
org.apache.maven.lifecycle.LifecycleExecutionException: Internal
error
in the plugin manager executing goal
'org.apache.maven.plugins:maven-dependency-
plugin:2.0:copy': Mojo execution failed.
When I enable debug output, I do not see any new information
regarding the error.
I am using eclipse 3.4 and I have set up to use the external
install of maven version 2.09
Here is how I configured the dependency plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
<executions>
<execution>
<id>copy</id>
<phase>process-test-resources</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>com.mygroup</groupId>
<artifactId>my-artifact</artifactId>
<version>${my-artifact.version}</version>
<type>jar</type>
<outputDirectory>${basedir}/target/test-classes/dependencies</outputDirectory>
<overWrite>true</overWrite>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
Is there a workaround for this or is this a bug?
Thanks
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
***********************************************************************************************************************
Ce message peut contenir des INFORMATIONS CONFIDENTIELLES destinées à l'usage exclusif du
destinataire. Si vous le receviez par erreur, merci de bien vouloir nous en avertir immédiatement par téléphone
ou messagerie,de le détruire et de n'en divulguer le contenu à personne.
This message may contain CONFIDENTIAL INFORMATION intended only for use by the addressee. If you
have received it by mistake, thank you for notifying us immediately by telephone or by e-mail,and please,
delete it and do not deliver it to anyone else.
***********************************************************************************************************************
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
