![]() iml files throughout the project hierarchy ( find. Otherwise, it didn't include my actual GAE modules in the list of modules I could add GAE too.īut anyways, I found success doing the following:Ĭlose the project delete it from IntelliJ delete ALL the IntelliJ files: both. Sorry - I wasn't clear I think manually deleted the facet from the Maven modules before trying that. The other Maven modules (green) get built into JARs, which are then dependencies for the GAE service the fact that you were able to add Google App Engine standard support to your module via that tools menu shortcut suggests to me that something was misconfigured previously with your App Engine framework support The Google Cloud Tools-based Maven plugin is used only in each of the GAE service poms (red above). But just like the others on this thread, in IntelliJ, the artifacts drop-down for the GAE Run Configuration is never populated with any of the exploded wars in my project.įrom inside Intellij, I can run the dev server using a Maven run configuration with the appengine:run goal - but no changes I make to files inside IntelliJ are reflected unless I kill and restart that process every time. Outside of IntelliJ, I am able to run the GAE dev server using the Maven plugin directly from the root of my GAE default module (using mvn appengine:run). Is there an up-to-data example to look at that works with the IntelliJ plugin? EAR is NOT supported for Java8 according to configuration files documentation, yet Java7 is deprecated. The example you cite ( multi-module guestbook) is java7 with an EAR structure. My project is multi-module java8, built with Maven using the Google Cloud Tools-based plugin, version 1.3.2. The issue being that the IDE does not prevent you from adding App Engine framework support on a newly imported project before the Gradle subsystem has finished resolving all of the modules (causing the Framework Support to be added to the wrong I'm getting this same issue with Intellij plugin version 17.12.2. We have been able to reproduce certain instances of this issue specifically with a multi-module project using Gradle. ![]() ![]() ) that would be helpful too in providing a full detailed explanation and a resolution to this. This may resolve the problem and result in the Artifact to Deploy dropdown being populated again:Īlso, if you could please report back on which build system you are using (Gradle / Maven / none. To attempt to resolve this, add the support via the tools menu ( make sure you are on plugin version 17.11.1 or later):Īnd then select the module to which you'd like to add the support. App Engine framework support is required for an artifact to be available for running on the local app engine development server. It is possible that you either don't have App Engine framework support at all, or it has been added to the incorrect module. Conversely, the configurations work on the version after 17.2.6 cannot work on the version 17.2.6.įeel free to deviate from this template as needed, especially if you are submitting a feature those of you still experiencing this issue, could you please try the following: Does the version after 17.2.6 change the run configuration mechanism? because the configurations work on 17.2.6 cannot work on the version after 17.2.6. I think the reason is that the project is an old project which uses the old version plugin.)īy the way, I I use the version of google-cloud-tools-17.2.6_2017, the previous version of run configuration do not have the error. ![]() (I also try to create a new project, the configuration is right. I don't why, and is there any tool or log to see what the wrong with the project. I always got the error in the running configuration as follows, I have added build Artifact in the build list, but it cannot find the Artifact to deploy. Upgrade to the new version plugin : 17.8.2. Google Cloud SDK version (run gcloud version on the command line):.(Please ensure you are running the latest version of Cloud Tools for IntelliJ with Help > Check for Updates.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |