Plugin-Update | Distributing Your Plugins in GitHub with Automatic Updates

You're creating the variable right there. You can even name it something else if you want (eg. $update_checker), that shouldn't cause any issues in this particular case as the variable isn't being used anywhere else (according to your own words.)

For more details: PHP variables.

You can change your current tag:

1. Get a working copy that points to tags/1.4.1/. To do this, right click on a directory in windows explorer where you want to place your working copy. Then select SVN Checkout.... Change the 'URL of repository' to tags/1.4.1/. See: Checking Out A Working Copy

2. Make your local changes in the working copy you created in previous step.

3. Right click on the folder of your working copy and select SVN Commit... Commit your changes in the working copy you worked on in previous step. TortoiseSVN may warn you that you're trying to commit into a tag (which is true) but you can proceed anyway if that's what you want.

... or you can simply remove the tag from the Repository Browser, make your changes elsewhere (in a working copy that points to trunk) and then Branch/Tag again from the aforementioned working copy.

I'm answering here cause comments are to short: (Not yet a final answer):

It is coming back cause it's a transitive dependency of spring-boot-starter ... or more accurate spring-boot-starter has a dependency on spring-boot-starter-logging which has the dependency on logback-classic which is the default for spring-boot.

Furthermore I don't see slf4j in lombok project

one more thing the first dependency endpoints-framework contains the reference to slf4j-nop which is from my point of view wrong.

Apart from all above the configured versions-maven-plugin and binding it to the compile phase does not make sense which makes your build very slow....

It appears to be this bug: https://youtrack.jetbrains.com/issue/IDEA-139236

Which is duplicated by: https://youtrack.jetbrains.com/issue/IDEA-157229 that contains the following workaround:

Using a newly generated plugin project using the maven-archytype-plugin, when I tried running the default integration test, it failed due to the following error:

while a "configuration" setup is usually safe to place in the reference of a plugin in the plugin management tree, its execution is not.

Update your pom as follow and share the enforcer execution with inherited artifacts:

The error was fixed by removing the icon definition from config.xml:

A patch by me has been released with version 2.5 of the Versions Maven Plugin

Now it is possible to create a version rules file and to place it on the classpath.

This example below shows how to reference a rules file called rules.xml which is provided in a jar on the classpath:

As saiyr stated in the comments, Google Cloud Endpoints v1.1 has been completely deprecated and has stopped serving traffic and that is the reason for the errors I was having. I solved this problem by migrating to cloud endpoints v2, the process is as easy as following the guide in the migration docs but here are some issues I had with Migration and how I fixed it.

1. Google guava library has to be updated to a version greater than version 19, using version 19 or lower could result in the application throwing reflection errors when handling requests.

2. If you have multiple service classes they have to be added to the web.xml file as service parameters while declaring the com.google.api.server.spi.EndpointsServlet Servlet. for some reasons listing only one service class worked for me in cloud endpoint 1.0 Api docs and routes were generated for all the service classes I had without declaring everyone of them explicitly under the com.google.api.server.spi.SystemServiceServlet Servlet, I think it has something to do with Objectify filters though. See the Docs for more info

3. Since the Google App Engine Java 7 runtime is deprecated too, I decided to migrate to Java 8 but unfortunately the library I used to abstract the process of connecting to datastore (Objectify) appears not to work with the Java 8 runtime, I would look into this later, but reverting back to Java 7 runtime worked for me and the application is back up and running.

Update: The issue I faced migrating to Java 8 runtime had nothing to do with Objectify, the library I used for encrypting passwords (BCrypt) was the issue, it just did not work on the Google App Engine Java 8 runtime, I had to switch to the Encryption library in spring security.

You raised three different issues: hot reload on App Engine flexible, deployment issue when using mvh appengine:devserver and Jetty 403 error message.

Regarding hot reload, it is only possible in Java for certain cases, as explained by Patrice (googler) in this post.

Regarding Jetty, 403 errors are mostly related to permissions, as described in wikipedia:

The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.

Regarding mvn development environment, is difficult to evaluate based only on your pom.xml but based on this SO post, I would review the groupIds, the goals and parameters described here (shouldn't you use appengine-web.xml instead of web.xml?) and the official documentation for Apache Maven.