[ 
https://issues.apache.org/jira/browse/SOLR-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576442#action_12576442
 ] 

Benson Margulies commented on SOLR-498:
---------------------------------------

Let me try to draw a clearer picture here of what I had in mind.

I'm sitting here in front of eclipse. It automatically rewrites .class files to 
whatever folder I tell it to as I make changes. Now, pace run-jetty-run, here's 
what I've been doing.

1) I made a shell script to launch the example with the usual -X arguments to 
allow a debugger to attach.

2) Every time I made a change, I used the Eclipse jar exporter to package the 
classes into a jar in solr/lib.

3) Then cycle jetty and attach Eclipse.

By no means am I proposing that a more complex delivery mechanism is 
appropriate for production use. This is all about the edit-deploy-debug cycle, 
such as it is.

I confess that even with the hints on the user list, I still haven't managed to 
get solr running from eclipse with run-jetty-run. I can't seem to round up the 
right jar files in the classpath, and I seem to have hit a bug in run-jetty-run 
related to using Eclipse workspace links.

Having written all this, I think we should abandon this as an issue. I will 
eventually sort out RJR, and when I do I'll look for a place on your Wiki to 
record a detailed recipe.




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

Reply via email to