Rahul Akolkar wrote:
> On Tue, Jul 14, 2009 at 1:13 PM, Dennis Lundberg wrote:
>> Do you have your source checked out from the EU svn mirror?
>>
>> If so try to check out and do the release against svn.apache.org
>> instead.
>
>
> Need to go to the master explicitly. With pgeodns that will still
On Tue, Jul 14, 2009 at 1:13 PM, Dennis Lundberg wrote:
> Do you have your source checked out from the EU svn mirror?
>
> If so try to check out and do the release against svn.apache.org
> instead.
Need to go to the master explicitly. With pgeodns that will still
shunt you to harmonia (if it plac
Do you have your source checked out from the EU svn mirror?
If so try to check out and do the release against svn.apache.org
instead. Apparently the dynamic DNS currently used for the ASF svn
servers messes up releases using Maven's Release Plugin.
If not, try to run the release command one more
On Tue, Jul 14, 2009 at 12:35 PM, Siegfried
Goeschl wrote:
> Hi folks,
>
> anyone out there having an idea what to do with? It is a reproducible
> SVN problem but this is the only thing I know for the moment :-(
>
If all else fails, go straight to the master (use
svn-master.apache.org) -- su
I've had some troubles with the release plugin lately. With the newer
versions of Maven, you'll get a problem with svn. It seems to clean
itself up if you do svn update and then retry your command.
On Tue, Jul 14, 2009 at 12:35 PM, Siegfried
Goeschl wrote:
> Hi folks,
>
> anyone out there having
Hi folks,
anyone out there having an idea what to do with? It is a reproducible
SVN problem but this is the only thing I know for the moment :-(
Thanks in advance
Siegfried Goeschl
PS: Was using "mvn -Prc release:prepare" on commons-exec
=== START ===
[INFO]
-
