Cool. Thanks for the advice. Makes sense.

Cheers, Eric

On 3/19/2014 4:39 PM, Stephen Connolly wrote:
I favour using my ssh key to deploy and keeping my password out of a file.
With my password I can de-authorise any ssh key... So if the machine I am
releasing from becomes compromised I can retain control of my GitHub
account

You may view otherwise if you choose

On Wednesday, 19 March 2014, Eric Kolotyluk <[email protected]>
wrote:

Ok, adding

     <server>
       <id>github.com</id>
       <username>kolotyluk</username>
       <password>/secret/</password>
     </server>

to settings.xml did the trick. Many thanks Stephen, and Russell.

Russell, this would be a good step to add to Video6_3.mp4

Why is ssh better than https?

Cheers, Eric


On 3/19/2014 12:30 PM, Stephen Connolly wrote:

On Wednesday, 19 March 2014, Eric Kolotyluk <[email protected]>
wrote:

  Now I have

    <scm>
<url>https://github.com/kolotyluk/java-file-utilities.git</url>
<connection>scm:git:https://github.com/kolotyluk/java-file-utilities.git</
connection>
<developerConnection>scm:git:https://github.com/kolotyluk/
java-file-utilities.git</developerConnection>


I favour the ssh variant of the GitHub URL


     </scm>

But it still hangs...

    [INFO] Checking in modified POMs...
    [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities
    [INFO] Executing: cmd.exe /X /C "git status"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities
    [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
C:\Users\Eric\AppData\Local\Temp\maven-scm-1007803688.commit pom.xml"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities
    [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities
    [INFO] Executing: cmd.exe /X /C "git push https://github.com/kolotyluk/
java-file-utilities.git master:master"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities

In my experience, getting release to work is the hardest thing I have ever
done in Maven. I struggled for weeks to get it working with Perforce
correctly. This is my first time with Git.

Do I need to set up a <server> in my settings.xml file for github?


Yes


  Cheers, Eric

On 3/19/2014 12:06 PM, Russell Gold wrote:

  HI Eric, I think you are missing the ".git" extensions in your urls.
Here's the ones I use.

       <scm>
           <url>https://github.com/meterware/simplestub.git</url>
           <developerConnection>scm:git:https://github.com/meterware/
simplestub.git</developerConnection>
           <connection>scm:git:https://github.com/meterware/simplestub.git
</connection>
       </scm>

On Mar 19, 2014, at 2:58 PM, Eric Kolotyluk <[email protected]>
wrote:

   I am having trouble getting mvn release:prepare to work with github

    <scm>
<connection>scm:git:http://github.com/kolotyluk/java-file-utilities
</connection>
<url>scm:git:http://github.com/kolotyluk/java-file-utilities</url>
<developerConnection>scm:git:https://github.com/kolotyluk/
java-file-utilities</developerConnection>
      <tag>java-file-utilities-0.0.1</tag>
    </scm>

When I try to prepare the release I get

    [INFO] Checking in modified POMs...
    [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
    [INFO] Working directory: D:\Users\Eric\Software\
Project\Repositories\java-file-utilities
    [INFO] Executing: cmd.exe /X /C "git status"





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to