[ http://issues.apache.org/jira/browse/YOKO-149?page=all ]
Alan Cabrera updated YOKO-149:
------------------------------
Fix Version/s: 1.0-incubating-M1
> Generating an eclipse project is broken with the addition of NOTICE, LICENSE
> and DISCLAIMER files.
> --------------------------------------------------------------------------------------------------
>
> Key: YOKO-149
> URL: http://issues.apache.org/jira/browse/YOKO-149
> Project: Yoko - CORBA Server
> Issue Type: Bug
> Affects Versions: 1.0-incubating-M1
> Reporter: Edell Nolan
> Fix For: 1.0-incubating-M1
>
>
> From Dan Kulp:
> With the addition of the NOTICE, LICENSE and DISCLAIMER text files into "."
> for each project, you can no longer easily generate a working eclipse
> project. What happens if you run "mvn eclipse:eclipse", you get a .classpath
> file that
> has:
> <classpathentry kind="src" path="." output="target/classes/META-INF"/>
> <classpathentry kind="src" path="src/main/java"/>
> The second "src" dir is a subdir of the first and eclipse barfs about that.
> There really are a couple options:
> 1) Move the files to a more "maven friendly" location: src/java/resources
> 2) Move them to something like "./etc" or "./notices" or something so that
> the normal maven dirs are not subdirs.
> 3) Add an "eclipse" profile that changes notice.dir property to something
> else
> so eclipse won't see those files. However, your docs will need to be
> updated to say you need to do "mvn -Peclipse eclipse:eclipse"
> 4) Update docs to say you need to run:
> mvn eclipse:eclipse -Dnotice.dir=src/java/resources
> Anyway, just thought I'd mention it so someone can figure out a good fix.
> FYI: Tuscany went with #3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
