juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Faath (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-175) resources are not on the eclipse classpath by default
Date Wed, 04 Feb 2009 20:40:00 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670453#action_12670453
] 

Jeff Faath commented on JUDDI-175:
----------------------------------

While researching another issue, I found this thread in the eclipse web tools newsgroup. 
It appears to be an issue with the maven-eclipse plugin:

http://dev.eclipse.org/newslists/news.eclipse.webtools/msg17927.html

> resources are not on the eclipse classpath by default
> -----------------------------------------------------
>
>                 Key: JUDDI-175
>                 URL: https://issues.apache.org/jira/browse/JUDDI-175
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.0alpha
>            Reporter: Kurt T Stam
>            Assignee: Tom Cunningham
>            Priority: Minor
>             Fix For: 3.0beta
>
>
> When using the http://m2eclipse.codehaus.org/ plugin in eclipse (version 0.0.12.20071107-2300)
and turning on "Enable Nested Module" a nice .classpath is generated by the plugin. The issue
that in each of the src/test/resources there is an exclusion filter of '**' so no resources
are on the eclipse .classpath by default. We should investigate if this is due a problem in
our pom or with the plugin.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message