so I am wondering if its a m2eclipse configuration or some
> classpath/command line type mess up.
>
> > From: ajpurk...@hotmail.com
> > To: users@maven.apache.org
> > Subject: RE: maven-dependency-plugin odd behaviour
> > Date: Thu, 21 May 2009 20:36:52 -0400
>
urk...@hotmail.com
> To: users@maven.apache.org
> Subject: RE: maven-dependency-plugin odd behaviour
> Date: Thu, 21 May 2009 20:36:52 -0400
>
>
> Thanks will give that a try. I tried a few things around that idea that did
> not seem to work but maybe that will address it. Al
bject: RE: maven-dependency-plugin odd behaviour
> Date: Thu, 21 May 2009 15:11:28 -0500
>
> Yup..seen that..be careful switching between CLI and m2eclipse..turn of
> Build Automatically when running CLI..
>
>
> Thanks,
> mohan kr
>
>
> -Original Messag
-dependency-plugin odd behaviour
I have the following setup in a POM file during a transition phase between a
massive ANT based project and trying to mavenise it. When run using the
install target from the command line with maven 2.1 I get the expected
behaviour:
[INFO] [dependency:copy {execution: copy
Access is denied
might mean "run it again"
or "make sure no other java processes are running that are related"
maybe eclipse has a hold on it?
2009/5/21 Adam Purkiss :
>
>
> I have the following setup in a POM file during a transition phase between a
> massive ANT based project and trying to mav
I have the following setup in a POM file during a transition phase between a
massive ANT based project and trying to mavenise it. When run using the install
target from the command line with maven 2.1 I get the expected behaviour:
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured A
