Notes on the MyFaces Build Tools Maven 2 Archetypes 1.0.2 Release

Timeline

Release Notes

Testing

Here's how you can help us test the distribution.

Create a project from an archetype:

mvn archetype:generate -DarchetypeCatalog=http://people.apache.org/~jakobk/m2_archetypes_102_release

Choose an archetype from the list and enter values for groupId, artifactId and version.

Then on the path of the generated archetype

mvn clean jetty:run

or for the 2.0 archetypes

mvn clean jetty:run-exploded -PjettyConfig

Then open http://localhost:8080 and see if everything works.

Diary

Follow the guide on http://www.apache.org/dev/publishing-maven-artifacts.html

Prepare your POMs for release

  1. Make sure there are no snapshots in the POMs to be released.
  2. Check that your POMs will not lose content when they are rewritten during the release process:
    1. Verify that all pom.xml files have an SCM definition.
    2. Do a dryRun release: mvn release:prepare -DdryRun=true

    3. Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has been removed.

mvn release:prepare -DdryRun=true

Choose 1.0.2 as release version, m2_archetypes_102_release as the tag and 1.0.3-SNAPSHOT as next development version.

Check pom modifications using diff:

diff pom.xml pom.xml.tag

Clean the local release info.

mvn release:clean

Publish a snapshot

mvn deploy

Verify the deployment under the Maven Snapshot repository at Apache (https://repository.apache.org/content/repositories/snapshots/).

Prepare the release

mvn release:prepare

Choose 1.0.2 as release version, m2_archetypes_102_release as the tag and 1.0.3-SNAPSHOT as next development version (just as in dryRun).

Note: Preparing the release will create the new tag in SVN, automatically checking in on your behalf.

Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and 'svn: No such revision X'. Wait 10 seconds and run mvn release:prepare again.

  1. FAIL (Unable to tag SCM)
  2. SUCCESS

Stage the release for a vote

mvn release:perform

The release will automatically be inserted into a temporary staging repository for you.

Now you must close the staging repository to indicate to Nexus that the build is done and to make the artifacts available.

Create archetype catalog file

Make sure only the new archetypes are in the local repo and use the following command to create the archetype-catalog file:

mvn archetype:crawl

Manually remove duplicate entries and upload it to my public_html folder on people.apache.org for testing (http://people.apache.org/~jakobk/m2_archetypes_102_release/).

Vote

Subject: [VOTE] release for myfaces archetypes 1.0.2

Hi,

I was running the needed tasks to get the 1.0.2 release of Apache
MyFaces Build Tools Archetypes out.

Please note that this vote concerns all of the following parts:
 1. Maven artifact group "org.apache.myfaces.buildtools" v1.0.2 (only archetypes)

The artifacts are deployed to the nexus repository [1].

The following issues have been addressed in this release:
 * MYFACES-2515 Archetype for MyFaces 2.0 hello world app
 * TRINIDAD-1904 Archetype for Trinidad 2.0
 * Update archetypes structure to fit the new archetype plugin
 * Add license headers in various files
 * Update versions of MyFaces, Mojarra, Jetty, Trinidad


To test the archetypes just do the following:

Create a project from an archetype:

mvn archetype:generate -DarchetypeCatalog=http://people.apache.org/~jakobk/m2_archetypes_102_release

Choose an archetype from the list and enter values for groupId, artifactId and version.

Then on the path of the generated archetype

mvn clean jetty:run

or for the 2.0 archetypes

mvn clean jetty:run-exploded -PjettyConfig

Then open http://localhost:8080 and see if everything works.


Please take a look at the "1.0.2" artifacts and vote!

Please note: This vote is "majority approval" with a minimum of three
+1 votes (see [2]).

------------------------------------------------
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
 and why..............
------------------------------------------------

Thanks,
Jakob

[1] https://repository.apache.org/content/repositories/orgapachemyfaces-041/
[2] http://www.apache.org/foundation/voting.html#ReleaseVotes

Result

Subject: Result (was: [VOTE] release for myfaces archetypes 1.0.2)

Hi,

Thanks to all people who voted.

We have 5 +1

Mark Struberg
Gerhard Petracek
Matthias Wessendorf
Leonardo Uribe
Jakob Korherr

so we can continue with the necessary steps to release myfaces archetypes 1.0.2

Regards,
Jakob

Release the staged Repository

Go to Nexus Staging Repositories, select the repo and click release. Note that this pushes the artifacts to Maven central.

Deploy the site

mvn site-deploy

Deploy the archetype catalog to myfaces.apache.org

Update the archetype-catalog.xml on the MyFaces site (folder: resources) and deploy the MyFaces site.

Announce

Subject: [ANNOUNCE] MyFaces Buildtools Archetypes v1.0.2 Release

The Apache MyFaces team is pleased to announce the release of MyFaces Buildtools Archetypes v1.0.2.

The Myfaces Archetypes are various Maven2-archetypes which build a directory tree containing the files needed to quickly get started on a new JSF project. Different archetypes create different initial setups, such as including different libraries in the created pom.xml file, and adding different configuration to the created web.xml file.

For more information please see: http://myfaces.apache.org/build-tools/archetypes/

MyFaces Buildtools Archetypes is available in the central Maven repository under Group ID "org.apache.myfaces.buildtools".

Release Notes - MyFaces Buildtools Archetypes - Version 1.0.2

 * MYFACES-2515 Archetype for MyFaces 2.0 hello world app
 * TRINIDAD-1904 Archetype for Trinidad 2.0
 * Update archetypes structure to fit the new archetype plugin
 * Add license headers in various files
 * Update versions of MyFaces, Mojarra, Jetty, Trinidad


Regards,
Jakob