[jira] Created: (MPRAR-4) Do not bundle dependecies in rar without scope=provided

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (MPRAR-4) Do not bundle dependecies in rar without scope=provided

JIRA jira@codehaus.org
Do not bundle dependecies in rar  without scope=provided
--------------------------------------------------------

         Key: MPRAR-4
         URL: http://jira.codehaus.org/browse/MPRAR-4
     Project: maven-rar-plugin
        Type: New Feature

 Environment: Maven 2.0.4, rar plugin 2.2
    Reporter: Carsten Karkola


If I use "provided" the dependencies will never be included, my problem is
1. projects:
  my-jar
  rar1: dependency to my-jar
  rar2: dependency to my-jar
  ejb1: dependency to my-jar
  ear: dependency to rar1, rar2. ejb1
2. inside the ear:
    ejb1.jar
    rar1.rar
    rar2.rar
    lib/my-jar.jar
3. This works fine for packaging=ejb - the my-jar.jar gets copied to the lib dir during build of
the ear. But the same jar gets also packaged in the rar1 and in the rar2 archive. So I have it
three times instead only having the entries in MANFIFEST.MF/Class-Path and the jar only
once in the lib subdir.
The Manifest entries are not the problem, to get the jar not packaged in the rars is my
problem.

4. my proposal:
add plugin configuration parameter  <includeDependencies>false</includeDependencies>

in RarMojo.java additional parameter and check:

    /**
     * Specify if the specified dependencies of this project should be
     * included in the rar file ; default is true.
     *
     * @parameter
     */
  private Boolean includeDependencies = Boolean.TRUE;

....
        // Copy dependencies
        try
        {
            if (includeDependencies.booleanValue()) {  // additional check

carsten

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MPRAR-4) Do not bundle dependecies in rar without scope=provided

JIRA jira@codehaus.org
    [ http://jira.codehaus.org/browse/MPRAR-4?page=comments#action_66497 ]

Carsten Karkola commented on MPRAR-4:
-------------------------------------

It is the wrong rar plugin, sorry. I try to move this issue to the rar-plugin for mvn 2.x

> Do not bundle dependecies in rar  without scope=provided
> --------------------------------------------------------
>
>          Key: MPRAR-4
>          URL: http://jira.codehaus.org/browse/MPRAR-4
>      Project: maven-rar-plugin
>         Type: New Feature

>  Environment: Maven 2.0.4, rar plugin 2.2
>     Reporter: Carsten Karkola

>
>
> If I use "provided" the dependencies will never be included, my problem is
> 1. projects:
>   my-jar
>   rar1: dependency to my-jar
>   rar2: dependency to my-jar
>   ejb1: dependency to my-jar
>   ear: dependency to rar1, rar2. ejb1
> 2. inside the ear:
>     ejb1.jar
>     rar1.rar
>     rar2.rar
>     lib/my-jar.jar
> 3. This works fine for packaging=ejb - the my-jar.jar gets copied to the lib dir during build of
> the ear. But the same jar gets also packaged in the rar1 and in the rar2 archive. So I have it
> three times instead only having the entries in MANFIFEST.MF/Class-Path and the jar only
> once in the lib subdir.
> The Manifest entries are not the problem, to get the jar not packaged in the rars is my
> problem.
> 4. my proposal:
> add plugin configuration parameter  <includeDependencies>false</includeDependencies>
> in RarMojo.java additional parameter and check:
>     /**
>      * Specify if the specified dependencies of this project should be
>      * included in the rar file ; default is true.
>      *
>      * @parameter
>      */
>   private Boolean includeDependencies = Boolean.TRUE;
> ....
>         // Copy dependencies
>         try
>         {
>             if (includeDependencies.booleanValue()) {  // additional check
> carsten

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

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (MPRAR-4) Do not bundle dependecies in rar without scope=provided

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org
     [ http://jira.codehaus.org/browse/MPRAR-4?page=all ]
     
Lukas Theussl closed MPRAR-4:
-----------------------------

    Resolution: Duplicate

> Do not bundle dependecies in rar  without scope=provided
> --------------------------------------------------------
>
>          Key: MPRAR-4
>          URL: http://jira.codehaus.org/browse/MPRAR-4
>      Project: maven-rar-plugin
>         Type: New Feature

>  Environment: Maven 2.0.4, rar plugin 2.2
>     Reporter: Carsten Karkola

>
>
> If I use "provided" the dependencies will never be included, my problem is
> 1. projects:
>   my-jar
>   rar1: dependency to my-jar
>   rar2: dependency to my-jar
>   ejb1: dependency to my-jar
>   ear: dependency to rar1, rar2. ejb1
> 2. inside the ear:
>     ejb1.jar
>     rar1.rar
>     rar2.rar
>     lib/my-jar.jar
> 3. This works fine for packaging=ejb - the my-jar.jar gets copied to the lib dir during build of
> the ear. But the same jar gets also packaged in the rar1 and in the rar2 archive. So I have it
> three times instead only having the entries in MANFIFEST.MF/Class-Path and the jar only
> once in the lib subdir.
> The Manifest entries are not the problem, to get the jar not packaged in the rars is my
> problem.
> 4. my proposal:
> add plugin configuration parameter  <includeDependencies>false</includeDependencies>
> in RarMojo.java additional parameter and check:
>     /**
>      * Specify if the specified dependencies of this project should be
>      * included in the rar file ; default is true.
>      *
>      * @parameter
>      */
>   private Boolean includeDependencies = Boolean.TRUE;
> ....
>         // Copy dependencies
>         try
>         {
>             if (includeDependencies.booleanValue()) {  // additional check
> carsten

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