I don't think we have to 'hack' something ;-)
The main problem is, that the CI build does a 'mvn deploy' to deploy
snapshots - which is basically Ok. However, during a 'mvn release' the CI
build is also triggered because versions are updated to release versions in
SVN. This leads to:
1st deploy of
On Mon, Oct 19, 2009 at 8:45 PM, Matthias Küspert
wrote:
> The directories in under mvn-snapshots (mostly) belong to 'tomcat' while the
> ones in mvn-releases belong to real users.
> In my case the problem was that the release triggered a CI-build (by
> updating versions in SVN) which then publish
I recalled :DWhat solved my problem was updating svn to latest version.
On Mon, Oct 19, 2009 at 11:10 AM, Matthias Küspert wrote:
> Alin, thanks for the tip :-) I found:
> http://osi.fotap.org/2008/07/30/svn-151-breaks-maven-release-plugin/
> Just issuing an 'svn up' and running release:prepare
Hey all,
looking at https://scm.ops4j.org/repos/ops4j/projects/master/pom.xml ...
there are both (snapshot and release) repositories defined in the
repos.ops4j profile. So why not introduce a dedicated CI profile that allows
only snapshots to be deployed:
repos.ci.ops4j
Stuart,
> FWIW I thought we were supposed to be staging releases using Nexus these
> days?
> (ie. "-Prepos.sonatype,release" if you inherit the OPS4J master pom in your
> project)
>
> afaik that should avoid any deployment issue/clash
>
> I know, but since there is a 'repos.ops4j' profile encoura
2009/10/19 Matthias Küspert
> The directories in under mvn-snapshots (mostly) belong to 'tomcat' while
> the ones in mvn-releases belong to real users.
>
FWIW I thought we were supposed to be staging releases using Nexus these
days?
(ie. "-Prepos.sonatype,release" if you inherit the OPS4J master
The directories in under mvn-snapshots (mostly) belong to 'tomcat' while the
ones in mvn-releases belong to real users.
In my case the problem was that the release triggered a CI-build (by
updating versions in SVN) which then published to the 'mvn-releases' dir and
created the ldapserver dir as us
About the permission, look at the dirs for the other pax projects. What
permissions does those ones have?
On Mon, Oct 19, 2009 at 11:10 AM, Matthias Küspert wrote:
> Alin, thanks for the tip :-) I found:
> http://osi.fotap.org/2008/07/30/svn-151-breaks-maven-release-plugin/
> Just issuing an 'sv
Alin, thanks for the tip :-) I found:
http://osi.fotap.org/2008/07/30/svn-151-breaks-maven-release-plugin/
Just issuing an 'svn up' and running release:prepare again did the trick.
However now I get a 'Permission denied' when uploading scpexe://
repository.ops4j.org/var/http/repository.ops4j.org/m
On Mon, Oct 19, 2009 at 3:41 PM, Alin Dreghiciu wrote:
> Matthias,
> I had the same problems a couple of weeks ago. Sounds strange, but damn, I
> forgot what did I do to solve t. Anyhow, it is related to maven and not to
> any configuration from server. Something about the version of release plugi
Matthias,
I had the same problems a couple of weeks ago. Sounds strange, but damn, I
forgot what did I do to solve t. Anyhow, it is related to maven and not to
any configuration from server. Something about the version of release plugin
I guess but now sure.
On Mon, Oct 19, 2009 at 10:14 AM, Matth
I think it is "wrong error"-error...
svn ls https://scm.ops4j.org/repos/ops4j/qa/pax/ldapserver-0.2.0/
says that it doesn't exist...
On Mon, Oct 19, 2009 at 3:14 PM, Matthias Küspert
wrote:
> BTW, I already had some strange SVN behaviour some time ago: I couln't move
> projects from my lab to
I tried and it failed again ... I'm getting the same message:
[INFO] Checking in modified POMs...
[INFO] Executing: svn --username mkuespert --password *
--non-interactive commit --file /tmp/maven-scm-1694897289.commit --targets
/tmp/maven-scm-38192-targets
[INFO] Working directory:
/Users/Matt
Mmh,
not sure what is going on - could you try with 0.2.0 and let us know
if that is ok?
/peter
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org
Thanks Peter - that seemed to work, since now I get another error message
;-)
Maybe one of the release-gurus can enlighten me on that new error. It now
says:
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File
'/repos/ops4j/qa/pax/ldapserver
Hi Mattias,
in order to commit to the /qa branches you have to be in the qroup
"release-managers". I fixed that now, you should be able to release
within 1 hour. Let me know how it goes!
/peter
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.
Hi,
I just tried to prepare a release of the Pax LDAPServer which aborted with:
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: CHECKOUT of '/repos/ops4j/!svn/ver/16440/qa/pax': authorization failed:
Could not authen
17 matches
Mail list logo
