[jira] Commented: (MEJB-32) Add set classifier to client classifier
[
http://jira.codehaus.org/browse/MEJB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=151052#action_151052
]
David Siefert commented on MEJB-32:
---
It's been over a month and the fix has not been integrated. Is
maven-ejb-plugin dead?
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
(classifier*was6*/classifier) or JBoss (classifier*jboss*/classifier)
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] 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
(classifier*was6*/classifier) or JBoss (classifier*jboss*/classifier)
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] Created: (MNG-3288) Invalid systemPath allows build to continue--failing in later phase.
Invalid systemPath allows build to continue--failing in later phase.
Key: MNG-3288
URL: http://jira.codehaus.org/browse/MNG-3288
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.7
Reporter: David Siefert
Priority: Minor
Attachments: systempath-issue.zip
When the system scoped dependency is specified as follows:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopesystem/scope
systemPath${env.USERPROFILE}/.m2/repository/junit/junit/3.8.1/junit-3.8.2.jar/systemPath
/dependency
Maven fails and complains correctly (junit-3.8.2.jar is incorrect, and should
be junit-3.8.1.jar).
However, when the following is used:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopesystem/scope
systemPath${env.USERPROFILE}/.m2/repository/junit/junit/systemPath
/dependency
Maven DOES NOT COMPLAIN, the build process proceeds and fails later in the
compile/testCompile build phases since the dependency is not available. You
can see attached minimal project.
FYI-This was tested on a Windows XP system, I have not yet tried to replicate
this issue on *nix.
--
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
