maven.eclipse.project.name not supported and handling of non existing
maven.eclipse.classpath.include's.
--------------------------------------------------------------------------------------------------------
Key: MPECLIPSE-116
URL: http://jira.codehaus.org/browse/MPECLIPSE-116
Project: maven-eclipse-plugin
Type: Bug
Versions: 1.10
Reporter: Tsolak Petrosian
1. It seems the maven.eclipse.project.name is not handled anywhere in
project.jelly and is ignored by "maven eclipse" goal.
I added the following to project.jelly:
<!-- CUSTOM CODE TO SET CUSTOME PROJECT NAME IF NOT NULL -->
<j:set var="eclipse_project_name" value="${maven.eclipse.project.name}"/>
<j:if test="${eclipse_project_name != null}">
<name>${eclipse_project_name}</name>
</j:if>
<j:if test="${eclipse_project_name == null}">
<name>${pom.artifactId}</name>
</j:if>
before <comment>${pom.description}</comment> ....
2. Eclipse gives error on source path which was included by plugin but does not
physically exist.
I added the following to classpath.jelly to handle non existing paths:
<!-- add extra directories to be included in the classpath -->
<j:forEach var="res" items="${maven.eclipse.classpath.include.split}">
<maven:makeRelativePath var="srcDir" basedir="${basedir}" path="${res}"
separator="/" />
<u:file var="srcDirFile" name="${srcDir}" />
<j:if test="${ srcDirFile.exists() }" >
<classpathentry kind="src" path="${srcDir}" />
</j:if>
</j:forEach>
before <maven:get var="cactusSrcDir" plugin='cactus-maven'
property='cactus.src.dir' />......
--
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
