You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Bram de Kruijff (Updated) (JIRA)" <ji...@apache.org> on 2011/11/23 15:01:40 UTC

[jira] [Updated] (FELIX-3241) Fileinstall metatype artifactInstaller

     [ https://issues.apache.org/jira/browse/FELIX-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bram de Kruijff updated FELIX-3241:
-----------------------------------

    Attachment: fileinstall.metatype.zip

Attached initial code. Some notes on the work in progress:
* no writeback to files on disk ala ConfigInstaller yet (do we need it?
* rather crude filename scoped drop/create for updates (could be more suble)
                
> Fileinstall metatype artifactInstaller
> --------------------------------------
>
>                 Key: FELIX-3241
>                 URL: https://issues.apache.org/jira/browse/FELIX-3241
>             Project: Felix
>          Issue Type: New Feature
>          Components: File Install
>            Reporter: Bram de Kruijff
>         Attachments: fileinstall.metatype.zip
>
>
> At the Amdatu project we need a way to use metatype configuration files in conjunction with fileinstall. We use metatype for provisioning using autoconf deployment based on Apache Ace. In some (development) cases however we also use fileinstall to supply configuration and it makes no sense for us to use cfg file there.
> To support this we created a fileinstall ArtifactInstaller extension that handles metatype. It's roughly modeled after the configinstaller andf autoconf code. As it is a rather generic use case we would be happy to transfer the code to Apache Felix.
> I'll attach the initial code. If there is interest in adopting this I'de be happy to update it.

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

        

Re: [jira] [Updated] (FELIX-3241) Fileinstall metatype artifactInstaller

Posted by Marcel Offermans <ma...@luminis.nl>.
Being involved in both ACE and Amdatu, I agree it is generic enough to be of use to a wider audience. I would like to learn what others think about this. Is this something we should accept?

Greetings, Marcel

On Nov 23, 2011, at 15:01 PM, Bram de Kruijff (Updated) (JIRA) wrote:

>     [ https://issues.apache.org/jira/browse/FELIX-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Bram de Kruijff updated FELIX-3241:
> -----------------------------------
> 
>    Attachment: fileinstall.metatype.zip
> 
> Attached initial code. Some notes on the work in progress:
> * no writeback to files on disk ala ConfigInstaller yet (do we need it?
> * rather crude filename scoped drop/create for updates (could be more suble)
> 
>> Fileinstall metatype artifactInstaller
>> --------------------------------------
>> 
>>                Key: FELIX-3241
>>                URL: https://issues.apache.org/jira/browse/FELIX-3241
>>            Project: Felix
>>         Issue Type: New Feature
>>         Components: File Install
>>           Reporter: Bram de Kruijff
>>        Attachments: fileinstall.metatype.zip
>> 
>> 
>> At the Amdatu project we need a way to use metatype configuration files in conjunction with fileinstall. We use metatype for provisioning using autoconf deployment based on Apache Ace. In some (development) cases however we also use fileinstall to supply configuration and it makes no sense for us to use cfg file there.
>> To support this we created a fileinstall ArtifactInstaller extension that handles metatype. It's roughly modeled after the configinstaller andf autoconf code. As it is a rather generic use case we would be happy to transfer the code to Apache Felix.
>> I'll attach the initial code. If there is interest in adopting this I'de be happy to update it.
> 
> --
> 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
> 
>