| validate not called to find dependencies [message #500406] |
Wed, 25 November 2009 18:34  |
Eclipse User |
|
|
|
Hello,
I have a project with a pom containing two dependencies that are copied to the users local repository during the validate phase. They are copied with a <goal>install-file</goal>.
Although the project works fine with maven from the commadn line, it will not work in ecilpse with IAM. The classpath container disappears.
If instead 'mvn validate' is run on the command line first, then the project opened in eclipse, it works as expected.
I suspect this is because IAM doesn't run the validate target before deciding there are missing dependencies.
This seems like a bug. Are there any known workarounds, and should I file it as a bug?
|
|
|
| Re: validate not called to find dependencies [message #500608 is a reply to message #500406] |
Fri, 27 November 2009 01:09  |
| Eclipse User |
|
|
|
probably you are right, your way of using validate is unorthodox and IAM
does not run phases when it parses the pom
you can check the Maven 2 Events view and the Eclipse Error Log to see
if something comes up there.
On 11/25/09 5:34 PM, Kenny MacDermid wrote:
> Hello,
>
> I have a project with a pom containing two dependencies that are copied
> to the users local repository during the validate phase. They are copied
> with a <goal>install-file</goal>.
>
> Although the project works fine with maven from the commadn line, it
> will not work in ecilpse with IAM. The classpath container disappears.
>
> If instead 'mvn validate' is run on the command line first, then the
> project opened in eclipse, it works as expected.
>
> I suspect this is because IAM doesn't run the validate target before
> deciding there are missing dependencies.
>
> This seems like a bug. Are there any known workarounds, and should I
> file it as a bug?
|
|
|
Powered by
FUDForum. Page generated in 0.08947 seconds
Home