Re: [vote] release apache parent 6 and maven parent 12
I've promoted these artifacts to the release repository. Brian Fox wrote: This vote now has sufficient votes to pass. However some concerns were raised on legal-discuss (apparently a month ago and not mentioned here) that may require some tweaks to the release profile. I'll hold on promoting these poms until I better understand what we might be able to improve. HUYNH GIANG SON wrote: 2 * +2 -Original Message- From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier Lamy Sent: Monday, April 27, 2009 2:55 PM To: Maven Developers List Subject: Re: [vote] release apache parent 6 and maven parent 12 2 * +1 -- Olivier 2009/4/21 Brian Fox bri...@infinity.nu: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/ap ache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apa che/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
This vote now has sufficient votes to pass. However some concerns were raised on legal-discuss (apparently a month ago and not mentioned here) that may require some tweaks to the release profile. I'll hold on promoting these poms until I better understand what we might be able to improve. HUYNH GIANG SON wrote: 2 * +2 -Original Message- From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier Lamy Sent: Monday, April 27, 2009 2:55 PM To: Maven Developers List Subject: Re: [vote] release apache parent 6 and maven parent 12 2 * +1 -- Olivier 2009/4/21 Brian Fox bri...@infinity.nu: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/ap ache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apa che/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 -Lukas Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 Arnaud On Mon, Apr 27, 2009 at 8:43 AM, Lukas Theussl ltheu...@apache.org wrote: +1 -Lukas Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Arnaud
Re: [vote] release apache parent 6 and maven parent 12
2 * +1 -- Olivier 2009/4/21 Brian Fox bri...@infinity.nu: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [vote] release apache parent 6 and maven parent 12
2 * +2 -Original Message- From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier Lamy Sent: Monday, April 27, 2009 2:55 PM To: Maven Developers List Subject: Re: [vote] release apache parent 6 and maven parent 12 2 * +1 -- Olivier 2009/4/21 Brian Fox bri...@infinity.nu: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/ap ache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apa che/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 (but as I'm not currently an apache committer it probably does not count) -Stephen 2009/4/27 HUYNH GIANG SON huynh.giang.son...@gmail.com 2 * +2 -Original Message- From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier Lamy Sent: Monday, April 27, 2009 2:55 PM To: Maven Developers List Subject: Re: [vote] release apache parent 6 and maven parent 12 2 * +1 -- Olivier 2009/4/21 Brian Fox bri...@infinity.nu: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/ap ache/apache/6/apache-6.pomhttps://repository.apache.org/content/repositories/apache-staging-011/org/ap%0Aache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apa che/maven/maven-parent/12/maven-parent-12.pomhttps://repository.apache.org/content/repositories/maven-staging-012/org/apa%0Ache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
Anyone else? We have just two votes so far. On 4/20/2009 11:05 PM, Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 On 20-Apr-09, at 8:05 PM, Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
+1 Ralph On Apr 26, 2009, at 6:37 PM, Brian Fox wrote: Anyone else? We have just two votes so far. On 4/20/2009 11:05 PM, Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
Svn is up again it seems so you can login to Nexus if you want to look. On 4/24/2009 1:40 AM, Brett Porter wrote: Can't access these since Nexus is not responding because SVN is down. My vote is on the ones in SVN, I'm going to trust they are the same. +1 On 21/04/2009, at 1:05 PM, Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
Actually this will have no effect. The default for passphrase in the
plugin is...
|${gpg.passphrase}
|So no votes on this release?
On 4/20/2009 11:12 PM, Daniel Kulp wrote:
Honestly, I think the lines:
configuration
passphrase${gpg.passphrase}/passphrase
/configuration
need to be taken out of the config for the gpg plugin. I think that will end
up conflicting with other settings. (like using an agent which is what I do)
With the latest releases of the release plugin and gpg plugins, if you DON'T
pass it on the command line or in settings.xml, it will just prompt you for
the passphrase. Thus, it's not needed in the config.
Dan
On Mon April 20 2009 11:05:50 pm Brian Fox wrote:
Time to release the updated parent poms:
https://repository.apache.org/content/repositories/apache-staging-011/org/a
pache/apache/6/apache-6.pom
https://repository.apache.org/content/repositories/maven-staging-012/org/ap
ache/maven/maven-parent/12/maven-parent-12.pom
The changes were described in a previous thread:
We currently have some expectations about what artifacts are created
for apache builds, such as javadocs and source jars, and specifically
artifact signatures. Currently each project must configure the current
release profile in their own top level pom. This raises the bar of entry
for new projects and creates more work for us to help them get it sorted
out.
I'd like to take the maven release profile and release plugin config and
push it up to the apache pom to make it consistent and easy for all
apache projects to produce proper releases. I think to do it and avoid
conflicts with any existing profiles, I would change the profile name
from release to apache-release and activate that by default. Does
anyone see any downsides to this?
In addition to moving the profile, I pulled up the pluginManagement and
the default source encoding. I think if these things are best practices
for the Maven project, they can be default best practices for any Apache
project as well.
Vote is open for 72hrs:
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
Can't access these since Nexus is not responding because SVN is down. My vote is on the ones in SVN, I'm going to trust they are the same. +1 On 21/04/2009, at 1:05 PM, Brian Fox wrote: Time to release the updated parent poms: https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom https://repository.apache.org/content/repositories/maven-staging-012/org/apache/maven/maven-parent/12/maven-parent-12.pom The changes were described in a previous thread: We currently have some expectations about what artifacts are created for apache builds, such as javadocs and source jars, and specifically artifact signatures. Currently each project must configure the current release profile in their own top level pom. This raises the bar of entry for new projects and creates more work for us to help them get it sorted out. I'd like to take the maven release profile and release plugin config and push it up to the apache pom to make it consistent and easy for all apache projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? In addition to moving the profile, I pulled up the pluginManagement and the default source encoding. I think if these things are best practices for the Maven project, they can be default best practices for any Apache project as well. Vote is open for 72hrs: +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
Jochen, the release plugin is configured to activate this new profile automatically during perform, so that should answer both of your questions:: 1) it doesn't need an activation of it's own and 2) the name is irrelevant so it doesn't matter what we name it because noone has to activate it explicitelytherefore if people have their own existing release profiles, it's probably better that we don't stomp on them. Jochen Wiedmann wrote: On Tue, Apr 21, 2009 at 5:05 AM, Brian Fox bri...@infinity.nu wrote: projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? I would, if it where: The apache-release profile doesn't contain an activation section. My understanding is that means it is *not* turned on by default, is it? (And rightly so, because I wouldn't want to run javadoc with any build.) I am also not so sure about the change of profile name. The argument to avoid conflicts doesn't apply, IMO: Nobody needs to choose the new parents. I also do think that we should demonstrate best practices, which includes uniformity: Choose common profile names and depart from them only if necessary, not vice versa. I am -0 (non-binding) on these changes. Jochen
Re: [vote] release apache parent 6 and maven parent 12
Honestly, I think the lines:
configuration
passphrase${gpg.passphrase}/passphrase
/configuration
need to be taken out of the config for the gpg plugin. I think that will end
up conflicting with other settings. (like using an agent which is what I do)
With the latest releases of the release plugin and gpg plugins, if you DON'T
pass it on the command line or in settings.xml, it will just prompt you for
the passphrase. Thus, it's not needed in the config.
Dan
On Mon April 20 2009 11:05:50 pm Brian Fox wrote:
Time to release the updated parent poms:
https://repository.apache.org/content/repositories/apache-staging-011/org/a
pache/apache/6/apache-6.pom
https://repository.apache.org/content/repositories/maven-staging-012/org/ap
ache/maven/maven-parent/12/maven-parent-12.pom
The changes were described in a previous thread:
We currently have some expectations about what artifacts are created
for apache builds, such as javadocs and source jars, and specifically
artifact signatures. Currently each project must configure the current
release profile in their own top level pom. This raises the bar of entry
for new projects and creates more work for us to help them get it sorted
out.
I'd like to take the maven release profile and release plugin config and
push it up to the apache pom to make it consistent and easy for all
apache projects to produce proper releases. I think to do it and avoid
conflicts with any existing profiles, I would change the profile name
from release to apache-release and activate that by default. Does
anyone see any downsides to this?
In addition to moving the profile, I pulled up the pluginManagement and
the default source encoding. I think if these things are best practices
for the Maven project, they can be default best practices for any Apache
project as well.
Vote is open for 72hrs:
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release apache parent 6 and maven parent 12
On Tue, Apr 21, 2009 at 5:05 AM, Brian Fox bri...@infinity.nu wrote: projects to produce proper releases. I think to do it and avoid conflicts with any existing profiles, I would change the profile name from release to apache-release and activate that by default. Does anyone see any downsides to this? I would, if it where: The apache-release profile doesn't contain an activation section. My understanding is that means it is *not* turned on by default, is it? (And rightly so, because I wouldn't want to run javadoc with any build.) I am also not so sure about the change of profile name. The argument to avoid conflicts doesn't apply, IMO: Nobody needs to choose the new parents. I also do think that we should demonstrate best practices, which includes uniformity: Choose common profile names and depart from them only if necessary, not vice versa. I am -0 (non-binding) on these changes. Jochen -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
