[ 
https://issues.apache.org/jira/browse/GERONIMO-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055348#comment-13055348
 ] 

David Jencks commented on GERONIMO-5764:
----------------------------------------

I'm -1 on the additional bundle-records.csv file.  We already have the karaf 
startup.properties file which lists the bundles that will still get started 
after a clean.  Why do we need another file with apparently the same purpose?

I also am not sure that we should let people osgi uninstall such persistent 
bundles and have it mean that they will no longer be started on the next server 
start.  If you osgi uninstall a bundle listed in startup.properties it will 
still get started the next time the server starts.  I think there should be an 
explicit command to take the bundle out of startup.properties.

I think that modifying what the server looks like after a clean is a big deal 
and we should avoid introducing more ways to make such changes and discourage 
people from making such changes to an existing server.


> Support Bundles Deployment in deployment command line
> -----------------------------------------------------
>
>                 Key: GERONIMO-5764
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5764
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: commands, console, deployment
>    Affects Versions: 3.0
>            Reporter: viola.lu
>            Assignee: Rex Wang
>            Priority: Critical
>             Fix For: 3.0
>
>         Attachments: GERONIMO-5764-install-bundle.patch, 
> GERONIMO-5764-record-bundle.patch, GERONIMO-5764.patch
>
>
> Now we have to deploy a regular bundle via karaf shell: osgi:install 
> file:/[bunlde_path], not deployer command line, so open this jira to track 
> this feature enablement.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to