You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dolf Starreveld <do...@starreveld.com> on 2003/10/03 01:06:25 UTC
Eclipse plugin does not deal with artifact type
I am using the eclipse plugin for a project in which project.xml
lists a dependency on a <type>tld</type> artifact.
maven eclipse
then generates a dependency on
MAVEN_REPO/path/file.tld
Arguable this has no value, but Eclipse also does not like it,
producing "Unbound classpath variable" messages.
Manually removing these guys in Eclipse solves the problem, but of
course each execute of maven eclipse reintroduces the problem.
It seems that one can add a <eclipse.depency> property to each
dependency to cause special behavior.
I think a solution would be to either:
- Introduce a new property <eclipse.exclude>, or
- Make the eclipse plug-in aware of the supported artifact types and
only include artifacts of type: jar, war, sar etc. but not tld
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Eclipse plugin does not deal with artifact type
Posted by di...@multitask.com.au.
Got a good list?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Dolf Starreveld <do...@starreveld.com> wrote on 03/10/2003 09:06:25 AM:
> I am using the eclipse plugin for a project in which project.xml
> lists a dependency on a <type>tld</type> artifact.
> maven eclipse
> then generates a dependency on
> MAVEN_REPO/path/file.tld
> Arguable this has no value, but Eclipse also does not like it,
> producing "Unbound classpath variable" messages.
> Manually removing these guys in Eclipse solves the problem, but of
> course each execute of maven eclipse reintroduces the problem.
>
> It seems that one can add a <eclipse.depency> property to each
> dependency to cause special behavior.
> I think a solution would be to either:
> - Introduce a new property <eclipse.exclude>, or
> - Make the eclipse plug-in aware of the supported artifact types and
> only include artifacts of type: jar, war, sar etc. but not tld
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Eclipse plugin does not deal with artifact type
Posted by di...@multitask.com.au.
Dolf Starreveld <do...@starreveld.com> wrote on 03/10/2003 09:06:25 AM:
> I am using the eclipse plugin for a project in which project.xml
> lists a dependency on a <type>tld</type> artifact.
> maven eclipse
> then generates a dependency on
> MAVEN_REPO/path/file.tld
> Arguable this has no value, but Eclipse also does not like it,
> producing "Unbound classpath variable" messages.
What has no value? The MAVEN_REPO variable??
If so, please execute eclipse:add-maven-repo
as per http://maven.apache.org/reference/plugins/eclipse/goals.html
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org