Re: versioning

I go with 1.0.0-incubating-SNAPSHOT thanks, Matthias On 2/4/07, Martin Marinschek [EMAIL PROTECTED] wrote: Sure, d'accord - just like the Tomcat folks do it, it doesn't make sense to keep the product versions fully at the spec or API versions. We should do the same for MyFaces and Tomahawk,

[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=

Re: [release] fun with maven

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

Re: [release] fun with maven

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

Re: [release] fun with maven

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

Re: [release] vote ??

ok, I think next step is doing a checkout on the tag (1.0.0-inc) and build the stuff and do the vote ... do you agree ? On 2/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, I was able to prepare the relase, based on the given feedback. Maven created already a TAG for that (see [1]).

Re: [release] fun with maven

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

Re: [release] vote ??

Yes, IMHO you should build and sign all the stuff, deploy it to a temporary staging dir and start a vote on those artifacts. Regards, Manfred On 2/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: ok, I think next step is doing a checkout on the tag (1.0.0-inc) and build the stuff and do

Re: [release] vote ??

We can do both, but I will focus on the binary.. Mvgr, Martin Matthias Wessendorf wrote: Hi, I was able to prepare the relase, based on the given feedback. Maven created already a TAG for that (see [1]). Should we vote on the tag (meaning source files) or on a binary artifact ? I think

Re: [release] vote ??

No. release:perform ends the release process - after the vote! Just do a mvn clean deploy -Psign-artifacts (after you have checked that distributionManagement points to the correct staging dir) --Manfred On 2/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: so that means doing a

Re: [release] vote ??

I think the process here is a bit different than in a real Apache project. We need to get approval from Incubator PMC on binaries that are exactly the same that we put into a real m2-repo. A podling can't simply put together a release. it needs an approval on some binaries and when that approval

Re: [release] fun with maven

we use this, parent groupIdorg.apache/groupId artifactIdapache/artifactId version3/version /parent was suggested on the general incubator list On 2/13/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 2/13/07, Wendy Smoak [EMAIL PROTECTED] wrote: Please create a new staging folder for

Re: [release] vote ??

You are right. Did not know that release:perform does a new deploy. See [1]. --Manfred [1] http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html On 2/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: I think the process here is a bit different than in a real

Re: [release] vote ??

Btw this is not just an incubator requirement.. It's a requirement for all projects to vote on binaries.. Normally discussion about code is held in the are we ready for release vote, after that on binaries. Mvgr, Martin Matthias Wessendorf wrote: I think the process here is a bit different

Re: [release] vote ??

thanks for making it more clear, so need now only to figure out, how to tell my friend maven that I actually do -Dpassphrase :))) thanks, Matthias On 2/13/07, Martin van den Bemt [EMAIL PROTECTED] wrote: Btw this is not just an incubator requirement.. It's a requirement for all projects to

Re: [release] fun with maven

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

Patches

Can someone please take a look at the patches for the following JIRA issues and give me your feedback so that we can get these merged into the JSF 1.2 branch and trunk? ADFFACES-374 ADFFACES-379 Thanks. Scott O'Bryan

Re: [release] fun with maven

I think it is the plugin. check out and changing the code (GpgSignAttachedMojo) /** * The passphrase to use when signing. * * @parameter expression=${passphrase} default-value=xx * @required */ private String passphrase; takes me to another exception, but that can

Re: [release] fun with maven

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

Re: [release] fun with maven

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

Re: [release] fun with maven

No, it's nothing with the gpg-plugin. What you are doing is something like mvn release:perform -Dpassphrase=, 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!

Re: [release] fun with maven

Try a manual scp connect first to add the server fingerprint to your ssh trusted server list. --Manfred On 2/13/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: one more ... now getting this: [INFO] [deploy:deploy] altDeploymentRepository = null The authenticity of host 'people.apache.org'

Re: [release] fun with maven

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 [EMAIL PROTECTED] wrote: Try a manual scp connect first to add the server

Re: Patches

Scott, I'll do my best to review your patches and check them into trunk and the JSF 1.2 branch. It would be great if someone else can give their feedback, since I'm not that familiar with what you are doing here.. Thanks, - Jeanne Scott O'Bryan wrote: Can someone please take a look at the

Re: Patches

Oh, I see Adam already did this. Thanks Adam. Jeanne Waldman wrote: Scott, I'll do my best to review your patches and check them into trunk and the JSF 1.2 branch. It would be great if someone else can give their feedback, since I'm not that familiar with what you are doing here.. Thanks,