[ 
https://issues.apache.org/jira/browse/SOLR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504009
 ] 

Hoss Man commented on SOLR-135:
-------------------------------

one the topic of adding a src/common directory ... i think in the long run 
we'll be happier if there is no overlap in the java package names that live in 
this directory and the ones that live in src/java (much the way the only java 
packages in src/webapp are o.a.s.servlet) ... so using 
src/common/org/apache/solr/common/XML.java may be a better way to go (even 
though it means we would need to leave a deprecated 
src/java/org/apache/solr/util/XML.java subclassing it in src/java)  I could 
probably be convinced that this isn't that important, but i've definitely found 
it confusing for people that some of the lucene-java contribs reuse the same 
package names as the core classes in some cases)

on the subject of the build.xml ... now that we've got three instances of 
<javac> and two of <jar> we probably want to make some macros for them to 
reduce redundency.

Gimme 30 minutes to see if i can whip up a derivitive patch ... if i dont' 
attach one it means i got sidetracked with something else.

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

Reply via email to