You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2009/10/23 00:07:59 UTC

[jira] Created: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
------------------------------------------------------------------------------

                 Key: SLING-1162
                 URL: https://issues.apache.org/jira/browse/SLING-1162
             Project: Sling
          Issue Type: Bug
          Components: Launchpad
            Reporter: Justin Edelson


If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.

This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.

I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Updated: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Felix Meschberger updated SLING-1162:
-------------------------------------

    Affects Version/s: Launchpad Base 2.0.4

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.0.4
>            Reporter: Justin Edelson
>            Assignee: Felix Meschberger
>             Fix For: Launchpad Base 2.0.6
>
>         Attachments: SLING-1162-corrected.patch, SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Closed: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Felix Meschberger closed SLING-1162.
------------------------------------


Released.

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.0.4
>            Reporter: Justin Edelson
>            Assignee: Felix Meschberger
>             Fix For: Launchpad Base 2.1.0
>
>         Attachments: SLING-1162-corrected.patch, SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Updated: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Justin Edelson updated SLING-1162:
----------------------------------

    Attachment: SLING-1162.patch

here's the patch.

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>            Reporter: Justin Edelson
>         Attachments: SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Updated: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Justin Edelson updated SLING-1162:
----------------------------------

    Attachment: SLING-1162-corrected.patch

The first patch I submitted was actually the reverse patch. Here's a corrected one.

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>            Reporter: Justin Edelson
>         Attachments: SLING-1162-corrected.patch, SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Assigned: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Felix Meschberger reassigned SLING-1162:
----------------------------------------

    Assignee: Felix Meschberger

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>            Reporter: Justin Edelson
>            Assignee: Felix Meschberger
>         Attachments: SLING-1162-corrected.patch, SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Updated: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Justin Edelson updated SLING-1162:
----------------------------------

    Issue Type: Improvement  (was: Bug)

whoops. not a bug.

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>            Reporter: Justin Edelson
>         Attachments: SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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


[jira] Resolved: (SLING-1162) force upgrading of SNAPSHOT bundles from inside app/webapp resources directory

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

Felix Meschberger resolved SLING-1162.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: Launchpad Base 2.0.6

Thanks for providing the patch.

I have committed your patch for BootstrapInstaller in Rev. 834077.

The reference update in the other modules has already been done by Bertrand as part of SLING-1177

> force upgrading of SNAPSHOT bundles from inside app/webapp resources directory
> ------------------------------------------------------------------------------
>
>                 Key: SLING-1162
>                 URL: https://issues.apache.org/jira/browse/SLING-1162
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.0.4
>            Reporter: Justin Edelson
>            Assignee: Felix Meschberger
>             Fix For: Launchpad Base 2.0.6
>
>         Attachments: SLING-1162-corrected.patch, SLING-1162.patch
>
>
> If a bundle file in WEB-INF/resources/bundles (in a webapp) or resources/bundles (in a standalone app) is a SNAPSHOT, the bundle should be upgraded if it is already installed and the versions match.
> This doesn't work consistently because isAlreadyInstalled() doesn't detect changes to bundles in an exploded webapp (e.g. with mvn jetty:run); you have to touch the launcher jar file to force the upgrade check to happen.
> I didn't come up with a good way to test this functionality. Open to suggestions...

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