You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David H. DeWolf" <dd...@apache.org> on 2007/02/07 00:02:29 UTC
Pluto 1.1.0 Test Build Available
The test build of Pluto 1.1.0 is available.
No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
1.1.0 has been made, and at this time it is simply a "test build". We
welcome any comments you may have, and will take all feedback into
account if a quality vote is called for this build.
Release notes:
* http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
Distribution:
* http://people.apache.org/builds/portals-pluto/
Maven 2 staging repository:
* http://people.apache.org/builds/portals-pluto/m2-staging-repository/
We appreciate the time and effort everyone has put toward testing,
contributing code and documentation, posting to the mailing lists, and
logging issues.
I will call a vote on this test build to determine it's status after
allowing comments for a couple of days.
Re: Pluto 1.1.0 Test Build Available
Posted by Elliot Metsger <em...@jhu.edu>.
David H. DeWolf wrote:
>
> Good catch. I think we actually want to exclude both jsp-api and
> servlet-api. We don't want to change the jsp-api exclude, we want to
> add the servlet one - right?
Right - duh.
>
> Patch the trunk. I can recut the tag -- that's the whole purpose for
> the "test build" before the release.
:-)
Re: Pluto 1.1.0 Test Build Available
Posted by Elliot Metsger <em...@jhu.edu>.
David H. DeWolf wrote:
>
>
> Elliot Metsger wrote:
>> David,
>>
>> I've come across a minor thing. Question: do you want to commit fixes
>> on the existing 1.1.0 tag or on the trunk?
>
> I don't think we should ever update a tag. Let's patch the trunk and if
> we determine we need a new build, we can retag.\
Cool - I agree.
>>
>> I wonder if in the future it would be better to build release
>> candidate builds straight from trunk. As problems are found with the
>> release candidates, we can apply them to trunk, and not to a tag.
>> Then after we are happy with the fixes and we've determined we don't
>> need another release candidate, we can use the maven plugin to
>> actually create the tag.
>
> SVN tags are actually VERY cheap. I think it'd be a lot easier to
> simple remove the tag and start over.
Yes.
My concern about starting over was that the maven plugin couldn't roll
back from 1.1.1-SNAPSHOT to 1.1.0-SNAPSHOT. But looking closer I
realize that only the base pom.xml is affected so no big deal -
I'll patch the trunk -E
>>
>> What do you think?
>>
>> Here's the fix (problem is pluto-portal is including servlet-api.jar
>> in the webapp):
>>
>> Index: pluto-portal/pom.xml
>> ===================================================================
>> --- pluto-portal/pom.xml (revision 505110)
>> +++ pluto-portal/pom.xml (working copy)
>> @@ -21,7 +21,7 @@
>> <exclusions>
>> <exclusion>
>> <groupId>javax.servlet</groupId>
>> - <artifactId>jsp-api</artifactId>
>> + <artifactId>servlet-api</artifactId>
>> </exclusion>
>> <exclusion>
>> <groupId>xml-apis</groupId>
>> @@ -42,7 +42,7 @@
>> <exclusions>
>> <exclusion>
>> <groupId>javax.servlet</groupId>
>> - <artifactId>jsp-api</artifactId>
>> + <artifactId>servlet-api</artifactId>
>> </exclusion>
>> <exclusion>
>> <groupId>xml-apis</groupId>
>> @@ -101,4 +101,4 @@
>>
>> </build>
>>
>> -</project>
>> \ No newline at end of file
>> +</project>
>>
>
> Good catch. I think we actually want to exclude both jsp-api and
> servlet-api. We don't want to change the jsp-api exclude, we want to
> add the servlet one - right?
>
> Patch the trunk. I can recut the tag -- that's the whole purpose for
> the "test build" before the release.
>
> David
>>
>> David H. DeWolf wrote:
>>> The test build of Pluto 1.1.0 is available.
>>>
>>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of
>>> Pluto 1.1.0 has been made, and at this time it is simply a "test
>>> build". We welcome any comments you may have, and will take all
>>> feedback into account if a quality vote is called for this build.
>>>
>>> Release notes:
>>> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>>>
>>> Distribution:
>>> * http://people.apache.org/builds/portals-pluto/
>>>
>>> Maven 2 staging repository:
>>> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>>>
>>> We appreciate the time and effort everyone has put toward testing,
>>> contributing code and documentation, posting to the mailing lists,
>>> and logging issues.
>>>
>>> I will call a vote on this test build to determine it's status after
>>> allowing comments for a couple of days.
>>
Re: Pluto 1.1.0 Test Build Available
Posted by "David H. DeWolf" <dd...@apache.org>.
Elliot Metsger wrote:
> David,
>
> I've come across a minor thing. Question: do you want to commit fixes
> on the existing 1.1.0 tag or on the trunk?
I don't think we should ever update a tag. Let's patch the trunk and if
we determine we need a new build, we can retag.
>
> I wonder if in the future it would be better to build release candidate
> builds straight from trunk. As problems are found with the release
> candidates, we can apply them to trunk, and not to a tag. Then after we
> are happy with the fixes and we've determined we don't need another
> release candidate, we can use the maven plugin to actually create the tag.
SVN tags are actually VERY cheap. I think it'd be a lot easier to
simple remove the tag and start over. The maven plugin is VERY nice in
terms of automating this and going back to manual builds would be very
painfull and result in less frequent builds. I'm actually excited that
we're finally to a point where it seems like there's a lower barrier for
releases and I'm hopefull they'll start to come at a faster pace.
>
> What do you think?
>
> Here's the fix (problem is pluto-portal is including servlet-api.jar in
> the webapp):
>
> Index: pluto-portal/pom.xml
> ===================================================================
> --- pluto-portal/pom.xml (revision 505110)
> +++ pluto-portal/pom.xml (working copy)
> @@ -21,7 +21,7 @@
> <exclusions>
> <exclusion>
> <groupId>javax.servlet</groupId>
> - <artifactId>jsp-api</artifactId>
> + <artifactId>servlet-api</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xml-apis</groupId>
> @@ -42,7 +42,7 @@
> <exclusions>
> <exclusion>
> <groupId>javax.servlet</groupId>
> - <artifactId>jsp-api</artifactId>
> + <artifactId>servlet-api</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xml-apis</groupId>
> @@ -101,4 +101,4 @@
>
> </build>
>
> -</project>
> \ No newline at end of file
> +</project>
>
Good catch. I think we actually want to exclude both jsp-api and
servlet-api. We don't want to change the jsp-api exclude, we want to
add the servlet one - right?
Patch the trunk. I can recut the tag -- that's the whole purpose for
the "test build" before the release.
David
>
> David H. DeWolf wrote:
>> The test build of Pluto 1.1.0 is available.
>>
>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
>> 1.1.0 has been made, and at this time it is simply a "test build". We
>> welcome any comments you may have, and will take all feedback into
>> account if a quality vote is called for this build.
>>
>> Release notes:
>> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>>
>> Distribution:
>> * http://people.apache.org/builds/portals-pluto/
>>
>> Maven 2 staging repository:
>> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>>
>> We appreciate the time and effort everyone has put toward testing,
>> contributing code and documentation, posting to the mailing lists, and
>> logging issues.
>>
>> I will call a vote on this test build to determine it's status after
>> allowing comments for a couple of days.
>
Re: Pluto 1.1.0 Test Build Available
Posted by Elliot Metsger <em...@jhu.edu>.
David,
I've come across a minor thing. Question: do you want to commit fixes
on the existing 1.1.0 tag or on the trunk?
I wonder if in the future it would be better to build release candidate
builds straight from trunk. As problems are found with the release
candidates, we can apply them to trunk, and not to a tag. Then after we
are happy with the fixes and we've determined we don't need another
release candidate, we can use the maven plugin to actually create the tag.
What do you think?
Here's the fix (problem is pluto-portal is including servlet-api.jar in
the webapp):
Index: pluto-portal/pom.xml
===================================================================
--- pluto-portal/pom.xml (revision 505110)
+++ pluto-portal/pom.xml (working copy)
@@ -21,7 +21,7 @@
<exclusions>
<exclusion>
<groupId>javax.servlet</groupId>
- <artifactId>jsp-api</artifactId>
+ <artifactId>servlet-api</artifactId>
</exclusion>
<exclusion>
<groupId>xml-apis</groupId>
@@ -42,7 +42,7 @@
<exclusions>
<exclusion>
<groupId>javax.servlet</groupId>
- <artifactId>jsp-api</artifactId>
+ <artifactId>servlet-api</artifactId>
</exclusion>
<exclusion>
<groupId>xml-apis</groupId>
@@ -101,4 +101,4 @@
</build>
-</project>
\ No newline at end of file
+</project>
David H. DeWolf wrote:
> The test build of Pluto 1.1.0 is available.
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
> 1.1.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into
> account if a quality vote is called for this build.
>
> Release notes:
> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>
> Distribution:
> * http://people.apache.org/builds/portals-pluto/
>
> Maven 2 staging repository:
> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>
> We appreciate the time and effort everyone has put toward testing,
> contributing code and documentation, posting to the mailing lists, and
> logging issues.
>
> I will call a vote on this test build to determine it's status after
> allowing comments for a couple of days.
Re: Pluto 1.1.0 Test Build Available
Posted by "David H. DeWolf" <dd...@apache.org>.
These are awesome. Thanks for the thorough testing.
I've run a test run and things look pretty good. I'm going to start
working on rec-utting now.
David
Elliot Metsger wrote:
> David et al,
>
> I've made some fixes, including what turned out to be an easy fix for
> the assembler, which in turn fixed the binary distributions. I filed
> PLUTO-309 and PLUTO-310 which I don't think need to hold up a release -
> what do you think? I think we're ready to re-cut it -
>
> Elliot
>
>
> David H. DeWolf wrote:
>> The test build of Pluto 1.1.0 is available.
>>
>> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
>> 1.1.0 has been made, and at this time it is simply a "test build". We
>> welcome any comments you may have, and will take all feedback into
>> account if a quality vote is called for this build.
>>
>> Release notes:
>> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>>
>> Distribution:
>> * http://people.apache.org/builds/portals-pluto/
>>
>> Maven 2 staging repository:
>> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>>
>> We appreciate the time and effort everyone has put toward testing,
>> contributing code and documentation, posting to the mailing lists, and
>> logging issues.
>>
>> I will call a vote on this test build to determine it's status after
>> allowing comments for a couple of days.
>
Re: Pluto 1.1.0 Test Build Available
Posted by Elliot Metsger <em...@jhu.edu>.
David et al,
I've made some fixes, including what turned out to be an easy fix for
the assembler, which in turn fixed the binary distributions. I filed
PLUTO-309 and PLUTO-310 which I don't think need to hold up a release -
what do you think? I think we're ready to re-cut it -
Elliot
David H. DeWolf wrote:
> The test build of Pluto 1.1.0 is available.
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
> 1.1.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into
> account if a quality vote is called for this build.
>
> Release notes:
> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>
> Distribution:
> * http://people.apache.org/builds/portals-pluto/
>
> Maven 2 staging repository:
> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>
> We appreciate the time and effort everyone has put toward testing,
> contributing code and documentation, posting to the mailing lists, and
> logging issues.
>
> I will call a vote on this test build to determine it's status after
> allowing comments for a couple of days.
Re: Pluto 1.1.0 Test Build Available
Posted by Elliot Metsger <em...@jhu.edu>.
Hi David,
Thanks again for doing all this work. I plan on trying out the builds
tonight!!
Best,
Elliot
David H. DeWolf wrote:
> The test build of Pluto 1.1.0 is available.
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of Pluto
> 1.1.0 has been made, and at this time it is simply a "test build". We
> welcome any comments you may have, and will take all feedback into
> account if a quality vote is called for this build.
>
> Release notes:
> * http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0/README
>
> Distribution:
> * http://people.apache.org/builds/portals-pluto/
>
> Maven 2 staging repository:
> * http://people.apache.org/builds/portals-pluto/m2-staging-repository/
>
> We appreciate the time and effort everyone has put toward testing,
> contributing code and documentation, posting to the mailing lists, and
> logging issues.
>
> I will call a vote on this test build to determine it's status after
> allowing comments for a couple of days.