Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 2588 invoked from network); 12 Mar 2008 06:37:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2008 06:37:44 -0000 Received: (qmail 60391 invoked by uid 500); 12 Mar 2008 06:37:40 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 60328 invoked by uid 500); 12 Mar 2008 06:37:40 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 60317 invoked by uid 99); 12 Mar 2008 06:37:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 23:37:39 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.57] (HELO smtp102.prem.mail.sp1.yahoo.com) (98.136.44.57) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 12 Mar 2008 06:37:02 +0000 Received: (qmail 92682 invoked from network); 12 Mar 2008 06:37:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Mime-Version:To:Message-Id:Content-Type:From:Subject:Date:X-Mailer; b=eBeFsQytMTKZ+0EJPbT+5XCnwcRXm6XrCONaAtkiKKyg9H4wvrELYYq2cEn/qjf9WkrEmdJqo/DzOEPQ7NcCxXJ/jHhpzBm+OFUHsK5UDq7k90h3ZqWvDpo0IVS7tFO8vxcq59yV/Y20stFctJbcvM0OCR9zOmJC8j8p3ZZExls= ; Received: from unknown (HELO ?192.168.1.101?) (david_jencks@67.102.173.8 with plain) by smtp102.prem.mail.sp1.yahoo.com with SMTP; 12 Mar 2008 06:37:11 -0000 X-YMail-OSG: LZ3p8S4VM1nO4Mo87YbG7jKujP_fGoZXUMqgz.h8v_fSkbuoAxRipLFFCkoALcHTiYmp8CuJbi21b8oFHDKUyKdNC6tUQKcgzkk9 X-Yahoo-Newman-Property: ymail-3 Mime-Version: 1.0 (Apple Message framework v753) To: "Geronimo Dev List (JIRA)" Message-Id: Content-Type: multipart/alternative; boundary=Apple-Mail-35--636603508 From: David Jencks Subject: [VOTE] genesis 1.4 take 5 Date: Tue, 11 Mar 2008 23:37:43 -0700 X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-35--636603508 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi, Changes in v5: legal files in all the jars (I hope) fix a typo in the NOTICE template make the generated site work better (parent link, maven feather) remove logging-config and checkstyle-config per jdillons advice. move modules to base pom, not a profile; change how bootstrap works. Changes in v4: make the legal-bundle version fixed rather than equal to the version of whatever subproject is trying to use it. Fix noise in DEPENDENCIES file generation Change legal verifier to expect LICENSE and NOTICE files by default add the rat plugin so you can run mvn rat:check for a project check (note that rat does not look inside jars so we still need the verifier) add some more commonly used plugins to the project-config and alphabetize them. Changes in v3: Change the legal-bundle to have really simple NOTICE file and put all the dependency info in a separate DEPENDENCIES file. This corresponds to what appears to be current thinking on legal-discuss about what should be in these files. We should be able to use this bundle with the maven-remote-resources-plugin everywhere now. Fiddle around with the maven site generation and site deployment so it more or less works. Add some instructions in the project-config site. Changes in v2: Change in the release plugin configuration to use the default tagBase in release profiles in projects that inherit from the project-config pom. It is also possible to override tagBase but this should not be necessary as we adhere to standard svn layout. There are also some plugin version upgrades. The new root pom includes a release profile that sets up the standard javadoc, source and gpg plugins and uses the default tagBase location. This sets us up for using the release process also now under vote described at http://cwiki.apache.org/confluence/display/GMOxPMGT/ Proposed+%28updated%29+release+process The only Jira I know about is https://issues.apache.org/jira/browse/ GERONIMO-3895 Staging repo: (note, this is a different location) http://people.apache.org/~djencks/staging-repo/genesis/org/apache/ geronimo/genesis/ site staging: http://people.apache.org/~djencks/staging-site/maven/genesis/1.4/ This time I was able to use mvn site site-deploy -Prelease to deploy the site all at once to the staging-site. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks --Apple-Mail-35--636603508 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
Hi,

Changes in = v5:
legal files in all the jars (I = hope)
fix a typo in the NOTICE = template
make the generated site work = better (parent link, maven feather)
remove = logging-config and checkstyle-config per jdillons advice.
move modules to base pom, not a profile; change how = bootstrap works.

Changes in v4:
make the = legal-bundle version fixed rather than equal to the version of whatever = subproject is trying to use it.
Fix noise = in DEPENDENCIES file generation
Change = legal verifier to expect LICENSE and NOTICE files by = default
add the rat plugin so you = can run mvn rat:check for a project check (note that rat does not look = inside jars so we still need the verifier)
add some more commonly used plugins to the = project-config and alphabetize them.
Changes in = v3:
Change the legal-bundle to = have really simple NOTICE file and put all the dependency info in a = separate DEPENDENCIES file. =A0This corresponds to what appears to be = current thinking on legal-discuss about what should be in these files. = =A0We should be able to use this bundle with the = maven-remote-resources-plugin everywhere now.

Fiddle = around with the maven site generation and site deployment so it more or = less works. =A0Add some instructions in the project-config = site.

=A0=A0 =A0 = =A0

Changes in = v2:
Change in the release plugin = configuration to use the default tagBase in release profiles in projects = that inherit from the project-config pom. =A0It is also possible to = override tagBase but this should not be necessary as we adhere to = standard svn layout. There are also some plugin version = upgrades.

The new root pom includes a release profile that sets = up the standard javadoc, source and gpg plugins and uses the default = tagBase location.

This sets us up for using the release process also now = under vote described at=A0http://cwiki.apache.org/confluence/display/GMOxPMGT/Proposed+%= 28updated%29+release+process


Staging repo: (note, this is a different = location)
site staging:

This time I was able to use mvn site site-deploy = -Prelease to deploy the site all at once to the = staging-site.


Vote open = for 72 hours.

[ ] +1
[ ] = +0
[ ] -1

thanks
david = jencks
= --Apple-Mail-35--636603508--