You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (Created) (JIRA)" <ji...@apache.org> on 2011/10/21 12:38:32 UTC

[jira] [Created] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

features.xml dropped into deploy BEFORE karaf is started are not recognised
---------------------------------------------------------------------------

                 Key: KARAF-953
                 URL: https://issues.apache.org/jira/browse/KARAF-953
             Project: Karaf
          Issue Type: Bug
          Components: karaf-features
    Affects Versions: 2.2.4, 3.0.0
            Reporter: Andreas Pieber
             Fix For: 2.2.5, 3.0.0


a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.

I'm convinced that behavior b) isn't planed but rather a bug...

I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider updated KARAF-953:
--------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0
    
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.1.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear closed KARAF-953.
--------------------------------

    
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.1.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Ioannis Canellos (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos resolved KARAF-953.
------------------------------------

    Resolution: Cannot Reproduce

This one is getting pretty old and I couldn't reproduce it and I think Andreas either (after reporting it).
                
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.1.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

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

Andreas Pieber reopened KARAF-953:
----------------------------------


wrong target versions
                
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Andreas Pieber (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228001#comment-13228001 ] 

Andreas Pieber commented on KARAF-953:
--------------------------------------

nope, it seams to work now; pretty strange... seams to be some other issue cross-referencing with this one...
                
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.1.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Ioannis Canellos (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133969#comment-13133969 ] 

Ioannis Canellos commented on KARAF-953:
----------------------------------------

Tried to reproduce it both using 2.2.5-SNAPSHOT and 3.0.0-SNAPSHTO and couldn't.
                
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-features
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.5, 3.0.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

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

Andreas Pieber closed KARAF-953.
--------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.2.6)
                       (was: 3.1.0)
    
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Ioannis Canellos (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos reassigned KARAF-953:
--------------------------------------

    Assignee: Ioannis Canellos
    
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-features
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.5, 3.0.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (KARAF-953) features.xml dropped into deploy BEFORE karaf is started are not recognised

Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated KARAF-953:
---------------------------------

    Fix Version/s:     (was: 2.2.5)
                   2.2.6

Bump to 2.2.6.
                
> features.xml dropped into deploy BEFORE karaf is started are not recognised
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-953
>                 URL: https://issues.apache.org/jira/browse/KARAF-953
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-features
>    Affects Versions: 2.2.4, 3.0.0
>            Reporter: Andreas Pieber
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.6, 3.0.0
>
>
> a) If you copy a features.xml to the deploy folder AFTER karaf had been started it registeres the features.xml and starts all features; 
> b) if you copy a features.xml to the deploy folder BEFORE karaf had been started the feature file is simply ignored.
> I'm convinced that behavior b) isn't planed but rather a bug...
> I've not tested the behavior by now on the master but I expect it to be the same there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira