You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2007/01/19 00:24:06 UTC
Re: Struts 2.0.3 status - Retag?
I forgot that we needed to sign the Maven artificats separately before
the deploy step.
I haven't been able to get the other signing scripts to work, but
Wendy's new release gopal does seem to be doing the job for me.
Problem is, the new goal was checked in after the 2.0.3 tag. The
simplest thing might be to retag the head as 2.0.3 and try again.
Are there any recent commits to the head that we would not want to be
part of 2.0.3?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Ted Husted <hu...@apache.org>.
As mentioned in the Struts-Annotations thread, there will be an issue
with building applications with Maven, in that it will pull down an
unnecessary snapshot of the struts-annotatios JAR.
For now, I think we should let Struts 2.0.3 lie as a test build. When
we sort out the build issues, we can try again with Struts 2.0.4.
Perhaps by then, we will also have a performance boost in the form of
the template caching that Phil and Tom have been working on.
I'm out of town next week, and I don't know what sort of connectivity
I'll have. But, I would be available to try again next weekend.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Musachy Barroso <mb...@wfscorp.com>.
Any chance of getting this minor, but really annoying thing in:
https://issues.apache.org/struts/browse/WW-1602 ?
musachy
Don Brown wrote:
> Nope, and it would be a good thing as I fixed the portlet example and
> a few other minor bugs.
>
> Don
>
> Ted Husted wrote:
>> I forgot that we needed to sign the Maven artificats separately before
>> the deploy step.
>>
>> I haven't been able to get the other signing scripts to work, but
>> Wendy's new release gopal does seem to be doing the job for me.
>>
>> Problem is, the new goal was checked in after the 2.0.3 tag. The
>> simplest thing might be to retag the head as 2.0.3 and try again.
>>
>> Are there any recent commits to the head that we would not want to be
>> part of 2.0.3?
>>
>> -Ted.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Don Brown <mr...@twdata.org>.
Nope, and it would be a good thing as I fixed the portlet example and a
few other minor bugs.
Don
Ted Husted wrote:
> I forgot that we needed to sign the Maven artificats separately before
> the deploy step.
>
> I haven't been able to get the other signing scripts to work, but
> Wendy's new release gopal does seem to be doing the job for me.
>
> Problem is, the new goal was checked in after the 2.0.3 tag. The
> simplest thing might be to retag the head as 2.0.3 and try again.
>
> Are there any recent commits to the head that we would not want to be
> part of 2.0.3?
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Ted Husted <hu...@apache.org>.
That seems to do it. I'll redeploy the Maven artifacts later and then
start the vote.
Thanks again, Rahul. Your posts are always helpful.
-Ted.
On 1/19/07, Rahul Akolkar <ra...@gmail.com> wrote:
> On 1/19/07, Ted Husted <hu...@apache.org> wrote:
> > I've tagged, rolled, and uploaded 2.0.3 again, but the Maven sources
> > are not showing up in the deployment to the staging folder or in my
> > local repository . I don't know why the sources are not being built
> > for me. The steps I followed are at
> >
> > * http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
> >
> <snip/>
>
> That source (and javadoc) plugins seems to be part of the 'alljars'
> profile in the parent pom [1], which would need to be included in the
> -P list in the above recipe.
>
> Another option (for v2.0.4, since it requires a pom change) would be
> to merge the 'alljars' profile into the 'release' profile, as the
> Shale framework parent pom [2] does.
>
> -Rahul
>
> [1] http://svn.apache.org/repos/asf/struts/struts2/trunk/pom.xml
> [2] http://svn.apache.org/repos/asf/shale/framework/trunk/pom.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Rahul Akolkar <ra...@gmail.com>.
On 1/19/07, Ted Husted <hu...@apache.org> wrote:
> I've tagged, rolled, and uploaded 2.0.3 again, but the Maven sources
> are not showing up in the deployment to the staging folder or in my
> local repository . I don't know why the sources are not being built
> for me. The steps I followed are at
>
> * http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
>
<snip/>
That source (and javadoc) plugins seems to be part of the 'alljars'
profile in the parent pom [1], which would need to be included in the
-P list in the above recipe.
Another option (for v2.0.4, since it requires a pom change) would be
to merge the 'alljars' profile into the 'release' profile, as the
Shale framework parent pom [2] does.
-Rahul
[1] http://svn.apache.org/repos/asf/struts/struts2/trunk/pom.xml
[2] http://svn.apache.org/repos/asf/shale/framework/trunk/pom.xml
>
> --
> HTH, Ted.
> * http://www.husted.com/struts/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.0.3 status - Retag?
Posted by Ted Husted <hu...@apache.org>.
I've tagged, rolled, and uploaded 2.0.3 again, but the Maven sources
are not showing up in the deployment to the staging folder or in my
local repository . I don't know why the sources are not being built
for me. The steps I followed are at
* http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
-Ted.
On 1/18/07, Ted Husted <hu...@apache.org> wrote:
> I forgot that we needed to sign the Maven artificats separately before
> the deploy step.
>
> I haven't been able to get the other signing scripts to work, but
> Wendy's new release gopal does seem to be doing the job for me.
>
> Problem is, the new goal was checked in after the 2.0.3 tag. The
> simplest thing might be to retag the head as 2.0.3 and try again.
>
> Are there any recent commits to the head that we would not want to be
> part of 2.0.3?
>
> -Ted.
>
--
HTH, Ted.
* http://www.husted.com/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org