[
https://issues.apache.org/jira/browse/SOLR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-135:
--------------------------
Attachment: SOLR-135-RestructureForCommonJar.patch
as far as i can tell the manifest merging that the ant docs describe for the
<jar> task just flat out don't work, so we just wont use the new macro for hte
post.jar
NOTE: with this patch, the intent is to svn copy XML.java to the new common
dir, then patch the existing file to purge it's body and add the deprecated
messages.
as i mentioned before, this appraoch doesn't use src/common at all ... it
assumes a new "org.apache.solr.common" package in src/java and uses
include/exclude rules to make sure things in that package live in the common
jar (and compile first)
it would be easy to move this package to live in src/common if people think
there is a need, my main concern is just that we shouldn't have
"org.apache.solr.util" living in two places (src/java and src/common)
> Restructure / Refactor codebase for shared libraries
> ----------------------------------------------------
>
> Key: SOLR-135
> URL: https://issues.apache.org/jira/browse/SOLR-135
> Project: Solr
> Issue Type: Wish
> Reporter: Ryan McKinley
> Priority: Minor
> Attachments: SOLR-135-RestructureForCommonJar.patch,
> SOLR-135-RestructureForCommonJar.patch, SOLR-135-RestructureForCommonJar.patch
>
>
> For SOLR-20 and other java projects, it would be nice to have common code
> share a codebase that does not require lucene or junit to compile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
