Siegfried Goeschl wrote:
> Hi folks,
>
> I got my next problem - when I run "mvn -Prc release:perform" I get
>
> "Error deploying artifact: Authentication failed: Cannot connect.
> Reason: Algorithm negotiation fail"
>
> Having said that
>
> +) I'm using Maven 2.0.10 on Mac OS X 10.4
> +) I can
Hi Dennis,
+) I downgraded to SVN 1.5.0 but still got an SVN error (the SVN sync issue)
+) re-running the maven release plugin did the trick (before I hit the
next problem)
Cheers,
Siegfried Goeschl
Dennis Lundberg wrote:
> Siegfried Goeschl wrote:
>
>> Hi folks,
>>
>> I have simply no "comm
Hi folks,
I got my next problem - when I run "mvn -Prc release:perform" I get
"Error deploying artifact: Authentication failed: Cannot connect.
Reason: Algorithm negotiation fail"
Having said that
+) I'm using Maven 2.0.10 on Mac OS X 10.4
+) I can ssh to people.apache.org
+) I can scp to peopl
sebb schrieb:
On 28/09/2009, sebb wrote:
On 28/09/2009, Stephen Colebourne wrote:
> sebb wrote:
>
> > Where is that described? The first reference I found says that the
> > local variable is a performance optimisation; it's the volatile
> > keyword that makes it thread-safe:
> >
> >
>
On 28/09/2009, sebb wrote:
> On 28/09/2009, Stephen Colebourne wrote:
> > sebb wrote:
> >
> > > Where is that described? The first reference I found says that the
> > > local variable is a performance optimisation; it's the volatile
> > > keyword that makes it thread-safe:
> > >
> > >
> >
On 27/09/2009, James King wrote:
> Hi All,
> Currently, there is no readFully method in IOUtils, the method that is
> the same as the normal read(b, off, len) in java.io.InputStream, but
> tries to ensure that the entire len number of bytes are read.
>
> There is a readFully method in java.io.
Hi All,
Currently, there is no readFully method in IOUtils, the method that is
the same as the normal read(b, off, len) in java.io.InputStream, but
tries to ensure that the entire len number of bytes are read.
There is a readFully method in java.io.DataInput. However, this method
will throw EOFExc
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-fmt-test has an issue affecting its community
integrat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jaxme contains errors.
The current state of this projec
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-xmlunit contains errors.
The current state of this proj
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
On 28/09/2009, Stephen Colebourne wrote:
> sebb wrote:
>
> > Where is that described? The first reference I found says that the
> > local variable is a performance optimisation; it's the volatile
> > keyword that makes it thread-safe:
> >
> >
> http://technology.amis.nl/blog/4384/the-double-checke
sebb wrote:
Where is that described? The first reference I found says that the
local variable is a performance optimisation; it's the volatile
keyword that makes it thread-safe:
http://technology.amis.nl/blog/4384/the-double-checked-locking-confusion
also
http://jeremymanson.blogspot.com/2008/05
13 matches
Mail list logo
