[
https://jira.codehaus.org/browse/MEAR-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346104#comment-346104
]
Stéphane Nicoll edited comment on MEAR-186 at 5/12/14 6:32 AM:
---------------------------------------------------------------
It's not a bug, it's intentional. The only reason why this one is not closed as
won't fix (as MEAR-82) is because you have an additional requirement of having
several resource directories.
{{mvn ear:ear}} can be ran in a non-ear project (with packaging type whatever).
{{<packaging>ear</packaging}} is just a way to bind the plugin at the proper
phase automatically. Since day one, the EAR plugin has been built with a
dedicated resource directory. It has never been the plan to use the "resources"
part so that's why it does not qualify as a bug.
That being said, if you have several directories, it turns out to be more
painful than it should.
was (Author: sni):
It's not a bug, it's intentional. The only reason why this one is not closed as
won't fix (as MEAR-82) is because you have an additional requirement of having
several resources directory.
{{mvn ear:ear}} can be ran in a non-ear project (with packaging type whatever).
{{<packaging>ear</packaging}} is just a way to bind the plugin at the proper
phase automatically. Since day one, the EAR plugin has been built with a
dedicated resource directory. It has never been the plan to use the "resources"
part so that's why it does not qualify as a bug.
That being said, if you have several directories, it turns out to be more
painful than it should.
> Source and Resource Directories are Ignored
> -------------------------------------------
>
> Key: MEAR-186
> URL: https://jira.codehaus.org/browse/MEAR-186
> Project: Maven Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.9
> Environment: Ubuntu 13.10
> Reporter: Thomas Beauvais
> Attachments: pom.xml
>
>
> Due to an odd necessity for different source and resource directories because
> of using another IDE that can't be configued (JDeveloper).
> When running the EAR plugin, I expect the <resources/> to be included in the
> base of the EAR file.
> <build>
> <sourceDirectory>src</sourceDirectory>
> <resources>
> <resource>
> <directory>.adf</directory>
> </resource>
> </resources>
> ...
> </build>
> Here is the project tree:
> ./src
> ./src/META-INF
> ./src/META-INF/jps-config.xml
> ./src/META-INF/weblogic-application.xml
> ./.adf
> ./.adf/META-INF
> ./.adf/META-INF/adf-config.xml
> ./.adf/META-INF/connections.xml
> ./pom.xml
> Here is the contents of the EAR:
> META-INF/
> META-INF/MANIFEST.MF
> META-INF/application.xml
> web-0.0.1-SNAPSHOT.war
> META-INF/maven/
> META-INF/maven/org.my.company/
> META-INF/maven/org.my.company/ssxa/
> META-INF/maven/org.my.company/ssxa/pom.xml
> META-INF/maven/org.my.company/ssxa/pom.properties
> Notice, it doesn't include either the source or the resources. I know that I
> can include a <earSourceDirectory/> but this only allows for a single
> directory and I have two (.adf and src).
> Attached is the pom.xml used.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
