I remember that adding those manually helped a bit. But I could never add enough jar files to fully got rid of the issue.
And any update to the gradle files and reload in intellij - you are back to square one. On Thu, Oct 4, 2018 at 7:43 AM Maximilian Michels <m...@apache.org> wrote: > 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, 2018 at 6:13 AM Maximilian Michels <m...@apache.org > > <mailto:m...@apache.org>> wrote: > > > > 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 setup (like for validates runners which are not "just tests") > > and there is no trivial way to make the IDE aware of it until you > > generate the IDE files (.idea > > The ValidatesRunner tests are not part of the IntelliJ setup. These > are > > additional integration test which are part of Gradle but can't be > > programmatically called from within IntelliJ. > > > > On 04.10.18 14:59, Romain Manni-Bucau wrote: > > > > > > > > > > > > Le jeu. 4 oct. 2018 à 14:53, Maximilian Michels <m...@apache.org > > <mailto:m...@apache.org> > > > <mailto:m...@apache.org <mailto:m...@apache.org>>> 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` task which generates > > IntelliJ > > > IPR files, that doesn't work anymore. The build is way too > > involved for > > > that too work. We've since removed this from the contribute > > guide. > > > > > > There is still the IntelliJ tips page which describes a > different > > > (non-working) procedure. In the end, you have to fiddle with > the > > > project > > > setup, i.e. adding the vendor JAR to the classpath where > > necessary. But > > > it breaks as soon as your refresh the Gradle project. > > > > > > Romain, can you really get it to work out of the box with > > your method? > > > If so, I'd like to contact you for information to update the > > > IntelliJ page. > > > > > > > > > Yep, worked at least last time I tried. I didn't played much with > > it but > > > I assume it is reproducible. Feel free to ping me on slack. > > > > > > > > > Note, this is not the first conversation, so we should really > > fix the > > > instructions/describe the workarounds. See also > > > > > > https://lists.apache.org/thread.html/c8323622e5de92089ebdfecee09a0e37cae0c631e1bebf06ed9f2bc6@%3Cdev.beam.apache.org%3E > > > > > > > > > The small warn here is that, by design, you will not fix them all > > since: > > > > > > 1. the IDE must run the script to import the project (which is a > big > > > drawback compared to maven where it can be imported without > > running any > > > project code). This small phase easily breaks if you need > > anything from > > > the env and beam requires some setup. > > > 2. the script defines a lifecycle the IDE can't respect today > > cause it > > > is coded and not always guessable enough > > > 3. running tests in the IDE requires to use the launcher which > > rebuilds > > > the whole project model before executing anything which is slow > > compared > > > to IDE default launcher which is way better and the one used my > > most dev > > > 4. the current gradle setup still requires some knowledge about > the > > > setup (like for validates runners which are not "just tests") and > > there > > > is no trivial way to make the IDE aware of it until you generate > > the IDE > > > files (.idea) > > > > > > On 01.10.18 23:32, Romain Manni-Bucau wrote: > > > > 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 using the wrapper. > > > > > > > > As it has been mentionned you will have to run tests using > > gradle > > > > wrapper due to current gradle setup which slows down a lot > the > > > execution > > > > compared to native idea one but at least it will run and > > you can > > > debug > > > > normally. > > > > > > > > Le lun. 1 oct. 2018 22:38, Kenneth Knowles > > <k...@apache.org <mailto:k...@apache.org> > > > <mailto:k...@apache.org <mailto:k...@apache.org>> > > > > <mailto:k...@apache.org <mailto:k...@apache.org> > > <mailto:k...@apache.org <mailto:k...@apache.org>>>> 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? > > > > > > > > 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 > > > <ieme...@gmail.com <mailto:ieme...@gmail.com> > > <mailto:ieme...@gmail.com <mailto:ieme...@gmail.com>> > > > > <mailto:ieme...@gmail.com <mailto:ieme...@gmail.com> > > <mailto:ieme...@gmail.com <mailto:ieme...@gmail.com>>>> wrote: > > > > > > > > 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 the > > > gradle cache > > > > files) and also I had to refresh the project in > > IntelliJ's > > > > gradle tool > > > > windows view after the initial import at least 2 > times > > > until it > > > > finally worked. Also remember that 2018.2 is not > > supported as > > > > reported > > > > by Ryan some weeks ago (not sure if already fixed). > > > > > > > > Probably there was something corrupted in my setup > > but I > > > have heard > > > > similar stories of at least 2 more people. > > > > I really don't know how we can improve the current > > status quo > > > > apart of > > > > contacting the IntelliJ guys but I am concerned on > how > > > this can > > > > be an > > > > issue for new contributors. > > > > > > > > On Mon, Oct 1, 2018 at 8:47 PM Rui Wang > > > <ruw...@google.com <mailto:ruw...@google.com> > > <mailto:ruw...@google.com <mailto:ruw...@google.com>> > > > > <mailto:ruw...@google.com > > <mailto:ruw...@google.com> <mailto:ruw...@google.com > > <mailto:ruw...@google.com>>>> wrote: > > > > > > > > > > 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 annotation processor. > > > > > > > > > > -Rui > > > > > > > > > > On Mon, Oct 1, 2018 at 11:33 AM Jean-Baptiste > > Onofré > > > > <j...@nanthrax.net <mailto:j...@nanthrax.net> > > <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>> > > > <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net> > > <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>>>> wrote: > > > > >> > > > > >> 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 01/10/2018 20:05, 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 test the project. It seemed > > like the build > > > > button did > > > > >> > nothing and the test buttons did not appear. > > > > >> > https://beam.apache.org/contribute/intellij/ > > > > >> > > > > > >> > I'm also curious about the gradle support for > > > generating > > > > intelliJ > > > > >> > projects. Has anyone tried this as well? > > > > >> > > > > > >> > Any tips would be appreciated. > > > > >> > Thank you, > > > > >> > Alex > > > > >> > > > > >> -- > > > > >> Jean-Baptiste Onofré > > > > >> jbono...@apache.org > > <mailto:jbono...@apache.org> <mailto:jbono...@apache.org > > <mailto:jbono...@apache.org>> > > > <mailto:jbono...@apache.org <mailto:jbono...@apache.org> > > <mailto:jbono...@apache.org <mailto:jbono...@apache.org>>> > > > > >> http://blog.nanthrax.net > > > > >> Talend - http://www.talend.com > > > > > > > > > >
