You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2009/02/01 02:48:59 UTC
[jira] Created: (JUDDI-175) resources are not on the eclipse
classpath by default
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.0alpha
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.
[jira] Assigned: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam reassigned JUDDI-175:
---------------------------------
Assignee: Kurt T Stam (was: Tom Cunningham)
> 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: Kurt T Stam
> 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.
[jira] Updated: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-175:
------------------------------
Fix Version/s: (was: 3.0alpha)
3.0
> 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.0
>
>
> 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.
[jira] Closed: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam closed JUDDI-175.
-----------------------------
Resolution: Fixed
Looks like it's not going to be "fixed", and intentionally made to work this way.
> 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: Kurt T Stam
> 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.
[jira] Commented: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Jeff Faath (JIRA)" <ju...@ws.apache.org>.
[ 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.
[jira] Commented: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675170#action_12675170 ]
Kurt T Stam commented on JUDDI-175:
-----------------------------------
Looks like it's by design:
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-WhyresourcefoldersinJavaprojecthaveexcluded%3D%22%22
> 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.
[jira] Updated: (JUDDI-175) resources are not on the eclipse
classpath by default
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-175:
------------------------------
Fix Version/s: (was: 3.0)
3.0beta
> 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.