[
https://issues.apache.org/jira/browse/OODT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973265#action_12973265
]
Brian Foster commented on OODT-88:
----------------------------------
Other things to note, when running the maven eclipse plugin:
- it will try to link to your oodt dependencies as an eclipse project one
directory up with the same name as the it's artifactId.
- if you check out cas-catalog, but check out commons with project name
commons, not oodt-commons, and metadata as metadata and not cas-metadata, you
will end up build errors saying projects oodt-commons and cas-metadata can't be
found.
- if you would like your project to depend on the installed version (in your
local maven repo) of oodt-commons and cas-metadata, then run the eclipse
plug-in as such: mvn -Declipse.useProjectReferences=false eclipse:eclipse
> mvn eclipse:eclipse fails to merge resources
> --------------------------------------------
>
> Key: OODT-88
> URL: https://issues.apache.org/jira/browse/OODT-88
> Project: OODT
> Issue Type: Bug
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
> Attachments: OODT-88.2010-12-15.patch.txt
>
>
> issue explained here (versions of eclipse plugin, 2.7 and above, causes build
> error):
> http://jira.codehaus.org/browse/MECLIPSE-576
> my purposed fix is adding the following to core/pom.xml:
> {noformat}
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <version>2.6</version>
> </plugin>
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
