Daniel,

your command/suggestion did it for me, again :-)

the profile is sorta legacy, I used to have it in my old settings;

So; I'll upload the new stuff tomorrow and do a "re-run" of that vote.

But not sure, if the obfuscated JS files are still an issue
(sorta generated files).

Thanks,
Matthias

On 3/20/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:

Matthias,

On Tuesday 20 March 2007 15:10, Matthias Wessendorf wrote:
> here is the cmd I used:
>
> <cmd>
> mvn clean install source:jar javadoc:jar deploy
> -DaltDeploymentRepository=matzew::default::file:/apache_myfaces_trinid
>ad_core_stage -Psign-artifacts -Dpassphrase=keepItSecretBaby
> </cmd>
>

That would do it.   The install and deploy target would both have
separate lifecycles that would cause the double signing.

You also don't have a sign-artifacts profile.   The switch isn't needed.

My suggestions:
1) Remove it from the build/plugins list.
2) Uncomment the javadoc plugin from the release profile.  (new version
of remote-resources fixes the bug that required that to be commented
out)

Then just run:

mvn -Prelease deploy  \
    -DaltDeploymentRepository=matzew::default::file:/a......

Don't specify the passphrase.   The new version of gpg will ask you for
it.


Dan






> Would it "help" to do a "evil" remove of ".asc.asc" file, in the stage
> `? (yes, a hack, I guess ;-))
>
> Thanks for the feedback,
> Matthias
>
> On 3/20/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> > On Tuesday 20 March 2007 14:36, Matthias Wessendorf wrote:
> > > > (suggestions not requirements)
> > > >
> > > > http://people.apache.org/~matzew/stage_trin_core/org/apache/myfa
> > > >ces/ trinidad/trinidad-api/1.0.0-incubating/ has some crazy
> > > > signing of signatures asc.asc
> > >
> > > yep, not really sure why, using the maven-gpg-plugin, as mentioned
> > > above.
> >
> > Sounds like some interaction with a forked lifecycle which is
> > causing the gpg plugin to run twice.  The first time, it signs
> > everything and attaches the asc files to be deployed.   Then the
> > second time, it runs again signing everything, including the asc
> > files attached the first time.
> >
> > What's the complete command you're using?
> >
> > We probably could/should have the gpg plugin exclude signing
> > anything ending in .asc, .sha1, .md5.
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727    C: 508-380-7194
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog
> >
> > --------------------------------------------------------------------
> >- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Matthias Wessendorf
http://tinyurl.com/fmywh

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to