Yes, that's what happened.
Yeah, I still assume /tag/ name should be different from branch name,
at least for svn.
Kristian
2015-04-22 7:58 GMT+02:00 Chris Graham :
> If you add some tests, please make sure that can still release from branches,
> as all of my corporate work was like that.
>
If you add some tests, please make sure that can still release from branches,
as all of my corporate work was like that.
There were some circumstances when a release would go nuts, and the URL in the
SCM section of the Pom was not left as trunk or branches, but the tag itself.
Is that what happ
Thanks a lot Adrien, that seemed to fix it !
I'll see if I can add a test for this to the release plugin itself.
Kristian
2015-04-21 22:24 GMT+02:00 Adrien Rivard :
> Looks like to me it is trying to copy the tag to the tag.
> SCM url should contains "trunk" before starting the release. It is
>
Ok, I'll roll 3.3.3 in the morning.
On Apr 21, 2015, at 11:05 AM, Jason van Zyl wrote:
> I burned the 3.3.2 with a failed staging attempt and I wanted to integrate
> Jan's fix for Wagon so I'll stage 3.3.3.
>
> I have staged Wagon 2.9 which is required for some Maven related fixes. If no
> on
Great, thanks for testing.
On Apr 21, 2015, at 12:54 PM, Dan Tran wrote:
> +1 ( none binding)
>
> Tested maven-3.2.2 with wagon-2.8 swapped out for wagon-2.9
>
> * ssh site deploy works with wagon-2.9 as extension
> * http deploy works
> * wagon ssh download no longer hang
>
> -Dan
>
>
Looks like to me it is trying to copy the tag to the tag.
SCM url should contains "trunk" before starting the release. It is
currently wrong, not sure if it was the case before though your first
release though.
On Tue, Apr 21, 2015 at 9:09 PM, Robert Scholte
wrote:
> different versions of svn
Hi Graham,
I've forked http://git-wip-us.apache.org/repos/asf/maven-scm which builds
fine on Winodws7
Robert
Op Tue, 21 Apr 2015 13:13:04 +0200 schreef Chris Graham
:
I've forked the apache scm repo on github and cloned it locally.
I'm simply trying to build it, before I start making a
different versions of svn clients? svn version of sources not in sync with
client?
Op Tue, 21 Apr 2015 19:58:31 +0200 schreef Kristian Rosenvold
:
I have
140.211.11.105 svn.apache.org in /etc/hosts, which should solve /that/
problem.
I'm particularly wondering about this part of the
I have
140.211.11.105 svn.apache.org in /etc/hosts, which should solve /that/ problem.
I'm particularly wondering about this part of the message, is this
some kind of internal svn uri ?
[ERROR] svn: E160013:
'/repos/asf/!svn/rvr/1675172/maven/plugins/tags/maven-assembly-plugin-2.5.4'
2015-04-
European timing issue?
http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
Op Tue, 21 Apr 2015 19:51:59 +0200 schreef Kristian Rosenvold
:
I'm trying to tag assembly-plugin, but get the following error - any
ideas ?
[INFO] Executing: /bin/sh -c cd
/home/release15/trunk/mave
I'm trying to tag assembly-plugin, but get the following error - any ideas ?
[INFO] Executing: /bin/sh -c cd
/home/release15/trunk/maven-assembly-plugin && svn --non-interactive
copy --file /tmp/maven-scm-1432262679.commit --parents --revision
1675172
https://svn.apache.org/repos/asf/maven/plugin
+1 ( none binding)
Tested maven-3.2.2 with wagon-2.8 swapped out for wagon-2.9
* ssh site deploy works with wagon-2.9 as extension
* http deploy works
* wagon ssh download no longer hang
-Dan
On Tue, Apr 21, 2015 at 7:38 AM, Jason van Zyl wrote:
> Hi,
>
> We have fixed 9 issues:
>
>
+1
On 21 April 2015 at 16:05, Jason van Zyl wrote:
> I burned the 3.3.2 with a failed staging attempt and I wanted to integrate
> Jan's fix for Wagon so I'll stage 3.3.3.
>
> I have staged Wagon 2.9 which is required for some Maven related fixes. If
> no one objects I'll stage Maven 3.3.3 with t
I burned the 3.3.2 with a failed staging attempt and I wanted to integrate
Jan's fix for Wagon so I'll stage 3.3.3.
I have staged Wagon 2.9 which is required for some Maven related fixes. If no
one objects I'll stage Maven 3.3.3 with the staged Wagon 2.9 tomorrow morning.
Thanks,
Jason
--
Hi,
We have fixed 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12331786
Staging repository:
https://repository.apache.org/content/repositories/maven-1171/
Staged site: http://maven.apache.org/wagon-archives/wagon-LATEST/
Vote open for 72H
[+1]
[0]
I've forked the apache scm repo on github and cloned it locally.
I'm simply trying to build it, before I start making any changes at all.
I've run into several issues, something is truly not right here, but I can
not quite work out what.
At the moment, either under 2.2.1 or 3.0.4, I'm getting a
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/10#issuecomment-94748095
@Enygma2002 sure, sorry for the delay, will apply it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user Enygma2002 commented on the pull request:
https://github.com/apache/maven-indexer/pull/11#issuecomment-94742190
Hi,
Is anyone still interested in applying this PR?
Thanks,
Eduard
---
If your project is set up for it, you can reply to this email and h
Github user Enygma2002 commented on the pull request:
https://github.com/apache/maven-indexer/pull/10#issuecomment-94742058
Hi,
Is anyone still interested in applying this PR?
Thanks,
Eduard
---
If your project is set up for it, you can reply to this email and ha
19 matches
Mail list logo
