Store email and password in ~/.m2/Settings.xml about appengine-maven-plugin HOT 18 OPEN

There are some ways to do this, I'll see about putting some docs together.

using --oauth2 with the first appcfg update would be much better, no?

The main use case for this is automated deploys from ci build slaves...
where would we pass in/store the tokens?

Hey Matt,

"There are some ways to do this"
Can you name a few ways to do this or provide some pointers? Of course I want 
to use this with our CI server. Without this feature I cannot use the plugin.

Thanks,
Ingo

One good way to store credentials would be to use Maven server password 
encryption:

http://maven.apache.org/guides/mini/guide-encryption.html

That said, I'm really confused about the current behavior. I turned off OAuth2 
by including

<appengine.oauth2>false</appengine.oauth2>

in my pom.xml file. However, I was completely surprised when I ran "mvn 
appengine:update" and it WORKED without prompting for any email or password! 
Where in the world is it getting credentials to update my app?

OK, found it: a cookie stored in ~/.java/.userPrefs. Sorry for the digression.

Hi,

I am having the same problem of not knowing how to use the plugin on my CI 
server.

I don't have access to the CI server to plant an oauth token on the users 
folder.

Matt, did you find the time yet to write those docs? ;)

Thanks

Maven has a <server> declaration that is perfect for this. One can define their 
credentials in settings.xml and the plugin just needs to know the id of the 
server to pull the username and password.

How do you specify which <server> to pick form the settings.xml?

In the old maven-gae-plugin, there was a server configuration parameter that 
specified this, defaulting to "appengine.google.com"

I managed to work around this issue using this config:

<plugin>
  <groupId>com.google.appengine</groupId>
  <artifactId>appengine-maven-plugin</artifactId>
  <version>1.8.6</version>
  <configuration>
    <email>[email protected]</email>
    <oauth2>false</oauth2>
    <noCookies>true</noCookies>
    <passin>true</passin>
  </configuration>
</plugin>

and by invoking the update goal like this:

mvn clean appengine:update <<< "yourPassW00rd"

The problem is that your password is in clear in the command line in your CI 
server. Not really nice in terms of security.

Yes I totally agree with you. Picking the credentials from the <server> in 
Maven's settings.xml would be a much cleaner solution. 

i tried to use this command: mvn clean appengine:update <<< "yourPassW00rd"... 
but how do i do it? The Travis-ci console keeps saying my email and password do 
not match.

I though it was just substituting yourPassW00rd with my google app engine 
password.

@simon - this does not work in Jenkins. Not the standard way at least.

We need this...

I forked the project and merged in the settings.xml authentication from the old 
kindleit plugin.

https://github.com/rdwallis/appengine-maven-plugin

Needs some codestyle attention but otherwise works well.

No idea how to issue a PR to this project though.  Are there contribution 
guidelines anywhere?

'+'1000! You rock!