[ https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042232#comment-13042232
]
Ryan McKinley commented on LUCENE-1344:
---------------------------------------
bq. Can you maintain two different binaries
Not sure what that means... are you asking if Apache will release two versions of the same
thing? If so, no.
The maven integration is an officially unsupported developer build tool, so will not be part
of the official release -- but it does let someone easily build OSGi bundles, so it is a good
step forward. If there is an ant way to do this, that could become part of the official release
process.
> Make the Lucene jar an OSGi bundle
> ----------------------------------
>
> Key: LUCENE-1344
> URL: https://issues.apache.org/jira/browse/LUCENE-1344
> Project: Lucene - Java
> Issue Type: Improvement
> Components: general/build
> Reporter: Nicolas Lalevée
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 3.3, 4.0
>
> Attachments: LUCENE-1344-3.0-branch.patch, LUCENE-1344-maven.patch, LUCENE-1344-r679133.patch,
LUCENE-1344-r690675.patch, LUCENE-1344-r690691.patch, LUCENE-1344-r696747.patch, LUCENE-1344.patch,
LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch,
MANIFEST.MF.diff, lucene_trunk.patch
>
>
> In order to use Lucene in an OSGi environment, some additional headers are needed in
the manifest of the jar. As Lucene has no dependency, it is pretty straight forward and it
ill be easy to maintain I think.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
|