[jira] Updated: (MEJB-32) Add set classifier to client classifier
[
http://jira.codehaus.org/browse/MEJB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Siefert updated MEJB-32:
--
Attachment: MEJB32-fix.diff
Here is a fix! I need this same issue resolved. Updated test to reflect
change in client classifier inclusion.
> Add set classifier to client classifier
> ---
>
> Key: MEJB-32
> URL: http://jira.codehaus.org/browse/MEJB-32
> Project: Maven 2.x Ejb Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Libor Kramolis
> Attachments: MEJB32-fix.diff
>
>
> I user classifier to distinguish ejb artefact for IBM WAS
> (*was6*) or JBoss (*jboss*)
> and also I let ejb plugin to generate client.
> But now I can build 2 different ejb file for each deployment environment but
> it is not possible to distinguish what was client file generated for. There
> is no was6 or jboss in client jar file name.
> *I think ejb bodule should concatenate set classifier and "client" suffix to
> produce 4 different files for 2 different classifiers*, e.g:
> {quote}
> my-ejb-1.0.0-was6.jar
> my-ejb-1.0.0-was6-client.jar
> my-ejb-1.0.0-jboss.jar
> my-ejb-1.0.0-jboss-client.jar
> {quote}
--
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
[jira] Commented: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147932#action_147932
]
Olivier Lamy commented on MRESOURCES-8:
---
Good idea !
> maven-resources-plugin ignores configuration/resources property (add a new
> mojo to copy resources)
> --
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
>Affects Versions: 2.1, 2.2
>Reporter: Leszek Gawron
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
> target/generated-resources
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> {code}
> thing is this part:
> {code:xml}
>
>
> src/main/properties
> true
>
>
> {code}
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
> {code:xml}
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> {code}
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
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
[jira] Commented: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147930#action_147930
]
Benjamin Bentmann commented on MRESOURCES-8:
Oliver, given that users apparently cannot override the parameter {{resources}}
from the {{ResourcesMojo}}, should we mark it [EMAIL PROTECTED] to hide it from
the plugin docs and prevent future confusion?
> maven-resources-plugin ignores configuration/resources property (add a new
> mojo to copy resources)
> --
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
>Affects Versions: 2.1, 2.2
>Reporter: Leszek Gawron
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
> target/generated-resources
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> {code}
> thing is this part:
> {code:xml}
>
>
> src/main/properties
> true
>
>
> {code}
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
> {code:xml}
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> {code}
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
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
