[jbosstools-issues] [JBoss JIRA] (JBIDE-16370) evaluate creating OSGi bindex

Mickael Istria (JIRA) issues at jboss.org
Mon Feb 17 07:25:47 EST 2014


     [ https://issues.jboss.org/browse/JBIDE-16370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Istria updated JBIDE-16370:
-----------------------------------

    Description: 
Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
That would allow other projects doing OSGi but not p2 to consume Locus artifacts.

  was:
bindex is the standard for provisionning in OSGi < R5. It would be useful to provide bindex for locus (as well as p2 metadata) if we have some other OSGi projects at JBoss willing to consume some Locus bundles.

In a longer-term future, we can imagine that p2 conforms to OSGi standards


    
> evaluate creating OSGi bindex
> -----------------------------
>
>                 Key: JBIDE-16370
>                 URL: https://issues.jboss.org/browse/JBIDE-16370
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, locus
>            Reporter: Mickael Istria
>            Priority: Optional
>             Fix For: 4.2.x
>
>
> Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
> That would allow other projects doing OSGi but not p2 to consume Locus artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list