[
https://issues.apache.org/jira/browse/SOLR-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576353#action_12576353
]
Hoss Man commented on SOLR-498:
-------------------------------
from a developers perspective, the overhead of running "jar cf
solr/lib/myjar.jar classes/*" seems trival compared to the actual compilation
of the java code plus the restarting of the servlet container (or at a minimum:
reloading the war) so it hardly seems worthwhile for the debuging case.
if someone wants to submit a patch to allow more customizable configuration of
the plugin classloader, i won't object -- but it seems unnecessary to me. jars
are a very clean way to package plugins, and having a single lib directory for
holding them is simple and easy to understand.
> Make it easier to debug new plugin code in an IDE
> -------------------------------------------------
>
> Key: SOLR-498
> URL: https://issues.apache.org/jira/browse/SOLR-498
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 1.2
> Reporter: Benson Margulies
>
> I'm developing components to be deployed via schema.xml. I happen to use
> Eclipse, but I think that comparable fates await the users of other IDEs.
> I tried, and failed, to find a way to incorporate my eclipse output directory
> into the appropriate classpath for schema.xml files.
> Putting it into the global jetty classpath via the jetty startup config does
> not work, due to webapp class loader delegation rules.
> It would be really delux if there were a config file somewhere that would
> allow me to add directories that occur in the same class loader's classpath
> as the solr/lib directory.
> It would be nearly as delux if solr merely supported solr/classes, so that I
> could point Eclipse there.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
