You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jerker Klang (JIRA)" <ji...@codehaus.org> on 2006/05/14 16:06:41 UTC
[jira] Created: (MWAR-38) Plugin does not properly handle
dependency types.
Plugin does not properly handle dependency types.
-------------------------------------------------
Key: MWAR-38
URL: http://jira.codehaus.org/browse/MWAR-38
Project: Maven 2.x War Plugin
Type: Bug
Versions: 2.0
Environment: Maven 2.0.4 on Windows
Reporter: Jerker Klang
Priority: Blocker
When having a project with dependencies of ejb/ejb-client type they get their type as extension when included.
I have a project with a dependency to a 1.0-SNAPSHOT version of type ejb-client. When running the dependency gets included as WEB-INF/lib/myDependency-1.0-SNAPSHOT.ejb-client (the same happens with ejbs, they get .ejb as extension).
Running the same build but with 2.0-beta2 the problem is no longer there.
Needless to say, the plugin is now useless for many J2EE circumstances.
--
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: (MWAR-38) Plugin does not properly handle
dependency types.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-38?page=comments#action_65360 ]
Brett Porter commented on MWAR-38:
----------------------------------
caused by MWAR-7 patch.
> Plugin does not properly handle dependency types.
> -------------------------------------------------
>
> Key: MWAR-38
> URL: http://jira.codehaus.org/browse/MWAR-38
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven 2.0.4 on Windows
> Reporter: Jerker Klang
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0.1
>
>
> When having a project with dependencies of ejb/ejb-client type they get their type as extension when included.
> I have a project with a dependency to a 1.0-SNAPSHOT version of type ejb-client. When running the dependency gets included as WEB-INF/lib/myDependency-1.0-SNAPSHOT.ejb-client (the same happens with ejbs, they get .ejb as extension).
> Running the same build but with 2.0-beta2 the problem is no longer there.
> Needless to say, the plugin is now useless for many J2EE circumstances.
--
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: (MWAR-38) Plugin does not properly handle
dependency types.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-38?page=all ]
Brett Porter updated MWAR-38:
-----------------------------
Assign To: Brett Porter
Fix Version: 2.0.1
> Plugin does not properly handle dependency types.
> -------------------------------------------------
>
> Key: MWAR-38
> URL: http://jira.codehaus.org/browse/MWAR-38
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven 2.0.4 on Windows
> Reporter: Jerker Klang
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0.1
>
>
> When having a project with dependencies of ejb/ejb-client type they get their type as extension when included.
> I have a project with a dependency to a 1.0-SNAPSHOT version of type ejb-client. When running the dependency gets included as WEB-INF/lib/myDependency-1.0-SNAPSHOT.ejb-client (the same happens with ejbs, they get .ejb as extension).
> Running the same build but with 2.0-beta2 the problem is no longer there.
> Needless to say, the plugin is now useless for many J2EE circumstances.
--
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] Closed: (MWAR-38) Plugin does not properly handle dependency
types.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-38?page=all ]
Brett Porter closed MWAR-38:
----------------------------
Resolution: Fixed
> Plugin does not properly handle dependency types.
> -------------------------------------------------
>
> Key: MWAR-38
> URL: http://jira.codehaus.org/browse/MWAR-38
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven 2.0.4 on Windows
> Reporter: Jerker Klang
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0.1
>
>
> When having a project with dependencies of ejb/ejb-client type they get their type as extension when included.
> I have a project with a dependency to a 1.0-SNAPSHOT version of type ejb-client. When running the dependency gets included as WEB-INF/lib/myDependency-1.0-SNAPSHOT.ejb-client (the same happens with ejbs, they get .ejb as extension).
> Running the same build but with 2.0-beta2 the problem is no longer there.
> Needless to say, the plugin is now useless for many J2EE circumstances.
--
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