You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/06/21 18:10:53 UTC

[jira] Closed: (MNG-500) EJB client not included in installation

     [ http://jira.codehaus.org/browse/MNG-500?page=all ]
     
John Casey closed MNG-500:
--------------------------

    Resolution: Fixed

sort of a hack of a fix. we may need some better component support to decide whether things are binary dependencies or not in the future. Currently, filtering "tld".equals(artifact.getType()) to TLD dir, "pom".equals(artifact.getType()) to nowhere (would only be there for dependency inclusion), and everything else to LIB dir.

This is definitely NOT elegant.

> EJB client not included in installation
> ---------------------------------------
>
>          Key: MNG-500
>          URL: http://jira.codehaus.org/browse/MNG-500
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugins
>     Versions: 2.0-alpha-3
>  Environment: Windows XP SP2, J2SE 5.0
>     Reporter: Nathaniel Stoddard
>     Assignee: John Casey
>      Fix For: 2.0-alpha-3

>
>
> When a dependency of type "ejb-client" is specified for a project, the project successfully builds, but the ejb-client JAR is not included in the installation.  (Example: WAR project will successfully build, but the ejb-client JAR is not found in /WEB-INF/lib once installed into the local repository.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org