[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

["Juraj Burian (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MPECLIPSE-63?page=comments#action_41705 ] 

Juraj Burian commented on MPECLIPSE-63:
---------------------------------------

Please folks is there chance fix this problem or not?
I see lot of reason to have javanature and javabuilder included optional.
Namely,  for example javabuilder is not necessary when project is compiled by another builder.
Next, we have problems with the order in natures and buildSpec blocks in RAD.

So I am thing that best way is add property like : maven.eclipse.defaultbuilder
and do modification of project.jelly file like this:

<j:set var="addDefaultBuilder" value="${maven.eclipse.defaultbuilder}"/>
<j:if test="${addDefaultBuilder != 'false'}">
   <buildCommand>
       <name>org.eclipse.jdt.core.javabuilder</name>
       <arguments>
       </arguments>
  </buildCommand>
</j:if>

Similar convention  should be ok. for javanature ....

> dont want the hardcoded org.eclipse.jdt.core.javabuilder
> --------------------------------------------------------
>
>          Key: MPECLIPSE-63
>          URL: http://jira.codehaus.org/browse/MPECLIPSE-63
>      Project: maven-eclipse-plugin
>         Type: Bug
>  Environment: XP
>     Reporter: Dan Tran
>      Fix For: 1.9

>
>
> There are cases that we dont want this plugin to be added org.eclipse.jdt.core.javabuilder automatically.
> The same for org.eclipse.jdt.core.javanature.
> Docu plugin does not need java builder and nature

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org