[
https://issues.apache.org/jira/browse/SOLR-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575857#action_12575857
]
Ryan McKinley commented on SOLR-498:
------------------------------------
Hymmm, so you are trying to develop by putting your generated .jar files in the
lib directory in solr home?
I'm missing what problem you have -- i build plugins with eclipse without
issue.
For dev, I launch solr with "run jetty run"
http://code.google.com/p/run-jetty-run/
and use my classes directly rather then putting them in the solr.solr.home/lib
directory
In the future, try this question on [EMAIL PROTECTED] first -- that has a wider
audience of people who can help get things set up.
> 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.
