[
https://issues.apache.org/jira/browse/MECLIPSE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-645.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Ability to add extra resource folders only to the eclipse .classpath (and not
> to the maven build)
> -------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-645
> URL: https://issues.apache.org/jira/browse/MECLIPSE-645
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
