[ http://jira.codehaus.org/browse/MECLIPSE-117?page=all ]
Jeevan Sunkersett closed MECLIPSE-117:
--------------------------------------
Resolution: Incomplete
> MVN generated .project and .classpath files have to be tweaked before using
> ---------------------------------------------------------------------------
>
> Key: MECLIPSE-117
> URL: http://jira.codehaus.org/browse/MECLIPSE-117
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Environment: Windows XP
> Eclipse SDK Version: 3.1.0 Build id: I20050627-1435
> Maven 2.0.3
> JDK 1.4.2/ JDK 1.5
> Reporter: Jeevan Sunkersett
>
>
> Hi,
> I am not sure if this classifies as a BUG, but nevertheless...
> My projects are all Maven 2 compliant (migrated from Maven 1).
> I executed the mvn eclipse:eclipse command to generate the .classpath and
> .project files.
> They got generated but could not be used without manually editing them.
> For instance I have a project named "common" in a folder \common but the name
> in the generated .project file is SOMESUFFIX-common <the folder name and the
> project-name does not match.
> Because of this the project cannot be imported into Eclipse 3.1.
> The name and the folder have to be the same for a sucessful import.
> (please see eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=143757)
> The generated .classpath files also need to be edited manually.
> When the projects are imported they report errors like
> The errors are like:
> Cannot nest output folder
> 'eq_web_domain/target/classes/images/js/css/META-INF' inside output folder
> 'eq_web_domain/target/classes/images/js/css'
> Cannot nest 'alpha_reporter/src/main/resources/DEV' inside
> 'alpha_reporter/src/main/resources'.
> To enable the nesting exclude 'DEV/' from 'alpha_reporter/src/main/resources'
> These get resolved by having the excluding attribute in <classpathentry> in
> the .classpath.
> For e.g.
> <classpathentry excluding="DEV/" kind="src"
> path="src/main/resources"/>
> But this is missed by the maven eclipse plugin.
> FYA
> ~g1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
