At 10:56 +1000 10/3/03, [EMAIL PROTECTED] spoke thusly:

No, MAVEN_REPO is fine, but .tld artifacts don't need to be, or do not belong on the classpath. They are put there, as per the example below.
These non jar type files on the classpath causes Eclipse to complain with
the indicated message.
Note that eclipse refers to both MAVEN_REPO, as well as extensions of it as "classpath variables".


Dolf Starreveld <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to