Hi,

    I don't know how to get the log, because that is all what maven will print 
in the console. Even with mvn -X I get the same print out (plus some 
exceptions).


----- "Mark Struberg" <[email protected]> wrote:

> Erwin,
> 
> do you have a log of the git push command which fails? We log it to
> the console in case of an error.
> Please try to execute this command manually and check if there are any
> errors too.
> 
> LieGrue,
> strub
> 
> --- On Thu, 8/4/11, Stephen Connolly <[email protected]>
> wrote:
> 
> > From: Stephen Connolly <[email protected]>
> > Subject: Re: mvn release is failing with git
> > To: "Maven Users List" <[email protected]>
> > Date: Thursday, August 4, 2011, 6:43 AM
> > release activates some profiles which
> > will result in the active by default
> > profiles no longer being so
> > 
> > - Stephen
> > 
> > ---
> > Sent from my Android phone, so random spelling mistakes,
> > random nonsense
> > words and other nonsense are a direct result of using swype
> > to type on the
> > screen
> > On 4 Aug 2011 03:10, <[email protected]>
> > wrote:
> > > Hallo,
> > >
> > > I have an error in maven release plugin (mvn
> > release:prepare):
> > >
> > > [ERROR] The git-push command failed.
> > > [ERROR] Command output:
> > > [ERROR] fatal: The remote end hung up unexpectedly
> > >
> > > But I'm sure that the remote repository works just
> > fine. Is there
> > difficulties with the git protocol? I post my settings.xml
> > and pom.xml:
> > >
> > > @----------------- settings.xml
> > > <settings>
> > >
> > > <profiles>
> > > <profile>
> > > <id>Repository Root Locations Local</id>
> > > <activation>
> > > <activeByDefault>true</activeByDefault>
> > > </activation>
> > > <properties>
> > > <archiva.repository.root>http://localhost:8080/archiva
> > </archiva.repository.root>
> > >
> > <git.repository.root>git://localhost/~devent</git.repository.root>
> > > </properties>
> > > </profile>
> > > ...
> > > -----------------@
> > >
> > > @----------------- pom.xml
> > > <scm>
> > >
> > <connection>scm:git:${git.repository.root}/xmlstorage.git
> > </connection>
> > >
> > <developerConnection>scm:git:${git.repository.root}/xmlstorage.git
> > </developerConnection>
> > >
> > <url>scm:git:scm:git:${git.repository.root}/xmlstorage.git
> > </url>
> > > </scm>
> > >
> > > <distributionManagement>
> > > <repository>
> > > <id>globalscaling.com-public</id>
> > >
> >
> <url>${archiva.repository.root}/repository/globalscaling.com-public/</url>
> > > </repository>
> > > <snapshotRepository>
> > >
> > <id>globalscaling.com-public-snapshots</id>
> > >
> >
> <url>${archiva.repository.root}/repository/globalscaling.com-public-snapshots/</url>
> > > </snapshotRepository>
> > > </distributionManagement>
> > > -----------------@
> > >
> > > I have them in properties because I like to change
> > them without to touch
> > the pom.xml. Sometimes I work at home, there I have a good
> > internet
> > connection, but sometimes I work with my laptop with no/bad
> > connection. So I
> > setup a git repository and Archiva on localhost.
> > >
> > > git pull and git push works, and mvn deploy works,
> > too. mvn scm update
> > works, too. So I don't understand, if I use the ssh
> > protocol in the URLs,
> > mvn release works just fine. Is it an issue with the git
> > protocol?
> > >
> > > Kind regards, Erwin.
> > >
> > > --
> > > Erwin Mueller, [email protected]
> > > http://www.global-scaling-institute.de/
> > > http://www.deventm.org
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

-- 
Erwin Mueller, [email protected]
http://www.global-scaling-institute.de/
http://www.deventm.org

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

Reply via email to