[ 
http://jira.codehaus.org/browse/MECLIPSE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214705#action_214705
 ] 

Ramon Buckland commented on MECLIPSE-645:
-----------------------------------------

So I would like to +1 this request, but I have a different need for it.

Currently, to add a src/main/scala path to Eclipse. We have to use the 
build-helper-maven plugin (Michael Wenig - This is how you can acheieve today 
what you need). 

(See - http://scala-tools.org/mvnsites/maven-scala-plugin/faq.html)

However it would be nicer to have simpler concise config for this task. 

Scala and Java source files can co-exist in the same maven project and both be 
compiled and result in a single jar.

(See http://scala-tools.org/mvnsites/maven-scala-plugin/usage_java.html)

pom.xml
src/main/java
src/main/scala

The Maven Eclipse Plugin has no means of "adding" that src/main/scala source 
folder to the Eclipse .classpath file. So we either do it manually or through 
eclipse.

What I propose is the ability to add new src entries, as required:

<additonalClasspathSourceEntries>
  <entry>
    <path>src/main/scala</path>
    <includes>**/*.scala</includes>
    <excludes>**/*.java</excludes>
  </entry>
</addtionalClassPathSourceEntry>


In this way, when there is a source folder that eclipse can support, and the 
maven project has it, alongside of standard java classes, we can add them in as 
required, neatly.



> Ability to add extra resource folders only to the eclipse .classpath (and not 
> to the maven build)
> -------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-645
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-645
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.8
>            Reporter: Michael Wenig
>
> We have - in nearly every project - some resources which should only be used 
> during development inside eclipse - but should not be included in the central 
> maven builds.
> These are for example configuration-properties, log-configs etc. which are 
> only used by the developers as they are replaced and externally stored on 
> every other system (testing and prod).
> Actually we are storing them in a folder src/main/resources-local which is 
> NOT mentioned in the pom so maven ignores that. Then we have to manually add 
> this folder as a source folder after each regeneration of the project 
> configuration.
> It would be great if this could be configured in the maven-eclipse-plugin so 
> it is added automatically.
> We may NOT define this as a maven-resource at this would bring these files 
> into the productive artifact.

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

        

Reply via email to