Thanks Oliver!
It just hanged for more then two hours, then I just stopped it - sorry if this
was too short, I did not expect it to take as long.
/Domi
On 07.01.2014, at 08:28, Hervé BOUTEMY herve.bout...@free.fr wrote:
in the short term, Olivier did the publication: job done
but let's
Doxia was at least 1.5hr for me, so 2h wouldn't surprise me at all.
On Tuesday, 7 January 2014, Dominik Bartholdi wrote:
Thanks Oliver!
It just hanged for more then two hours, then I just stopped it - sorry if
this was too short, I did not expect it to take as long.
/Domi
On 07.01.2014, at
For the last surefire releases, I just created a tar.gz from the local
site, uploaded it to people.a.o via SCP and did the commit from there. Was
a matter of minutes instead of hours. It's cumbersome, though...
A pretty large part of the files is the Javadoc. And I don't know about you
guys, but
Hey guys,
I finally started the release of scm-1.9 - I was able to stage the artifacts,
but now , following this process
http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
I would have to close the staging repo (as described here
Did you log into repository.apache.org?
On Mon, Jan 6, 2014 at 1:44 PM, Dominik Bartholdi d...@fortysix.ch wrote:
Hey guys,
I finally started the release of scm-1.9 - I was able to stage the artifacts,
but now , following this process
Are you imod? If so, the repo is sitting there. I can close it for
you, but you should try logging in and closing it for yourself.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Thanks, I was searching for it on the sonatype OSS Nexus - now I can see it!
Lets see how far I get now :)
Domi
On 06.01.2014, at 19:56, Benson Margulies bimargul...@gmail.com wrote:
Are you imod? If so, the repo is sitting there. I can close it for
you, but you should try logging in and
My next problem…
does any one have any idea?
Publishing the page always hangs here (more then 30 Minutes, actually never
ends...):
mvn scm-publish:publish-scm -Dusername=imod -Dpassword=x
….
[INFO]
[INFO] Building Maven
Just be patient, it is a huge commit.
All changes to the documentation of the whole(!) SCM site are committed at
once.
Robert
Op Mon, 06 Jan 2014 22:23:59 +0100 schreef Dominik Bartholdi
d...@fortysix.ch:
My next problem…
does any one have any idea?
Publishing the page always hangs here
I don't know if you stop trying this but if needed I can do it for
you, I use an external ci server to not block my laptop and be able to
continue various music, videos etc...
Just let me know.
On 7 January 2014 08:23, Dominik Bartholdi d...@fortysix.ch wrote:
My next problem…
does any one have
Hi Oliver,
I tried over and over again - it just does not work out on my Mac - I’m not
able to publish the Documentation.
Would be great if you could do it - everything else (the artifacts) are already
done (https://repository.apache.org/content/repositories/maven-009/).
thanks Domi
On
done: http://maven.apache.org/scm-archives/scm-LATEST/
On 7 January 2014 15:52, Dominik Bartholdi d...@fortysix.ch wrote:
Hi Oliver,
I tried over and over again - it just does not work out on my Mac - I’m not
able to publish the Documentation.
Would be great if you could do it - everything
If you're in europe you should probably set the us svn server in your hosts
file; someone here will give you the magic settings :)
I tend to cross my fingers and let site publication run overnight. All the
different site publication strategies have been flawed in one way or
another, this latest
in the short term, Olivier did the publication: job done
but let's understand what does not work: did you get a failure? Or only you
stopped the publication process after some (long) time?
Regards,
Hervé
Le mardi 7 janvier 2014 05:52:16 Dominik Bartholdi a écrit :
Hi Oliver,
I tried over
IMHO the latest strategy is good for main site content: ie we can now publish
a modification in plugins list, for example, in a few minutes, with a site
being build in a consistent manner (no more anybody frightened to break the
site because something in his conf is different)
but for
Thanks Robert,
I’ll give it a go, but its gona be my first “official maven plugin release”, so
please be patient :)
/Domi
On 30.12.2013, at 13:07, Robert Scholte rfscho...@apache.org wrote:
Personally I think it is important that the source-releases.zip can at least
be built somewhere. The
Domi, you knew that day would come sooner or later, right? ;)
Op Fri, 03 Jan 2014 08:58:59 +0100 schreef Dominik Bartholdi
d...@fortysix.ch:
Thanks Robert,
I’ll give it a go, but its gona be my first “official maven plugin
release”, so please be patient :)
/Domi
On 30.12.2013, at
And better to get your feet wet early after all ;-)
On 3 January 2014 10:43, Robert Scholte rfscho...@apache.org wrote:
Domi, you knew that day would come sooner or later, right? ;)
Op Fri, 03 Jan 2014 08:58:59 +0100 schreef Dominik Bartholdi
d...@fortysix.ch:
Thanks Robert,
I’ll
I was hopping for a drysuite :)
On 03.01.2014, at 11:49, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
And better to get your feet wet early after all ;-)
On 3 January 2014 10:43, Robert Scholte rfscho...@apache.org wrote:
Domi, you knew that day would come sooner or later,
Personally I think it is important that the source-releases.zip can at
least be built somewhere. The more the better of course. If Windows isn't
the right OS, then that's fine for me.
@Domi, if nobody sees any blockers, could you start a take 3?
thanks,
Robert
Op Fri, 27 Dec 2013 10:00:07
Hi Robert,
I had a go too,
on Mac everything is OK -
but on Win with SVN 1.8.5 the maven-scm-plugin failed to create the repository
:(
regards Domi
On 24.12.2013, at 22:26, Robert Scholte rfscho...@apache.org wrote:
Hi,
I've fixed SCM-737, which means that the source-releases.zip should
Hi,
I've fixed SCM-737, which means that the source-releases.zip should match
all the files project files again.
If I'm correct this means that the reason for the -1 vote has been solved.
However, on my Windows machine I don't get the test for the
maven-scm-plugin to succeed.
The svnadmin
Thanks Oliver,
its a bit disappointing, as this at the end (at least for me) also means the
other scm components are not maintainable anymore…
Taking this into account, then its probably a better idea to not have this
under the apache umbrella anyway.
Where do you think we should release it
Stephens remarks are valid, let me try to pick this up in the next couple
of weeks.
Robert
Op Thu, 19 Dec 2013 18:31:13 +0100 schreef Dominik Bartholdi
d...@fortysix.ch:
Thanks Oliver,
its a bit disappointing, as this at the end (at least for me) also means
the other scm components are
I think all the crap/trolling in the release threads has gone way too far,
it's just not fun any more.
I can only request that PMC members chip in *before* the the vote to
/improve/ technical problems with a release
rather than spending a ton of energy documenting their -1 *after* the
release is
On Thursday, 19 December 2013, Kristian Rosenvold wrote:
I think all the crap/trolling in the release threads has gone way too far,
it's just not fun any more.
I can only request that PMC members chip in *before* the the vote to
/improve/ technical problems with a release
rather than
I usually ignore threads when they degenerate into procedural discussions
and I'll guarantee supress any voting thread where the first thing that
comes out is a -1; I've got coding to do.
Sorry for being an idiot, I'm usually quite good at keeping my foot out of
my mouth. Can't always get it
So that's 2 weeks now.
I presume I can say the vote failed.
I will delete the tag and the staging repo.
If someone else want to act RM let's go. perso I'm tired
@Domi I'm sorry I believed if was a good idea to have the module jgit
here (but cvs looks to me more important :P ).
Anyway we can
OK, then you have my +1
/Domi
On 03.12.2013, at 08:20, Olivier Lamy ol...@apache.org wrote:
No worries.
IMHO it's not the problem. Issue is cvs-commons module.
--
Olivier
On Dec 3, 2013 3:34 PM, Dominik Bartholdi d...@fortysix.ch wrote:
Sorry guys, during the week I’m usually a bit
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=18783
Staging repository:
https://repository.apache.org/content/repositories/maven-002/
Staged site:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
a0fdae255eebc2dfbd0f973073f7c97284b5f9f9.
* The source bundle does not build.
If I look at the difference between the tag and the source bundle I see the
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
a0fdae255eebc2dfbd0f973073f7c97284b5f9f9.
* The source bundle does
On Monday, 2 December 2013, Olivier Lamy wrote:
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
-1, for the following reasons
* No checksum of the source bundle in the email, per current vote email
format: FTR SHA1 of bundle I checked is
On 3 December 2013 11:18, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Monday, 2 December 2013, Olivier Lamy wrote:
On 2 December 2013 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
-1, for the following reasons
* No checksum of the source
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't understand yet why defaultExclude=false
doesn't work for CVS directories.
Uh, isnt that supposed to be yes to enable the exclusion of default
patterns?
Gruss
Bernd
On 3 December 2013 12:52, Bernd Eckenfels e...@zusammenkunft.net wrote:
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't understand yet why defaultExclude=false
doesn't work for CVS directories.
Uh, isnt that supposed to be yes to enable the
I dunno, change the version to 2.0 and remove support for CVS?
On Mon, Dec 2, 2013 at 8:57 PM, Olivier Lamy ol...@apache.org wrote:
On 3 December 2013 12:52, Bernd Eckenfels e...@zusammenkunft.net wrote:
Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy ol...@apache.org:
For some reasons I don't
now that:
1. the problem is known
2. its impact estimated low: only tests for CVS provider
IMHO, we can afford releasing as is and creating a Jira issue to find a better
solution later
Regards,
Hervé
Le mardi 3 décembre 2013 12:47:55 Olivier Lamy a écrit :
On 3 December 2013 11:18, Stephen
+1
need to find a workaround for CVS provider unit tests later
Regards,
Hervé
Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit :
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/browse/SCM-737 created
Le mardi 3 décembre 2013 03:05:17 Hervé BOUTEMY a écrit :
+1
need to find a workaround for CVS provider unit tests later
Regards,
Hervé
Le lundi 2 décembre 2013 19:38:41 Olivier Lamy a écrit :
Hi,
We fixed 11 issues. The new
Sorry guys, during the week I’m usually a bit short in time…
But is ist possible, that my commit d1f102e5223e5fe0f852e1a5becb497f0e860d6a is
actually causing this issue?
Its an exclude of some CVS stuff I had in my untracked list all the time when
doing a full build...
regards Domi
On
No worries.
IMHO it's not the problem. Issue is cvs-commons module.
--
Olivier
On Dec 3, 2013 3:34 PM, Dominik Bartholdi d...@fortysix.ch wrote:
Sorry guys, during the week I’m usually a bit short in time…
But is ist possible, that my commit
d1f102e5223e5fe0f852e1a5becb497f0e860d6a is
42 matches
Mail list logo
