trying now

scpexe://people.apache.org/www/people.apache.org/builds/myfaces/trinidad-staging

On 2/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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

Reply via email to