You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@portals.apache.org by Vivek Kumar <fi...@gmail.com> on 2009/05/08 14:12:13 UTC
[VOTE] Release portals-pom-1.1
Hi all
This new pom now uses the Apache 6 pom as parent which allowed to
cleanup and remove many elements.
Furthermore, the Portals developers info has been taken out to be moved
to a new main portals-site-pom shortly.
That will make it easier to incorporate updates to the developers info
without having to change this Portals super pom and thereby effecting
all sub projects and their versions.
Please review the release candidate POM from the Nexus staging
repository below:
https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
Please vote on releasing portals-pom-1.1 .
Vote is open for the next 72 hours.
Please cast your vote:
[ ] +1 for Release
[ ] 0 for Don't care
[ ] -1 Don't release, reason
Regards
Vivek Kumar
Re: [VOTE] Release portals-pom-1.1
Posted by Vivek Kumar <fi...@gmail.com>.
Here is mine +1
Vivek Kumar wrote:
> Hi all
>
> This new pom now uses the Apache 6 pom as parent which allowed to
> cleanup and remove many elements.
>
> Furthermore, the Portals developers info has been taken out to be
> moved to a new main portals-site-pom shortly.
> That will make it easier to incorporate updates to the developers info
> without having to change this Portals super pom and thereby effecting
> all sub projects and their versions.
>
> Please review the release candidate POM from the Nexus staging
> repository below:
>
> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>
>
> Please vote on releasing portals-pom-1.1 .
>
> Vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release, reason
>
> Regards
> Vivek Kumar
>
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by Carsten Ziegeler <cz...@apache.org>.
Ate Douma wrote:
> Carsten Ziegeler wrote:
>> Sorry for the late response, but I just noticed that we have a typo in
>> the pom. The organization needs to be "The Apache Software Foundation" -
>> this is our official name.
> Sigh
>
>>
>> The problem with this is that this value is picked up by some maven
>> plugins like the maven bundle plugin which we use for the portlet api's.
>>
>> We can solve this by overwriting the value in the spec poms.
> +1
> Can we just do so for the spec poms and *not* hold up the release yet
> another 3 days?
>
>> Nevertheless I think we should just do another release.
> I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming
> releases for APA, Pluto and Jetspeed-2 can leverage that.
> But as the *formal* release of an ASF project constitutes the *src*
> distribution, we can (by overriding the organization name in the spec
> poms) still produce valid ASF releases for these spec projects,
> *without* needing to wait upon the portals-pom-1.2, agreed?
>
Yes, that was my idea as well.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by David Jencks <da...@yahoo.com>.
On May 11, 2009, at 4:11 PM, David Sean Taylor wrote:
>
> On May 11, 2009, at 3:59 PM, David Jencks wrote:
>
>> Stuff is piling up that we (or at least I) would like in the
>> portals-pom
>>
>> - ianal plugin on all builds
>
> what is that?
It checks that the apache-required legal files are present in every
artifact. It doesn't seem to happen with the apache-release profile
but often the legal files don't get into source and javadoc jars to
this is really pretty handy.
>
>
>>
>> - better name for prepare-release profile if it really cant be
>> apache-release
>> - corrected organization name
>> - assembly plugin configuration for source distros.
>>
>> what if we released a portals-pom 1.2 and spec jars in the same
>> vote? We've done multiple-source/artifact releases pretty often in
>> geronimo.
>>
> thats a great idea. what if we voted on the pluto release at this
> time as well ?
I looked at pluto trunk and think it will be a couple days before it's
ready to vote on. I don't see any problem in having overlapping
dependent votes however, e.g. pluto release depends on spec release
passing.
thanks
david jencks
>
>
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by Ate Douma <at...@douma.nu>.
David Sean Taylor wrote:
>
> On May 11, 2009, at 3:59 PM, David Jencks wrote:
>
>> Stuff is piling up that we (or at least I) would like in the portals-pom
>>
>> - ianal plugin on all builds
>
> what is that?
>
>>
>> - better name for prepare-release profile if it really cant be
>> apache-release
>> - corrected organization name
>> - assembly plugin configuration for source distros.
>>
>> what if we released a portals-pom 1.2 and spec jars in the same vote?
>> We've done multiple-source/artifact releases pretty often in geronimo.
>>
> thats a great idea. what if we voted on the pluto release at this time
> as well ?
Pluto release isn't ready enough yet though, there are still pending steps to complete.
I think it'll take Carsten at least another day or so to be prepared for that.
Alternatively we could opt for holding off the release for both portals-pom-1.2 and portlet specs and do a combined release with Pluto as
well, but that is Carsten to decide upon as RM for Pluto.
Theoretically though we could win 1-2 days by doing so, depending how fast Pluto can be made ready :)
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by David Sean Taylor <da...@bluesunrise.com>.
On May 11, 2009, at 3:59 PM, David Jencks wrote:
> Stuff is piling up that we (or at least I) would like in the portals-
> pom
>
> - ianal plugin on all builds
what is that?
>
> - better name for prepare-release profile if it really cant be
> apache-release
> - corrected organization name
> - assembly plugin configuration for source distros.
>
> what if we released a portals-pom 1.2 and spec jars in the same
> vote? We've done multiple-source/artifact releases pretty often in
> geronimo.
>
thats a great idea. what if we voted on the pluto release at this time
as well ?
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by Ate Douma <at...@douma.nu>.
David Jencks wrote:
> Stuff is piling up that we (or at least I) would like in the portals-pom
>
> - ianal plugin on all builds
> - better name for prepare-release profile if it really cant be
> apache-release
> - corrected organization name
> - assembly plugin configuration for source distros.
>
> what if we released a portals-pom 1.2 and spec jars in the same vote?
> We've done multiple-source/artifact releases pretty often in geronimo.
OK, I'm fine with that too as it won't cause further delays.
>
> thanks
> david jencks
>
> On May 11, 2009, at 3:30 PM, Ate Douma wrote:
>
>> Carsten Ziegeler wrote:
>>> Sorry for the late response, but I just noticed that we have a typo in
>>> the pom. The organization needs to be "The Apache Software Foundation" -
>>> this is our official name.
>> Sigh
>>
>>> The problem with this is that this value is picked up by some maven
>>> plugins like the maven bundle plugin which we use for the portlet api's.
>>> We can solve this by overwriting the value in the spec poms.
>> +1
>> Can we just do so for the spec poms and *not* hold up the release yet
>> another 3 days?
>>
>>> Nevertheless I think we should just do another release.
>> I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming
>> releases for APA, Pluto and Jetspeed-2 can leverage that.
>> But as the *formal* release of an ASF project constitutes the *src*
>> distribution, we can (by overriding the organization name in the spec
>> poms) still produce valid ASF releases for these spec projects,
>> *without* needing to wait upon the portals-pom-1.2, agreed?
>>
>> Regards,
>>
>> Ate
>>> Regards
>>> Carsten
>>
>
>
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by David Jencks <da...@yahoo.com>.
Stuff is piling up that we (or at least I) would like in the portals-pom
- ianal plugin on all builds
- better name for prepare-release profile if it really cant be apache-
release
- corrected organization name
- assembly plugin configuration for source distros.
what if we released a portals-pom 1.2 and spec jars in the same vote?
We've done multiple-source/artifact releases pretty often in geronimo.
thanks
david jencks
On May 11, 2009, at 3:30 PM, Ate Douma wrote:
> Carsten Ziegeler wrote:
>> Sorry for the late response, but I just noticed that we have a typo
>> in
>> the pom. The organization needs to be "The Apache Software
>> Foundation" -
>> this is our official name.
> Sigh
>
>> The problem with this is that this value is picked up by some maven
>> plugins like the maven bundle plugin which we use for the portlet
>> api's.
>> We can solve this by overwriting the value in the spec poms.
> +1
> Can we just do so for the spec poms and *not* hold up the release
> yet another 3 days?
>
>> Nevertheless I think we should just do another release.
> I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming
> releases for APA, Pluto and Jetspeed-2 can leverage that.
> But as the *formal* release of an ASF project constitutes the *src*
> distribution, we can (by overriding the organization name in the
> spec poms) still produce valid ASF releases for these spec projects,
> *without* needing to wait upon the portals-pom-1.2, agreed?
>
> Regards,
>
> Ate
>> Regards
>> Carsten
>
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by David Sean Taylor <da...@bluesunrise.com>.
On May 11, 2009, at 3:30 PM, Ate Douma wrote:
> Carsten Ziegeler wrote:
>> Sorry for the late response, but I just noticed that we have a typo
>> in
>> the pom. The organization needs to be "The Apache Software
>> Foundation" -
>> this is our official name.
> Sigh
>
>> The problem with this is that this value is picked up by some maven
>> plugins like the maven bundle plugin which we use for the portlet
>> api's.
>> We can solve this by overwriting the value in the spec poms.
> +1
> Can we just do so for the spec poms and *not* hold up the release
> yet another 3 days?
>
+1 on not holding up releases for this
>> Nevertheless I think we should just do another release.
> I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming
> releases for APA, Pluto and Jetspeed-2 can leverage that.
> But as the *formal* release of an ASF project constitutes the *src*
> distribution, we can (by overriding the organization name in the
> spec poms) still produce valid ASF releases for these spec projects,
> *without* needing to wait upon the portals-pom-1.2, agreed?
>
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by Ate Douma <at...@douma.nu>.
Carsten Ziegeler wrote:
> Sorry for the late response, but I just noticed that we have a typo in
> the pom. The organization needs to be "The Apache Software Foundation" -
> this is our official name.
Sigh
>
> The problem with this is that this value is picked up by some maven
> plugins like the maven bundle plugin which we use for the portlet api's.
>
> We can solve this by overwriting the value in the spec poms.
+1
Can we just do so for the spec poms and *not* hold up the release yet another 3 days?
> Nevertheless I think we should just do another release.
I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming releases for APA, Pluto and Jetspeed-2 can leverage that.
But as the *formal* release of an ASF project constitutes the *src* distribution, we can (by overriding the organization name in the spec
poms) still produce valid ASF releases for these spec projects, *without* needing to wait upon the portals-pom-1.2, agreed?
Regards,
Ate
>
> Regards
> Carsten
Re: [VOTE][RESULT]Release portals-pom-1.1
Posted by Carsten Ziegeler <cz...@apache.org>.
Sorry for the late response, but I just noticed that we have a typo in
the pom. The organization needs to be "The Apache Software Foundation" -
this is our official name.
The problem with this is that this value is picked up by some maven
plugins like the maven bundle plugin which we use for the portlet api's.
We can solve this by overwriting the value in the spec poms.
Nevertheless I think we should just do another release.
Regards
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
[VOTE][RESULT]Release portals-pom-1.1
Posted by Vivek Kumar <fi...@gmail.com>.
+1 - 5 (Binding votes)
0 - none
-1 - none
Vote passes.
Thanks for the support!
Regards
Vivek
Vivek Kumar wrote:
> Hi all
>
> This new pom now uses the Apache 6 pom as parent which allowed to
> cleanup and remove many elements.
>
> Furthermore, the Portals developers info has been taken out to be
> moved to a new main portals-site-pom shortly.
> That will make it easier to incorporate updates to the developers info
> without having to change this Portals super pom and thereby effecting
> all sub projects and their versions.
>
> Please review the release candidate POM from the Nexus staging
> repository below:
>
> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>
>
> Please vote on releasing portals-pom-1.1 .
>
> Vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release, reason
>
> Regards
> Vivek Kumar
>
Re: [VOTE] Release portals-pom-1.1
Posted by David Jencks <da...@yahoo.com>.
On May 10, 2009, at 3:16 PM, Ate Douma wrote:
> David Jencks wrote:
>> I played with this a bit while working on the portlet-api poms. It
>> works pretty well however I have some reservations:
>> 1. There is no compiler plugin source level specified. So, if you
>> have code beyond java 1.3, you need to configure the compiler
>> plugin in your pom. I think that portals is all on java 5 and
>> maybe this could be set in the portals-pom directly.
> Not all.
> For instance the portlet-spec/portlet-api-1.0 needs to be JDK 1.4
> compatible.
>
> I don't think it such a big deal to configure the compiler source
> level per project either.
> For Portals APA, Pluto and Jetspeed, we only have to set this in
> each their master pom (to Java5 indeed).
right. Alternatively the spec that needs 2.4 could override it. Not
a big deal either way.
>
>
>> 2. I don't like the name prepare-release for the profile that uses
>> ianal and rat. First, it doesn't actually prepare anything and is
>> confusingly similar to the release plugin release:prepare goal.
>> Second and more important I think the ianal pllugin should run by
>> default always.
> AFAIK, Vivek initially *had* it configured within the apache-release
> profile so that it would run by default but it caused problems with
> the release plugin itself (something about tmp files causing trouble).
> The name might not be optimal, I agree, but that's something we can
> adjust in a future release.
> IMO, this is not something to hold up/stop the release for.
right.
>
>
>> Alternatively the apache-release profile could perhaps be extended
>> to include these plugins.
>> Also, I suspect there will be an apache 7 pom soon as some work to
>> make the release plugin produce a source distribution more
>> automatically are underway. So it might be worth waiting another
>> couple days to see if this happens.
> The vote is already out, so waiting for apache 7 pom would actually
> mean starting a new release for portals-pom-1.2.
> While I agree the ideas for the apache 7 pom might help for the
> source distribution, that probably needs "validating" by itself
> before we can rely on it to be "proper" for the ASF.
> Within the light of our current planned release schedules however I
> don't want to wait on that.
>
>> However these are fairly minor quibbles and we could postpone them.
> So I gather this means a +1 from you on the current VOTE for portals-
> pom-1.1, even with the above remarks, right?
yes, +1 from me
thanks
david jencks
>
>
> Regards,
>
> Ate
>
>> thanks
>> david jencks
>> On May 8, 2009, at 5:12 AM, Vivek Kumar wrote:
>>> Hi all
>>>
>>> This new pom now uses the Apache 6 pom as parent which allowed to
>>> cleanup and remove many elements.
>>>
>>> Furthermore, the Portals developers info has been taken out to be
>>> moved to a new main portals-site-pom shortly.
>>> That will make it easier to incorporate updates to the developers
>>> info without having to change this Portals super pom and thereby
>>> effecting all sub projects and their versions.
>>>
>>> Please review the release candidate POM from the Nexus staging
>>> repository below:
>>>
>>> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>>> Please vote on releasing portals-pom-1.1 .
>>>
>>> Vote is open for the next 72 hours.
>>>
>>> Please cast your vote:
>>>
>>> [ ] +1 for Release
>>> [ ] 0 for Don't care
>>> [ ] -1 Don't release, reason
>>>
>>> Regards
>>> Vivek Kumar
>>>
>
Re: [VOTE] Release portals-pom-1.1
Posted by Ate Douma <at...@douma.nu>.
David Jencks wrote:
> I played with this a bit while working on the portlet-api poms. It
> works pretty well however I have some reservations:
>
> 1. There is no compiler plugin source level specified. So, if you have
> code beyond java 1.3, you need to configure the compiler plugin in your
> pom. I think that portals is all on java 5 and maybe this could be set
> in the portals-pom directly.
Not all.
For instance the portlet-spec/portlet-api-1.0 needs to be JDK 1.4 compatible.
I don't think it such a big deal to configure the compiler source level per project either.
For Portals APA, Pluto and Jetspeed, we only have to set this in each their master pom (to Java5 indeed).
>
> 2. I don't like the name prepare-release for the profile that uses ianal
> and rat. First, it doesn't actually prepare anything and is confusingly
> similar to the release plugin release:prepare goal. Second and more
> important I think the ianal pllugin should run by default always.
AFAIK, Vivek initially *had* it configured within the apache-release profile so that it would run by default but it caused problems with the
release plugin itself (something about tmp files causing trouble).
The name might not be optimal, I agree, but that's something we can adjust in a future release.
IMO, this is not something to hold up/stop the release for.
> Alternatively the apache-release profile could perhaps be extended to
> include these plugins.
>
> Also, I suspect there will be an apache 7 pom soon as some work to make
> the release plugin produce a source distribution more automatically are
> underway. So it might be worth waiting another couple days to see if
> this happens.
The vote is already out, so waiting for apache 7 pom would actually mean starting a new release for portals-pom-1.2.
While I agree the ideas for the apache 7 pom might help for the source distribution, that probably needs "validating" by itself before we
can rely on it to be "proper" for the ASF.
Within the light of our current planned release schedules however I don't want to wait on that.
>
> However these are fairly minor quibbles and we could postpone them.
So I gather this means a +1 from you on the current VOTE for portals-pom-1.1, even with the above remarks, right?
Regards,
Ate
>
> thanks
> david jencks
>
> On May 8, 2009, at 5:12 AM, Vivek Kumar wrote:
>
>> Hi all
>>
>> This new pom now uses the Apache 6 pom as parent which allowed to
>> cleanup and remove many elements.
>>
>> Furthermore, the Portals developers info has been taken out to be
>> moved to a new main portals-site-pom shortly.
>> That will make it easier to incorporate updates to the developers info
>> without having to change this Portals super pom and thereby effecting
>> all sub projects and their versions.
>>
>> Please review the release candidate POM from the Nexus staging
>> repository below:
>>
>> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>>
>> Please vote on releasing portals-pom-1.1 .
>>
>> Vote is open for the next 72 hours.
>>
>> Please cast your vote:
>>
>> [ ] +1 for Release
>> [ ] 0 for Don't care
>> [ ] -1 Don't release, reason
>>
>> Regards
>> Vivek Kumar
>>
>
Re: [VOTE] Release portals-pom-1.1
Posted by David Jencks <da...@yahoo.com>.
I played with this a bit while working on the portlet-api poms. It
works pretty well however I have some reservations:
1. There is no compiler plugin source level specified. So, if you
have code beyond java 1.3, you need to configure the compiler plugin
in your pom. I think that portals is all on java 5 and maybe this
could be set in the portals-pom directly.
2. I don't like the name prepare-release for the profile that uses
ianal and rat. First, it doesn't actually prepare anything and is
confusingly similar to the release plugin release:prepare goal.
Second and more important I think the ianal pllugin should run by
default always. Alternatively the apache-release profile could
perhaps be extended to include these plugins.
Also, I suspect there will be an apache 7 pom soon as some work to
make the release plugin produce a source distribution more
automatically are underway. So it might be worth waiting another
couple days to see if this happens.
However these are fairly minor quibbles and we could postpone them.
thanks
david jencks
On May 8, 2009, at 5:12 AM, Vivek Kumar wrote:
> Hi all
>
> This new pom now uses the Apache 6 pom as parent which allowed to
> cleanup and remove many elements.
>
> Furthermore, the Portals developers info has been taken out to be
> moved to a new main portals-site-pom shortly.
> That will make it easier to incorporate updates to the developers
> info without having to change this Portals super pom and thereby
> effecting all sub projects and their versions.
>
> Please review the release candidate POM from the Nexus staging
> repository below:
>
> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
> Please vote on releasing portals-pom-1.1 .
>
> Vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release, reason
>
> Regards
> Vivek Kumar
>
Re: [VOTE] Release portals-pom-1.1
Posted by Ate Douma <at...@douma.nu>.
+1
Vivek Kumar wrote:
> Hi all
>
> This new pom now uses the Apache 6 pom as parent which allowed to
> cleanup and remove many elements.
>
> Furthermore, the Portals developers info has been taken out to be moved
> to a new main portals-site-pom shortly.
> That will make it easier to incorporate updates to the developers info
> without having to change this Portals super pom and thereby effecting
> all sub projects and their versions.
>
> Please review the release candidate POM from the Nexus staging
> repository below:
>
> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>
>
> Please vote on releasing portals-pom-1.1 .
>
> Vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release, reason
>
> Regards
> Vivek Kumar
>
>
Re: [VOTE] Release portals-pom-1.1
Posted by David Sean Taylor <da...@bluesunrise.com>.
+1
On May 8, 2009, at 9:27 AM, Woonsan Ko wrote:
>
> +1
>
>
> --- On Fri, 5/8/09, Vivek Kumar <fi...@gmail.com> wrote:
>
>> From: Vivek Kumar <fi...@gmail.com>
>> Subject: [VOTE] Release portals-pom-1.1
>> To: "Portals Discussion" <ge...@portals.apache.org>
>> Date: Friday, May 8, 2009, 2:12 PM
>> Hi all
>>
>> This new pom now uses the Apache 6 pom as parent which
>> allowed to cleanup and remove many elements.
>>
>> Furthermore, the Portals developers info has been taken out
>> to be moved to a new main portals-site-pom shortly.
>> That will make it easier to incorporate updates to the
>> developers info without having to change this Portals super
>> pom and thereby effecting all sub projects and their
>> versions.
>>
>> Please review the release candidate POM from the Nexus
>> staging repository below:
>>
>> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>>
>>
>> Please vote on releasing portals-pom-1.1 .
>>
>> Vote is open for the next 72 hours.
>>
>> Please cast your vote:
>>
>> [ ] +1 for Release
>> [ ] 0 for Don't care
>> [ ] -1 Don't release, reason
>>
>> Regards
>> Vivek Kumar
>
>
>
Re: [VOTE] Release portals-pom-1.1
Posted by Woonsan Ko <wo...@yahoo.com>.
+1
--- On Fri, 5/8/09, Vivek Kumar <fi...@gmail.com> wrote:
> From: Vivek Kumar <fi...@gmail.com>
> Subject: [VOTE] Release portals-pom-1.1
> To: "Portals Discussion" <ge...@portals.apache.org>
> Date: Friday, May 8, 2009, 2:12 PM
> Hi all
>
> This new pom now uses the Apache 6 pom as parent which
> allowed to cleanup and remove many elements.
>
> Furthermore, the Portals developers info has been taken out
> to be moved to a new main portals-site-pom shortly.
> That will make it easier to incorporate updates to the
> developers info without having to change this Portals super
> pom and thereby effecting all sub projects and their
> versions.
>
> Please review the release candidate POM from the Nexus
> staging repository below:
>
> https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
>
>
> Please vote on releasing portals-pom-1.1 .
>
> Vote is open for the next 72 hours.
>
> Please cast your vote:
>
> [ ] +1 for Release
> [ ] 0 for Don't care
> [ ] -1 Don't release, reason
>
> Regards
> Vivek Kumar