i recently tried setting up solr dev environment in my eclipse and i am
really glad to see Robert Muir's comments regarding how difficult it is to
get it all setup and working in these ide's because it took me about 3-4
redo everything attempts and about a week to get it all setup simply to be
able to run ant test and even then some tests still failed (very few). i
also had all kinds of problems in running specific tests instead of every
single test. so anyways with all these new updates you guys have made .. did
all that made anything easier. will there be new instructions in
HowToContrib section for eclipse and idea .. also another thing to mention
.. i setup mine on eclipse 3.5 but from HowToContrib i had to do steps
mentioned for eclipse 3.6 as well .. also as i mentioned before i am not
able to run individual tests and i have tried all the possible ways pointed
out in solr wiki (e.g. ant -DtestCase ....) ..

just thought ill make the voice of people, who want to contribute but just
cant get past the initial setting things up obstacle, heard.

Thanks
Adeel

On Fri, Dec 31, 2010 at 9:58 AM, JIRA [email protected] [via Lucene] <
[email protected]<ml-node%[email protected]>
> wrote:

>
>     [
> https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976284#action_12976284
>  ]
>
>
> Steven Rowe commented on LUCENE-2611:
> -------------------------------------
>
> Hi Erick,
>
> {quote}
> I just tried this on my Windows box and it works perfectly, even to running
> tests. The only thing I had to do was open the project from IntelliJ and set
> the compiler, just as expected. Well, and wait for IntelliJ to finish
> indexing things <G>...
>
> Sweet!
>
> I really think this will make it MUCH easier for people to contribute, I
> always dread setting up any IDE for a new project since it usually takes
> seemingly forever. Nice work!
> {quote}
>
> Thanks.  The key, of course, is keeping it in synch with the project
> structure.  I plan on writing up maintenance instructions the next time this
> is required, so that others can more easily contribute to the effort.
>
> bq. I'll try it on my Mac just for yucks...
>
> Cool, let me know if you notice anything amiss.
>
>
> > IntelliJ IDEA and Eclipse setup
> > -------------------------------
> >
> >                 Key: LUCENE-2611
> >                 URL: https://issues.apache.org/jira/browse/LUCENE-2611
> >             Project: Lucene - Java
> >          Issue Type: New Feature
> >          Components: Build
> >    Affects Versions: 3.1, 4.0
> >            Reporter: Steven Rowe
> >            Priority: Minor
> >             Fix For: 3.1, 4.0
> >
> >         Attachments: LUCENE-2611-branch-3x.patch,
> LUCENE-2611-branch-3x.patch, LUCENE-2611-branch-3x.patch,
> LUCENE-2611-branch-3x.patch, LUCENE-2611-branch-3x.patch, LUCENE-2611.patch,
> LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch,
> LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch,
> LUCENE-2611_eclipse.patch, LUCENE-2611_mkdir.patch, LUCENE-2611_test.patch,
> LUCENE-2611_test.patch, LUCENE-2611_test.patch, LUCENE-2611_test.patch,
> LUCENE-2611_test_2.patch
> >
> >
> > Setting up Lucene/Solr in IntelliJ IDEA or Eclipse can be time-consuming.
>
> > The attached patches add a new top level directory {{dev-tools/}} with
> sub-dirs {{idea/}} and {{eclipse/}} containing basic setup files for trunk,
> as well as top-level ant targets named "idea" and "eclipse" that copy these
> files into the proper locations.  This arrangement avoids the messiness
> attendant to in-place project configuration files directly checked into
> source control.
> > The IDEA configuration includes modules for Lucene and Solr, each Lucene
> and Solr contrib, and each analysis module.  A JUnit run configuration per
> module is included.
> > The Eclipse configuration includes a source entry for each
> source/test/resource location and classpath setup: a library entry for each
> jar.
> > For IDEA, once {{ant idea}} has been run, the only configuration that
> must be performed manually is configuring the project-level JDK.  For
> Eclipse, once {{ant eclipse}} has been run, the user has to refresh the
> project (right-click on the project and choose Refresh).
> > If these patches is committed, Subversion svn:ignore properties should be
> added/modified to ignore the destination IDEA and Eclipse configuration
> locations.
> > Iam Jambour has written up on the Lucene wiki a detailed set of
> instructions for applying the 3.X branch patch for IDEA:
> http://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden 
> email]<http://user/SendEmail.jtp?type=node&node=2172952&i=0>
> For additional commands, e-mail: [hidden 
> email]<http://user/SendEmail.jtp?type=node&node=2172952&i=1>
>
>
>
> ------------------------------
>  View message @
> http://lucene.472066.n3.nabble.com/jira-Commented-LUCENE-2611-IntelliJ-IDEA-and-Eclipse-setup-tp2172952p2172952.html
> To start a new topic under Solr - Dev, email
> [email protected]<ml-node%[email protected]>
> To unsubscribe from Solr - Dev, click 
> here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=506503&code=YWRlZWxtYWhtb29kQGdtYWlsLmNvbXw1MDY1MDN8LTg2NzQwODU2Nw==>.
>
>

-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/jira-Commented-LUCENE-2611-IntelliJ-IDEA-and-Eclipse-setup-tp2172952p2173278.html
Sent from the Solr - Dev mailing list archive at Nabble.com.

Reply via email to