You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/02/01 01:31:08 UTC

[jira] Created: (BUILDR-34) Support expanded packaging

Support expanded packaging
--------------------------

                 Key: BUILDR-34
                 URL: https://issues.apache.org/jira/browse/BUILDR-34
             Project: Buildr
          Issue Type: New Feature
          Components: Packaging
            Reporter: Assaf Arkin


Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.

One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (BUILDR-34) Support expanded packaging

Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Assaf Arkin updated BUILDR-34:
------------------------------

    Fix Version/s: 1.3.1

> Support expanded packaging
> --------------------------
>
>                 Key: BUILDR-34
>                 URL: https://issues.apache.org/jira/browse/BUILDR-34
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Assaf Arkin
>             Fix For: 1.3.1
>
>
> Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.
> One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-34) Support expanded packaging

Posted by "Shane Witbeck (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564746#action_12564746 ] 

Shane Witbeck commented on BUILDR-34:
-------------------------------------

Another use case that I had in mind for this is using the expanded directory of an EAR or WAR during development. This makes UI (editing JSP's, etc.) work and hot deploys go much faster when running the code in a local container.

> Support expanded packaging
> --------------------------
>
>                 Key: BUILDR-34
>                 URL: https://issues.apache.org/jira/browse/BUILDR-34
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Assaf Arkin
>
> Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.
> One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (BUILDR-34) Support expanded packaging

Posted by "Victor Hugo Borja (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Victor Hugo Borja updated BUILDR-34:
------------------------------------

    Attachment: 0002-Made-WAR-and-EAR-packages-expandable.patch

Implemented using PackagingType feature from BUILDR-46

> Support expanded packaging
> --------------------------
>
>                 Key: BUILDR-34
>                 URL: https://issues.apache.org/jira/browse/BUILDR-34
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Assaf Arkin
>             Fix For: 1.3.1
>
>         Attachments: 0002-Made-WAR-and-EAR-packages-expandable.patch
>
>
> Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.
> One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (BUILDR-34) Support expanded packaging

Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Assaf Arkin updated BUILDR-34:
------------------------------

    Fix Version/s:     (was: 1.3.1)

> Support expanded packaging
> --------------------------
>
>                 Key: BUILDR-34
>                 URL: https://issues.apache.org/jira/browse/BUILDR-34
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Assaf Arkin
>         Attachments: 0002-Made-WAR-and-EAR-packages-expandable.patch
>
>
> Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.
> One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-34) Support expanded packaging

Posted by "Victor Hugo Borja (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565390#action_12565390 ] 

Victor Hugo Borja commented on BUILDR-34:
-----------------------------------------

I've submitted a patch for this at http://issues.apache.org/jira/browse/BUILDR-26?focusedCommentId=12565358#action_12565358

Tested creating expanded WAR, EAR (with expanded WAR within), EAR expanded. 

> Support expanded packaging
> --------------------------
>
>                 Key: BUILDR-34
>                 URL: https://issues.apache.org/jira/browse/BUILDR-34
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Packaging
>            Reporter: Assaf Arkin
>             Fix For: 1.3.1
>
>
> Currently, packaging (JAR, WAR, etc) uses all the included files to create a Zip package, but there's no intermediary expanded form.  For example, to run a Web app from the expanded WAR.
> One possible implementation: adding an option to ZipTask that will layout the files in a temporary directory and compress that.  This can be used for different packaging types, also for tweaking package manifests when building an EAR. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.