You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2009/01/05 17:25:44 UTC
[jira] Commented: (LUCENE-1511) Improve Java packages (remove
shared/split packages, refactore naming scheme)
[ https://issues.apache.org/jira/browse/LUCENE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660808#action_12660808 ]
Otis Gospodnetic commented on LUCENE-1511:
------------------------------------------
Perhaps this should have been brough up on java-dev first...
How does one deal with package private classes/methods then?
> Improve Java packages (remove shared/split packages, refactore naming scheme)
> -----------------------------------------------------------------------------
>
> Key: LUCENE-1511
> URL: https://issues.apache.org/jira/browse/LUCENE-1511
> Project: Lucene - Java
> Issue Type: Wish
> Components: contrib/*, Search
> Affects Versions: 2.4
> Reporter: Gunnar Wagenknecht
>
> I recently prepared Lucene OSGi bundles for the Eclipse Orbit repository. During the preparation I discovered that some packages (eg. org.apache.lucene.search) are shared between different JARs, i.e. the package is in Lucene Core and in a contrib lib. While this is perfectly fine, it just makes OSGi packaging more complex and complexity also has a higher potential for errors.
> Thus, my wish for a Lucene 3.0 would be to rename some packages. For example, all contribs/extensions could be moved into their own package namespace.
> (Apologize if this has been reported elsewhere. I did a search in JIRA but did not find a similar issue.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org