That worked! Thank you!!
On Fri, Oct 26, 2018 at 2:05 PM Micah Wylde wrote:
> I saw similar problems with imports from RunnerApi not showing up. The
> issue is that by default IntelliJ will not analyze files that are larger
> than 2MB, and RunnerApi is 2.6MB. I was able to fix this by setting
I saw similar problems with imports from RunnerApi not showing up. The
issue is that by default IntelliJ will not analyze files that are larger
than 2MB, and RunnerApi is 2.6MB. I was able to fix this by setting
idea.max.intellisense.filesize=3000
in idea.properties (accessible via help -> edit
Yes. That is an issue that many people are running into.
Intellij's editor does not use the build output from Gradle when providing
code completion/editing support and uses a simple mechanism that indexes
Java source files that is incompatible with our current shading strategy.
Also, Intellij
So everything seems to build fine. But the analyzer shows missing imports
for libraries that are actually part of Beam (in particular: import
org.apache.beam.model.pipeline.v1.RunnerApi). I would have assumed that
this option: "Delegate IDE build/run actions to gradle" would mean that the
Glad it helped! I forgot to mention here that Kenn and I did some hacking
on the IntelliJ docs and the wiki now has much more information:
https://cwiki.apache.org/confluence/display/BEAM/Using+IntelliJ+IDE
If you're still having issues, take another look. And if you have a new
issues or tip
Thank you for the updated docs! I just set up IntelliJ from scratch and
got the build smoothly the the point where it's happy to use up all the
resources on my laptop :)
It was great to be able to just follow the steps provided to get up and
going!
On Fri, Oct 19, 2018 at 2:34 AM Maximilian
Yes, I have the same issue for sources (not binaries). I usually end up
manually fetching sources and adding them to IntelliJ.
On 18.10.18 18:16, Alexey Romanenko wrote:
Does anyone have a problem to fetch a source code of external dependencies?
I have always this error (see attached picture)
Thanks for this info and work! A couple relevant notes:
- There is a #beam-intellij slack channel where I tried to collect some
info a few weeks ago when I was debugging IntelliJ issues
- I tried to figure out where IntelliJ stores the info about the
vendored JARs we manually add to
FYI, I've opened BEAM-5762 to track the work to document and improve
IntelliJ integration. It's broken down into sub-tasks for documenting
individual scenarios. I've grabbed a couple; if you're feeling motivated
feel free to grab one or two to help out!
I left my tips to run *Java* unit tests in Intellij (work for me all the
time). I assumed that people mostly use intellij for Java development.
If there are some cases when people use Intellij to develop other languages
(maybe because of the power of plugins?), we might need to create separate
Last week I migrated all previous content from the website into wiki pages
for IntelliJ [1] and Eclipse [2] (thanks Thomas Weise for the pointers).
The next step is to incorporate all the tips that people have mentioned
here and fill in any other gaps we have. Here's how I'd like to get started:
On Fri, Oct 5, 2018 at 2:18 PM Thomas Weise wrote:
> And any update to the gradle files and reload in intellij - you are back
> to square one.
>
This is particularly compelling. Even the simplest manual step required is
a huge pain. Clear instructions are not an adequate solution if they need
Yes, you need to manually add the vendor JAR to the modules where it is
missing. AFAIK there is no automatic solution.
On 04.10.18 16:34, Thomas Weise wrote:
Was anyone successful making Intellij understand the dependency
vendoring and not display as unresolvable symbols?
On Thu, Oct 4,
Was anyone successful making Intellij understand the dependency vendoring
and not display as unresolvable symbols?
On Thu, Oct 4, 2018 at 6:13 AM Maximilian Michels wrote:
> That's fine, I think we have accepted the fact that IntelliJ only works
> with delegating the build to Gradle instead of
That's fine, I think we have accepted the fact that IntelliJ only works
with delegating the build to Gradle instead of using its built-in Gradle
support. That comes with a bunch of drawbacks, i.e. slow build/test
execution.
4. the current gradle setup still requires some knowledge about the
Le jeu. 4 oct. 2018 à 14:53, Maximilian Michels a écrit :
> > We have some hints in the gradle files that used to allow a smooth
> import with no extra steps*. Have the hints gotten out of date or are there
> new hints we can put in that might help?
>
> If you're referring to the `gradle idea`
Current content on CWiki is outdated and needs to be replaced.
+1 for moving the instructions there (delete from website)
On Wed, Oct 3, 2018 at 8:04 PM Mikhail Gryzykhin <
gryzykhin.mikh...@gmail.com> wrote:
> @Scott Wegner
>
> Would be really great if we can get good hints. However I would
@Scott Wegner
Would be really great if we can get good hints. However I would suggest to
update corresponding page on cwiki, not website. It will be easier to
maintain that one up-to-date. Some of tips already present there.
https://cwiki.apache.org/confluence/display/BEAM/IntelliJ+Tips
At ApacheCon I heard from a number of people that the IntelliJ setup isn't
as good as it used to be with Maven. Bad tooling makes me sad and I want to
make it better :(
It seems everyone has their own magic to get things working. If we got
these tips added to the website [1], do you think we'd
Personally i drop all caches - idea + ivy + maven beam folder, build in
console skipping test execution - important cause idea is not able to
import the project without a correctly ran gradle setup and a failure can
corrupt later imports, then I kill gradle daemon and finally import beam in
idea
We have some hints in the gradle files that used to allow a smooth import
with no extra steps*. Have the hints gotten out of date or are there new
hints we can put in that might help?
Kenn
*anyhow at least for a week or two for a couple of people :-)
On Mon, Oct 1, 2018 at 1:26 PM Ismaël Mejía
Hello Alex,
I understand your pain and thanks for bringing this subject, I also
have found many issues in the process to the point of believing
recently that it is undeterministic.
Last time I followed the process ~3 weeks ago. I had to clean up all
caches (both remove the intelliJ temp files and
Hi Alex,
I had troubles when importing JAVA SDK to intellij at the beginning.
Besides what the instruction says, some extra steps that might help:
1. Preferences/Settings > Build, Execution, Deployment > Build Tools >
Gradle > Runner, choose Gradle Test Runner in the dropdown menu.
2. Enable
Hi Alex,
After a git clean -fdx (removing all IDEA resources), I just open the
folder in IntelliJ and it imports the project.
It works fine so far (NB: I don't build using IntelliJ, it's mostly an
editor for me, I use the command line for any other stuff like git,
gradle, ...).
Regards
JB
On
Some fresh memory here. I had the same issue on my first intellij
project. In my second try I made sure "Create an empty IntelliJ project
outside of the Beam source tree." . Now I can just click a testing targets
in gradle window and it runs.
On Mon, Oct 1, 2018 at 11:05 AM Alex Amato wrote:
Hello,
I'm looking to get a good intellij setup working and then update the
documentation how to build and test the java SDK with intelliJ.
Does anyone have a good setup working, with some tips? I followed our
instructions here, but I found that after following these steps I could not
build or
26 matches
Mail list logo
