[
https://issues.apache.org/jira/browse/LUCENE-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aishwarya Dabhade updated LUCENE-9586:
--------------------------------------
Description:
I am a complete beginner trying to build Lucene from source on IntelliJ IDEA
IDE . Creating issue this as I have already tried it for a couple of days now.
I have one question mainly:
# Does the community use IntelliJ IDE on Windows for building ? If not, then
what is the configuration / setup used for development and debugging ? I
understand there might not be a single way to do it, but just want to know
which one is the easiest. Should I not attempt to build it in Windows and just
go for remote debugging?
I followed the instructions on the website but the assemble task fails in
IntelliJ IDE. I am working on Windows 10 Home, 64 bit.
In the project root directory ( lucene-solr ) cloned from git:
on ubuntu 18.04 container on Windows via WSL2, the following works.
`./gradlew -p lucene assemble`
The build is successful
Then, I tried on Windows cmd ( command line ) by executing the following
`gradlew.bat -p lucene assemble`
This time around, though I got an error which said 'command 'perl'' failed. So
I installed Strawberry perl on Windows 10. I guess perl is available out of box
in most linux distros, so it works by default. After installing perl, the build
was successful, so it works via Windows cmdline.
Then I went on to try it out in IntelliJ IDEA IDE on Windows 10. The only
reason I am trying to do it in IDEA is because that's the only method I know
that supports CheckStyle and where navigating the code surrounding a breakpoint
is easier rather than using say vim and the shell on a Linux machine. If there
is any other better or preferred way (maybe like remote debugging with IDE on
local Windows installation and source code and ./gradlew on remote Linux
machine [haven't tried it yet] ) , please highlight that.
This is where I got a bunch of red lines in MissingDoclet.java because IntelliJ
couldn't resolve it. But javadoc is indeed a part of jdk11, so I'm not sure why
IntelliJ cannot resolve it.
Following is the output of the assemble task
* What went wrong:
Execution failed for task ':missing-doclet:compileJava'.
> Compilation failed; see the compiler error output for details.
I have attached a screenshot below of the gradle settings
!gradle-settings.png!
!gradle-build-task-intellij.PNG!
After running the above task:
!intellij-build.PNG!
Thanks in advance, appreciate all the efforts by the community, hoping to
contribute soon !
was:
I am a complete beginner trying to build Lucene from source on IntelliJ IDEA
IDE . Creating issue this as I have already tried it for a couple of days now.
I have one question mainly:
# Does the community use IntelliJ IDE on Windows for building ? If not, then
what is the configuration / setup used for development and debugging ? I
understand there might not be a single way to do it, but just want to know
which one is the easiest. Should I not attempt to build it in Windows and just
go for remote debugging?
I followed the instructions on the website but the assemble task fails in
IntelliJ IDE. I am working on Windows 10 Home, 64 bit.
In the project root directory ( lucene-solr ) cloned from git:
on ubuntu 18.04 container on Windows via WSL2, the following works.
`./gradlew -p lucene assemble`
The build is successful
Then, I tried on Windows cmd ( command line ) by executing the following
`gradlew.bat -p lucene assemble`
This time around, though I got an error which said 'command 'perl'' failed. So
I installed Strawberry perl on Windows 10. I guess perl is available out of box
in most linux distros, so it works by default.
Then I went on to try it out in IntelliJ IDEA IDE on Windows 10. The only
reason I am trying to do it in IDEA is because that's the only method I know
that supports CheckStyle and where navigating the code surrounding a breakpoint
is easier rather than using say vim and the shell on a Linux machine. If there
is any other better or preferred way (maybe like remote debugging with IDE on
local Windows installation and source code and ./gradlew on remote Linux
machine [haven't tried it yet] ) , please highlight that.
This is where I got a bunch of red lines in MissingDoclet.java because IntelliJ
couldn't resolve it. But javadoc is indeed a part of jdk11, so I'm not sure why
IntelliJ cannot resolve it.
Following is the output of the assemble task
* What went wrong:
Execution failed for task ':missing-doclet:compileJava'.
> Compilation failed; see the compiler error output for details.
I have attached a screenshot below of the gradle settings
!gradle-settings.png!
!gradle-build-task-intellij.PNG!
After running the above task:
!intellij-build.PNG!
Thanks in advance, appreciate all the efforts by the community, hoping to
contribute soon !
> Intellij not able to resolve jdk.javadoc.doclet
> -----------------------------------------------
>
> Key: LUCENE-9586
> URL: https://issues.apache.org/jira/browse/LUCENE-9586
> Project: Lucene - Core
> Issue Type: Task
> Components: general/build, general/javadocs, general/tools, luke
> Affects Versions: 8.6.3
> Environment: Windows 10 Home
> jdk11
> IntelliJ IDEA
> Ubuntu 18.04 on WSL2 ( Windows Subsystem for Linux )
>
> Reporter: Aishwarya Dabhade
> Priority: Minor
> Labels: beginner, build, newbie
> Attachments: gradle-build-task-intellij.PNG, gradle-settings.png,
> intellij-build.PNG
>
>
> I am a complete beginner trying to build Lucene from source on IntelliJ IDEA
> IDE . Creating issue this as I have already tried it for a couple of days now.
> I have one question mainly:
> # Does the community use IntelliJ IDE on Windows for building ? If not, then
> what is the configuration / setup used for development and debugging ? I
> understand there might not be a single way to do it, but just want to know
> which one is the easiest. Should I not attempt to build it in Windows and
> just go for remote debugging?
> I followed the instructions on the website but the assemble task fails in
> IntelliJ IDE. I am working on Windows 10 Home, 64 bit.
> In the project root directory ( lucene-solr ) cloned from git:
> on ubuntu 18.04 container on Windows via WSL2, the following works.
> `./gradlew -p lucene assemble`
> The build is successful
> Then, I tried on Windows cmd ( command line ) by executing the following
> `gradlew.bat -p lucene assemble`
> This time around, though I got an error which said 'command 'perl'' failed.
> So I installed Strawberry perl on Windows 10. I guess perl is available out
> of box in most linux distros, so it works by default. After installing perl,
> the build was successful, so it works via Windows cmdline.
> Then I went on to try it out in IntelliJ IDEA IDE on Windows 10. The only
> reason I am trying to do it in IDEA is because that's the only method I know
> that supports CheckStyle and where navigating the code surrounding a
> breakpoint is easier rather than using say vim and the shell on a Linux
> machine. If there is any other better or preferred way (maybe like remote
> debugging with IDE on local Windows installation and source code and
> ./gradlew on remote Linux machine [haven't tried it yet] ) , please highlight
> that.
> This is where I got a bunch of red lines in MissingDoclet.java because
> IntelliJ couldn't resolve it. But javadoc is indeed a part of jdk11, so I'm
> not sure why IntelliJ cannot resolve it.
> Following is the output of the assemble task
> * What went wrong:
> Execution failed for task ':missing-doclet:compileJava'.
> > Compilation failed; see the compiler error output for details.
> I have attached a screenshot below of the gradle settings
> !gradle-settings.png!
>
> !gradle-build-task-intellij.PNG!
> After running the above task:
>
> !intellij-build.PNG!
>
> Thanks in advance, appreciate all the efforts by the community, hoping to
> contribute soon !
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
