You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-dev@incubator.apache.org by Matthias Wessendorf <ma...@apache.org> on 2007/02/13 11:42:28 UTC
[release] fun with maven
Hi,
since I got some feedback here regarding how to move forward with the
release, I was able to do this nice command (see also svn checkins,
triggered by that tool):
mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
-Ddeploy.altRepository=
scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
ok, that went through
next try was
mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
-Ddeploy.altRepository=
scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
That presents me a nice error in this format.
<niceError>
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] One or more required plugin parameters are invalid/missing
for 'gpg:sign'
[0] inside the definition for plugin: 'maven-gpg-plugin'specify
the following:
<configuration>
...
<passphrase>VALUE</passphrase>
</configuration>
-OR-
on the command line, specify: '-Dpassphrase=VALUE'
</niceError>
Fair enough, my friend needs a passphrase. Well I should add it to the
pom or the command line. But that tool seems to ignore it... (see
above)
Does anyone know how to solve that ?
Thanks,
Matthias
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
trying now
scpexe://people.apache.org/www/people.apache.org/builds/myfaces/trinidad-staging
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > There is no real "staging repo"!
>
> right
>
> > .../people.apache.org/builds/myfaces/m2-staging-repository is nothing
> > more than a temporary folder that is currently used for preparing the
> > core 1.1.5 release. So please use a different staging dir for Trinidad
> > to minimize the risk of unwanted affects on the current core release
> > procedure.
>
> sure, I'll use a different dir for that, just to clear the maven thing first.
> Since there is no real staging repo, I was about to "put" the *release* to that
> (since it is not official).
>
> Doing a vote based on that, and asking the Incubator PMC for approval
> on the stuff in the staging repo.
>
> (Yes, I'll create a trinidad-stage-repo)
>
> > > I read your diary, but you are on a different *environment*. I am
> > > using profiles in the pom.xml etc.
> > >
> > > can you post your settings.xml ?
> >
> > Nothing special in my settings.xml. gpg-plugin workes fine without any
> > settings.
> > Does manual signing with gpg work fine on your machine?
>
> To sign works fine here. Ok, perhaps I just try to deploy the
> "prepared" stuff to something ..... since the -Psign-artifact seams
> to work w/o special things in settings or pom
>
> Thanks,
>
> > --Manfred
> >
> >
> >
> >
> >
> >
> > >
> > >
> > >
> > > On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> > > > Matze,
> > > > First of all, please do not deploy tomahawk into
> > > > .../people.apache.org/builds/myfaces/m2-staging-repository right now.
> > > > We are currently preparing core 1.1.5 in this dir which will later be
> > > > moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
> > > >
> > > > Please create a new staging folder for tomahawk
> > > > e.g.
> > > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > > >
> > > > Thanks!
> > > >
> > > > Specifiying the passphrase with -Dpassphrase=VALUE worked fine for me.
> > > > See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4, last
> > > > step)
> > > >
> > > > BTW, you are doing a "release:perform" before the vote? Why that?
> > > >
> > > > --Manfred
> > > >
> > > >
> > > >
> > > >
> > > > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > Hi,
> > > > >
> > > > > since I got some feedback here regarding how to move forward with the
> > > > > release, I was able to do this nice command (see also svn checkins,
> > > > > triggered by that tool):
> > > > >
> > > > > mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
> > > > > -Ddeploy.altRepository=
> > > > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > > > >
> > > > > ok, that went through
> > > > >
> > > > > next try was
> > > > >
> > > > > mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
> > > > > -Ddeploy.altRepository=
> > > > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > > > >
> > > > > That presents me a nice error in this format.
> > > > >
> > > > > <niceError>
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO] ------------------------------------------------------------------------
> > > > > [INFO] One or more required plugin parameters are invalid/missing
> > > > > for 'gpg:sign'
> > > > >
> > > > > [0] inside the definition for plugin: 'maven-gpg-plugin'specify
> > > > > the following:
> > > > >
> > > > > <configuration>
> > > > > ...
> > > > > <passphrase>VALUE</passphrase>
> > > > > </configuration>
> > > > >
> > > > > -OR-
> > > > >
> > > > > on the command line, specify: '-Dpassphrase=VALUE'
> > > > > </niceError>
> > > > >
> > > > > Fair enough, my friend needs a passphrase. Well I should add it to the
> > > > > pom or the command line. But that tool seems to ignore it... (see
> > > > > above)
> > > > >
> > > > > Does anyone know how to solve that ?
> > > > >
> > > > > Thanks,
> > > > > Matthias
> > > > > --
> > > > > Matthias Wessendorf
> > > > > http://tinyurl.com/fmywh
> > > > >
> > > > > further stuff:
> > > > > blog: http://jroller.com/page/mwessendorf
> > > > > mail: mwessendorf-at-gmail-dot-com
> > > > >
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > http://tinyurl.com/fmywh
> > >
> > > further stuff:
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Martin van den Bemt <ml...@mvdb.net>.
I just stage to my home directory on people..
Mvgr,
Martin
Matthias Wessendorf wrote:
>> There is no real "staging repo"!
>
> right
>
>> .../people.apache.org/builds/myfaces/m2-staging-repository is nothing
>> more than a temporary folder that is currently used for preparing the
>> core 1.1.5 release. So please use a different staging dir for Trinidad
>> to minimize the risk of unwanted affects on the current core release
>> procedure.
>
> sure, I'll use a different dir for that, just to clear the maven thing
> first.
> Since there is no real staging repo, I was about to "put" the *release*
> to that
> (since it is not official).
>
> Doing a vote based on that, and asking the Incubator PMC for approval
> on the stuff in the staging repo.
>
> (Yes, I'll create a trinidad-stage-repo)
>
>> > I read your diary, but you are on a different *environment*. I am
>> > using profiles in the pom.xml etc.
>> >
>> > can you post your settings.xml ?
>>
>> Nothing special in my settings.xml. gpg-plugin workes fine without any
>> settings.
>> Does manual signing with gpg work fine on your machine?
>
> To sign works fine here. Ok, perhaps I just try to deploy the
> "prepared" stuff to something ..... since the -Psign-artifact seams
> to work w/o special things in settings or pom
>
> Thanks,
>
>> --Manfred
>>
>>
>>
>>
>>
>>
>> >
>> >
>> >
>> > On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
>> > > Matze,
>> > > First of all, please do not deploy tomahawk into
>> > > .../people.apache.org/builds/myfaces/m2-staging-repository right now.
>> > > We are currently preparing core 1.1.5 in this dir which will later be
>> > > moved to
>> .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
>> > >
>> > > Please create a new staging folder for tomahawk
>> > > e.g.
>> > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
>> > >
>> > > Thanks!
>> > >
>> > > Specifiying the passphrase with -Dpassphrase=VALUE worked fine for
>> me.
>> > > See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4,
>> last
>> > > step)
>> > >
>> > > BTW, you are doing a "release:perform" before the vote? Why that?
>> > >
>> > > --Manfred
>> > >
>> > >
>> > >
>> > >
>> > > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
>> > > > Hi,
>> > > >
>> > > > since I got some feedback here regarding how to move forward
>> with the
>> > > > release, I was able to do this nice command (see also svn checkins,
>> > > > triggered by that tool):
>> > > >
>> > > > mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
>> > > > -Ddeploy.altRepository=
>> > > >
>> scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
>>
>> > > >
>> > > > ok, that went through
>> > > >
>> > > > next try was
>> > > >
>> > > > mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
>> > > > -Ddeploy.altRepository=
>> > > >
>> scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
>>
>> > > >
>> > > > That presents me a nice error in this format.
>> > > >
>> > > > <niceError>
>> > > > [ERROR] BUILD ERROR
>> > > > [INFO]
>> ------------------------------------------------------------------------
>> > > > [INFO] One or more required plugin parameters are
>> invalid/missing
>> > > > for 'gpg:sign'
>> > > >
>> > > > [0] inside the definition for plugin: 'maven-gpg-plugin'specify
>> > > > the following:
>> > > >
>> > > > <configuration>
>> > > > ...
>> > > > <passphrase>VALUE</passphrase>
>> > > > </configuration>
>> > > >
>> > > > -OR-
>> > > >
>> > > > on the command line, specify: '-Dpassphrase=VALUE'
>> > > > </niceError>
>> > > >
>> > > > Fair enough, my friend needs a passphrase. Well I should add it
>> to the
>> > > > pom or the command line. But that tool seems to ignore it... (see
>> > > > above)
>> > > >
>> > > > Does anyone know how to solve that ?
>> > > >
>> > > > Thanks,
>> > > > Matthias
>> > > > --
>> > > > Matthias Wessendorf
>> > > > http://tinyurl.com/fmywh
>> > > >
>> > > > further stuff:
>> > > > blog: http://jroller.com/page/mwessendorf
>> > > > mail: mwessendorf-at-gmail-dot-com
>> > > >
>> > >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> > http://tinyurl.com/fmywh
>> >
>> > further stuff:
>> > blog: http://jroller.com/page/mwessendorf
>> > mail: mwessendorf-at-gmail-dot-com
>> >
>>
>
>
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
> There is no real "staging repo"!
right
> .../people.apache.org/builds/myfaces/m2-staging-repository is nothing
> more than a temporary folder that is currently used for preparing the
> core 1.1.5 release. So please use a different staging dir for Trinidad
> to minimize the risk of unwanted affects on the current core release
> procedure.
sure, I'll use a different dir for that, just to clear the maven thing first.
Since there is no real staging repo, I was about to "put" the *release* to that
(since it is not official).
Doing a vote based on that, and asking the Incubator PMC for approval
on the stuff in the staging repo.
(Yes, I'll create a trinidad-stage-repo)
> > I read your diary, but you are on a different *environment*. I am
> > using profiles in the pom.xml etc.
> >
> > can you post your settings.xml ?
>
> Nothing special in my settings.xml. gpg-plugin workes fine without any
> settings.
> Does manual signing with gpg work fine on your machine?
To sign works fine here. Ok, perhaps I just try to deploy the
"prepared" stuff to something ..... since the -Psign-artifact seams
to work w/o special things in settings or pom
Thanks,
> --Manfred
>
>
>
>
>
>
> >
> >
> >
> > On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> > > Matze,
> > > First of all, please do not deploy tomahawk into
> > > .../people.apache.org/builds/myfaces/m2-staging-repository right now.
> > > We are currently preparing core 1.1.5 in this dir which will later be
> > > moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
> > >
> > > Please create a new staging folder for tomahawk
> > > e.g.
> > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > >
> > > Thanks!
> > >
> > > Specifiying the passphrase with -Dpassphrase=VALUE worked fine for me.
> > > See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4, last
> > > step)
> > >
> > > BTW, you are doing a "release:perform" before the vote? Why that?
> > >
> > > --Manfred
> > >
> > >
> > >
> > >
> > > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > Hi,
> > > >
> > > > since I got some feedback here regarding how to move forward with the
> > > > release, I was able to do this nice command (see also svn checkins,
> > > > triggered by that tool):
> > > >
> > > > mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
> > > > -Ddeploy.altRepository=
> > > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > > >
> > > > ok, that went through
> > > >
> > > > next try was
> > > >
> > > > mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
> > > > -Ddeploy.altRepository=
> > > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > > >
> > > > That presents me a nice error in this format.
> > > >
> > > > <niceError>
> > > > [ERROR] BUILD ERROR
> > > > [INFO] ------------------------------------------------------------------------
> > > > [INFO] One or more required plugin parameters are invalid/missing
> > > > for 'gpg:sign'
> > > >
> > > > [0] inside the definition for plugin: 'maven-gpg-plugin'specify
> > > > the following:
> > > >
> > > > <configuration>
> > > > ...
> > > > <passphrase>VALUE</passphrase>
> > > > </configuration>
> > > >
> > > > -OR-
> > > >
> > > > on the command line, specify: '-Dpassphrase=VALUE'
> > > > </niceError>
> > > >
> > > > Fair enough, my friend needs a passphrase. Well I should add it to the
> > > > pom or the command line. But that tool seems to ignore it... (see
> > > > above)
> > > >
> > > > Does anyone know how to solve that ?
> > > >
> > > > Thanks,
> > > > Matthias
> > > > --
> > > > Matthias Wessendorf
> > > > http://tinyurl.com/fmywh
> > > >
> > > > further stuff:
> > > > blog: http://jroller.com/page/mwessendorf
> > > > mail: mwessendorf-at-gmail-dot-com
> > > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Manfred Geiler <ma...@gmail.com>.
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> You mean trinidad instead of tomahawk :-)
Yes of course. The three T's. Hard to distinguish... :-)
> I tried (I didn't) because as I got it here, the "release" will be
> deployed in the staging repo. It's not really a release, since an
> incubation project needs approval by the Incubator PMC.
There is no real "staging repo"!
.../people.apache.org/builds/myfaces/m2-staging-repository is nothing
more than a temporary folder that is currently used for preparing the
core 1.1.5 release. So please use a different staging dir for Trinidad
to minimize the risk of unwanted affects on the current core release
procedure.
> I read your diary, but you are on a different *environment*. I am
> using profiles in the pom.xml etc.
>
> can you post your settings.xml ?
Nothing special in my settings.xml. gpg-plugin workes fine without any
settings.
Does manual signing with gpg work fine on your machine?
--Manfred
>
>
>
> On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> > Matze,
> > First of all, please do not deploy tomahawk into
> > .../people.apache.org/builds/myfaces/m2-staging-repository right now.
> > We are currently preparing core 1.1.5 in this dir which will later be
> > moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
> >
> > Please create a new staging folder for tomahawk
> > e.g.
> > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> >
> > Thanks!
> >
> > Specifiying the passphrase with -Dpassphrase=VALUE worked fine for me.
> > See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4, last
> > step)
> >
> > BTW, you are doing a "release:perform" before the vote? Why that?
> >
> > --Manfred
> >
> >
> >
> >
> > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > Hi,
> > >
> > > since I got some feedback here regarding how to move forward with the
> > > release, I was able to do this nice command (see also svn checkins,
> > > triggered by that tool):
> > >
> > > mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
> > > -Ddeploy.altRepository=
> > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > >
> > > ok, that went through
> > >
> > > next try was
> > >
> > > mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
> > > -Ddeploy.altRepository=
> > > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> > >
> > > That presents me a nice error in this format.
> > >
> > > <niceError>
> > > [ERROR] BUILD ERROR
> > > [INFO] ------------------------------------------------------------------------
> > > [INFO] One or more required plugin parameters are invalid/missing
> > > for 'gpg:sign'
> > >
> > > [0] inside the definition for plugin: 'maven-gpg-plugin'specify
> > > the following:
> > >
> > > <configuration>
> > > ...
> > > <passphrase>VALUE</passphrase>
> > > </configuration>
> > >
> > > -OR-
> > >
> > > on the command line, specify: '-Dpassphrase=VALUE'
> > > </niceError>
> > >
> > > Fair enough, my friend needs a passphrase. Well I should add it to the
> > > pom or the command line. But that tool seems to ignore it... (see
> > > above)
> > >
> > > Does anyone know how to solve that ?
> > >
> > > Thanks,
> > > Matthias
> > > --
> > > Matthias Wessendorf
> > > http://tinyurl.com/fmywh
> > >
> > > further stuff:
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
You mean trinidad instead of tomahawk :-)
I tried (I didn't) because as I got it here, the "release" will be
deployed in the staging repo. It's not really a release, since an
incubation project needs approval by the Incubator PMC.
I read your diary, but you are on a different *environment*. I am
using profiles in the pom.xml etc.
can you post your settings.xml ?
On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> Matze,
> First of all, please do not deploy tomahawk into
> .../people.apache.org/builds/myfaces/m2-staging-repository right now.
> We are currently preparing core 1.1.5 in this dir which will later be
> moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
>
> Please create a new staging folder for tomahawk
> e.g.
> .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
>
> Thanks!
>
> Specifiying the passphrase with -Dpassphrase=VALUE worked fine for me.
> See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4, last
> step)
>
> BTW, you are doing a "release:perform" before the vote? Why that?
>
> --Manfred
>
>
>
>
> On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > Hi,
> >
> > since I got some feedback here regarding how to move forward with the
> > release, I was able to do this nice command (see also svn checkins,
> > triggered by that tool):
> >
> > mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
> > -Ddeploy.altRepository=
> > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> >
> > ok, that went through
> >
> > next try was
> >
> > mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
> > -Ddeploy.altRepository=
> > scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
> >
> > That presents me a nice error in this format.
> >
> > <niceError>
> > [ERROR] BUILD ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] One or more required plugin parameters are invalid/missing
> > for 'gpg:sign'
> >
> > [0] inside the definition for plugin: 'maven-gpg-plugin'specify
> > the following:
> >
> > <configuration>
> > ...
> > <passphrase>VALUE</passphrase>
> > </configuration>
> >
> > -OR-
> >
> > on the command line, specify: '-Dpassphrase=VALUE'
> > </niceError>
> >
> > Fair enough, my friend needs a passphrase. Well I should add it to the
> > pom or the command line. But that tool seems to ignore it... (see
> > above)
> >
> > Does anyone know how to solve that ?
> >
> > Thanks,
> > Matthias
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Bernd Bohmann <be...@atanion.com>.
Oh, last time I don't call mvn release:perform.
I call mvn deploy directly.
mvn release:perform is executing mvn again and don't copy the -D parameter.
Please add following configuration to the gpg plugin
<configuration>
<passphrase>${gpg.passphrase}</passphrase>
</configuration>
and add following profiles to your ${HOME}/.m2/settings.xml
<profiles>
<profile>
<id>staging</id>
<properties>
<deploy.altRepository>scpexe://minotaur.apache.org/www/people.apache.org/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</deploy.altRepository>
</properties>
</profile>
<profile>
<id>release</id>
<properties>
<gpg.passphrase>XXXXXXXXXXXXXXXXXXXXXXXXXXXXx</gpg.passphrase>
</properties>
</profile>
</profiles>
and call only
mvn release:perform -Prelease,staging
Bernd
Matthias Wessendorf wrote:
> one more ... now getting this:
>
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> The authenticity of host 'people.apache.org' can't be established.
> DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
>
>
> I've done this
>
> mvn release:perform -Prelease,staging -Ddeploy.altRepository=theRepoURL
>
> what's wrong here ?
>
>
> Thanks,
> Matthias
>
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
Ok, I switched to a local staging directory and that URL
(matzew::default::file:/trinidad-stage) worked.
But..... I figured out another bug in Maven. I searched the maven list
and came to an issue that another user was also seeing. The source-jar
build was skipped, after the size has reached 4 GB :)
The work around came from Apache Jakarta:
<plugin>
<!-- This should possibly better be done by using a resource
definition. However, if we declare a resource with
${basedir} as the base directory, then the
maven-source-plugin will add the whole directory to
its contents.
-->
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>generate-resources</phase>
<configuration>
<tasks>
<copy todir="${project.build.outputDirectory}/META-INF">
<fileset dir="${basedir}">
<include name="LICENSE.txt" />
<include name="NOTICE.txt" />
</fileset>
</copy>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
I pinging the codehaus guys regarding the seen issue.
-Matthias
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> my main concern is the
>
> altDeploymentRepository = null
>
> line ...
>
> that sounds like the other param is also ignored.
>
> Ok, I'll check all your feedback tomorrow morning.
> Thanks so far.
>
> -Matze
>
> On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> > Try a manual scp connect first to add the server fingerprint to your
> > ssh "trusted server list".
> >
> > --Manfred
> >
> >
> > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > one more ... now getting this:
> > >
> > > [INFO] [deploy:deploy]
> > > altDeploymentRepository = null
> > > The authenticity of host 'people.apache.org' can't be established.
> > > DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
> > >
> > >
> > > I've done this
> > >
> > > mvn release:perform -Prelease,staging -Ddeploy.altRepository=theRepoURL
> > >
> > > what's wrong here ?
> > >
> > >
> > > Thanks,
> > > Matthias
> > >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
my main concern is the
altDeploymentRepository = null
line ...
that sounds like the other param is also ignored.
Ok, I'll check all your feedback tomorrow morning.
Thanks so far.
-Matze
On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> Try a manual scp connect first to add the server fingerprint to your
> ssh "trusted server list".
>
> --Manfred
>
>
> On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > one more ... now getting this:
> >
> > [INFO] [deploy:deploy]
> > altDeploymentRepository = null
> > The authenticity of host 'people.apache.org' can't be established.
> > DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
> >
> >
> > I've done this
> >
> > mvn release:perform -Prelease,staging -Ddeploy.altRepository=theRepoURL
> >
> > what's wrong here ?
> >
> >
> > Thanks,
> > Matthias
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Manfred Geiler <ma...@gmail.com>.
Try a manual scp connect first to add the server fingerprint to your
ssh "trusted server list".
--Manfred
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> one more ... now getting this:
>
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> The authenticity of host 'people.apache.org' can't be established.
> DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
>
>
> I've done this
>
> mvn release:perform -Prelease,staging -Ddeploy.altRepository=theRepoURL
>
> what's wrong here ?
>
>
> Thanks,
> Matthias
>
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
one more ... now getting this:
[INFO] [deploy:deploy]
altDeploymentRepository = null
The authenticity of host 'people.apache.org' can't be established.
DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
I've done this
mvn release:perform -Prelease,staging -Ddeploy.altRepository=theRepoURL
what's wrong here ?
Thanks,
Matthias
Re: [release] fun with maven
Posted by Manfred Geiler <ma...@gmail.com>.
No, it's nothing with the gpg-plugin.
What you are doing is something like mvn release:perform
-Dpassphrase=xxxx, right?
Well, the release:perform does a svn checkout to work folder and then
forks a new mvn deploy process. But: It seems like the command-line
properties are not passed over! That's the problem.
Solution:
Define a property in your settings.xml:
<profile>
<id>gpg-passphrase</id>
<properties>
<passphrase>???</passphrase>
</properties>
</profile>
and
either activate it by default:
<activeProfiles>
<activeProfile>gpg-passphrase</activeProfile>
</activeProfiles>
or activate it by adding a -Pgpg-passphrase to the command line.
HTH,
Manfred
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> I think it is the plugin.
>
> check out and changing the code
> (GpgSignAttachedMojo)
> /**
> * The passphrase to use when signing.
> *
> * @parameter expression="${passphrase}" default-value="xxxxxx"
> * @required
> */
> private String passphrase;
>
>
> takes me to another exception, but that can be triggered by my running VPN
>
> -M
>
> On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > Looks like the -Dpassphrase get's ignored
> >
> > [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> > -DperformRelease=true
> >
> >
> >
> > <snip>
> > [INFO] Scanning for projects...
> > [INFO] Reactor build order:
> > [INFO] Maven Apache Plugin Parent
> > [INFO] Maven Faces Plugin
> > [INFO] Maven Javacc Plugin
> > [INFO] Maven i18n Plugin
> > [INFO] Maven JDev Plugin
> > [INFO] Maven Javascript Plugin
> > [INFO] Maven XRTS Plugin
> > [INFO] Maven Tag Documentation Report
> > [INFO] Apache MyFaces Trinidad Archetype
> > [INFO] Searching repository for plugin with prefix: 'release'.
> > [INFO] ----------------------------------------------------------------------------
> > [INFO] Building Maven Apache Plugin Parent
> > [INFO] task-segment: [release:perform] (aggregator-style)
> > [INFO] ----------------------------------------------------------------------------
> > [INFO] [release:perform]
> > [INFO] Checking out the project to perform the release ...
> > [INFO] Executing: svn --non-interactive checkout
> > https://svn.apache.org/repos/asf/incubator/adffaces/tags/maven-plugin-p
> > arent-1.0.0-incubating checkout
> > [INFO] Working directory: D:\Apache\_release\last\target
> > [INFO] Unknown file status: ' '.
> > [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> > -DperformRelease=true
> > [INFO] Scanning for projects...
> > [INFO] Reactor build order:
> > [INFO] Maven Apache Plugin Parent
> > [INFO] Maven Faces Plugin
> > [INFO] Maven Javacc Plugin
> > [INFO] Maven i18n Plugin
> > [INFO] Maven JDev Plugin
> > [INFO] Maven Javascript Plugin
> > [INFO] Maven XRTS Plugin
> > [INFO] Maven Tag Documentation Report
> > [INFO] Apache MyFaces Trinidad Archetype
> >
> > On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > we use this,
> > >
> > > <parent>
> > > <groupId>org.apache</groupId>
> > > <artifactId>apache</artifactId>
> > > <version>3</version>
> > > </parent>
> > >
> > > was suggested on the general incubator list
> > >
> > > On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > > On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > > > > Please create a new staging folder for tomahawk
> > > > > > e.g.
> > > > > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > > > >
> > > > > To get this to work you'll probably have to add
> > > > > <distributionManagement><repository> to the trinidad pom.
> > > > >
> > > > > (I don't think you can override that on the command line.)
> > > >
> > > > Actually... unless the trinidad pom has myfaces-master as its parent,
> > > > this does not apply.
> > > >
> > > > --
> > > > Wendy
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > http://tinyurl.com/fmywh
> > >
> > > further stuff:
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
I think it is the plugin.
check out and changing the code
(GpgSignAttachedMojo)
/**
* The passphrase to use when signing.
*
* @parameter expression="${passphrase}" default-value="xxxxxx"
* @required
*/
private String passphrase;
takes me to another exception, but that can be triggered by my running VPN
-M
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> Looks like the -Dpassphrase get's ignored
>
> [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> -DperformRelease=true
>
>
>
> <snip>
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Apache Plugin Parent
> [INFO] Maven Faces Plugin
> [INFO] Maven Javacc Plugin
> [INFO] Maven i18n Plugin
> [INFO] Maven JDev Plugin
> [INFO] Maven Javascript Plugin
> [INFO] Maven XRTS Plugin
> [INFO] Maven Tag Documentation Report
> [INFO] Apache MyFaces Trinidad Archetype
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Apache Plugin Parent
> [INFO] task-segment: [release:perform] (aggregator-style)
> [INFO] ----------------------------------------------------------------------------
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: svn --non-interactive checkout
> https://svn.apache.org/repos/asf/incubator/adffaces/tags/maven-plugin-p
> arent-1.0.0-incubating checkout
> [INFO] Working directory: D:\Apache\_release\last\target
> [INFO] Unknown file status: ' '.
> [INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
> -DperformRelease=true
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Maven Apache Plugin Parent
> [INFO] Maven Faces Plugin
> [INFO] Maven Javacc Plugin
> [INFO] Maven i18n Plugin
> [INFO] Maven JDev Plugin
> [INFO] Maven Javascript Plugin
> [INFO] Maven XRTS Plugin
> [INFO] Maven Tag Documentation Report
> [INFO] Apache MyFaces Trinidad Archetype
>
> On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > we use this,
> >
> > <parent>
> > <groupId>org.apache</groupId>
> > <artifactId>apache</artifactId>
> > <version>3</version>
> > </parent>
> >
> > was suggested on the general incubator list
> >
> > On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > > > Please create a new staging folder for tomahawk
> > > > > e.g.
> > > > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > > >
> > > > To get this to work you'll probably have to add
> > > > <distributionManagement><repository> to the trinidad pom.
> > > >
> > > > (I don't think you can override that on the command line.)
> > >
> > > Actually... unless the trinidad pom has myfaces-master as its parent,
> > > this does not apply.
> > >
> > > --
> > > Wendy
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
Looks like the -Dpassphrase get's ignored
[INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
-DperformRelease=true
<snip>
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Maven Apache Plugin Parent
[INFO] Maven Faces Plugin
[INFO] Maven Javacc Plugin
[INFO] Maven i18n Plugin
[INFO] Maven JDev Plugin
[INFO] Maven Javascript Plugin
[INFO] Maven XRTS Plugin
[INFO] Maven Tag Documentation Report
[INFO] Apache MyFaces Trinidad Archetype
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Apache Plugin Parent
[INFO] task-segment: [release:perform] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: svn --non-interactive checkout
https://svn.apache.org/repos/asf/incubator/adffaces/tags/maven-plugin-p
arent-1.0.0-incubating checkout
[INFO] Working directory: D:\Apache\_release\last\target
[INFO] Unknown file status: ' '.
[INFO] Executing: mvn deploy --no-plugin-updates -P release,staging
-DperformRelease=true
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Maven Apache Plugin Parent
[INFO] Maven Faces Plugin
[INFO] Maven Javacc Plugin
[INFO] Maven i18n Plugin
[INFO] Maven JDev Plugin
[INFO] Maven Javascript Plugin
[INFO] Maven XRTS Plugin
[INFO] Maven Tag Documentation Report
[INFO] Apache MyFaces Trinidad Archetype
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> we use this,
>
> <parent>
> <groupId>org.apache</groupId>
> <artifactId>apache</artifactId>
> <version>3</version>
> </parent>
>
> was suggested on the general incubator list
>
> On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > > Please create a new staging folder for tomahawk
> > > > e.g.
> > > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> > >
> > > To get this to work you'll probably have to add
> > > <distributionManagement><repository> to the trinidad pom.
> > >
> > > (I don't think you can override that on the command line.)
> >
> > Actually... unless the trinidad pom has myfaces-master as its parent,
> > this does not apply.
> >
> > --
> > Wendy
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Matthias Wessendorf <ma...@apache.org>.
we use this,
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>3</version>
</parent>
was suggested on the general incubator list
On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > Please create a new staging folder for tomahawk
> > > e.g.
> > > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
> >
> > To get this to work you'll probably have to add
> > <distributionManagement><repository> to the trinidad pom.
> >
> > (I don't think you can override that on the command line.)
>
> Actually... unless the trinidad pom has myfaces-master as its parent,
> this does not apply.
>
> --
> Wendy
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [release] fun with maven
Posted by Wendy Smoak <ws...@gmail.com>.
On 2/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > Please create a new staging folder for tomahawk
> > e.g.
> > .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
>
> To get this to work you'll probably have to add
> <distributionManagement><repository> to the trinidad pom.
>
> (I don't think you can override that on the command line.)
Actually... unless the trinidad pom has myfaces-master as its parent,
this does not apply.
--
Wendy
Re: [release] fun with maven
Posted by Wendy Smoak <ws...@gmail.com>.
On 2/13/07, Manfred Geiler <ma...@gmail.com> wrote:
> Matze,
> First of all, please do not deploy tomahawk into
> .../people.apache.org/builds/myfaces/m2-staging-repository right now.
> We are currently preparing core 1.1.5 in this dir which will later be
> moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
>
> Please create a new staging folder for tomahawk
> e.g.
> .../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
To get this to work you'll probably have to add
<distributionManagement><repository> to the trinidad pom.
(I don't think you can override that on the command line.)
--
Wendy
Re: [release] fun with maven
Posted by Manfred Geiler <ma...@gmail.com>.
Matze,
First of all, please do not deploy tomahawk into
.../people.apache.org/builds/myfaces/m2-staging-repository right now.
We are currently preparing core 1.1.5 in this dir which will later be
moved to .../people.apache.org/builds/myfaces/core-1.1.5/m2-staging-repository.
Please create a new staging folder for tomahawk
e.g.
.../people.apache.org/builds/myfaces/tomahawk/m2-staging-repository
Thanks!
Specifiying the passphrase with -Dpassphrase=VALUE worked fine for me.
See http://wiki.apache.org/myfaces/CoreRelease115#diary (Point 4, last
step)
BTW, you are doing a "release:perform" before the vote? Why that?
--Manfred
On 2/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
> Hi,
>
> since I got some feedback here regarding how to move forward with the
> release, I was able to do this nice command (see also svn checkins,
> triggered by that tool):
>
> mvn release:prepare -Prelease,staging -Dpassphrase=myPhrase
> -Ddeploy.altRepository=
> scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
>
> ok, that went through
>
> next try was
>
> mvn release:perform -Prelease,staging -Dpassphrase=myPhrase
> -Ddeploy.altRepository=
> scpexe://people.apache.org/www/people.apache.org/builds/myfaces/m2-staging-repository
>
> That presents me a nice error in this format.
>
> <niceError>
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] One or more required plugin parameters are invalid/missing
> for 'gpg:sign'
>
> [0] inside the definition for plugin: 'maven-gpg-plugin'specify
> the following:
>
> <configuration>
> ...
> <passphrase>VALUE</passphrase>
> </configuration>
>
> -OR-
>
> on the command line, specify: '-Dpassphrase=VALUE'
> </niceError>
>
> Fair enough, my friend needs a passphrase. Well I should add it to the
> pom or the command line. But that tool seems to ignore it... (see
> above)
>
> Does anyone know how to solve that ?
>
> Thanks,
> Matthias
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>