You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shale.apache.org by Rahul Akolkar <ra...@gmail.com> on 2008/04/18 22:19:17 UTC
Master pom changes (was: Release Shale Master POM Version 3)
On 4/18/08, Greg Reddin <gr...@gmail.com> wrote:
> I would like to cancel this vote and go ahead and implement the
> changes outlined by Rahul that will keep the site from redeploying
> when the master-pom is released. You can track progress in SHALE-487:
>
> https://issues.apache.org/struts/browse/SHALE-487
>
> Any objections?
>
<snip/>
None, thanks for doing this. If the master pom v3 hasn't been sync'ed
to central, I don't mind doing a take 2 on it (otherwise we can move
on to v4).
I've locked down some other commonly used plugins. There are some
TODOs, I'll comment on SHALE-487 where we're tracking this.
-Rahul
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, May 2, 2008 at 2:02 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>
> I think the master pom is mostly ready for a vote (unless you're
> having issues with the build due to any particular now-locked-down
> plugin that you weren't having before).
No issues. I was just trying to decide whether to go ahead and move
all the plugins to the latest versions or just release it as it is and
do that later. Depending on how much time I can find this weekend I
may go ahead and push for a release as it is now.
Thanks,
Greg
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Rahul Akolkar <ra...@gmail.com>.
On 5/2/08, Greg Reddin <gr...@gmail.com> wrote:
> On Fri, May 2, 2008 at 10:42 AM, Paul Spencer <pa...@apache.org> wrote:
> > Greg,
> > Thank you for the update.
> >
> > For clarification, what are you artifacts are you planning on releasing in
> > the near future.
>
>
> We are going to try to do a 1.0.5 release of the entire framework. But
> there are a few changes that need to be made to the master pom first.
> So the plan is:
>
> 1) Bring the master pom up to date and release it.
>
> 2) Release 1.0.5 of all framework components.
>
> Then I will start looking at getting 1.1.0 up to snuff for a release.
>
<snip/>
Sounds very good.
I think the master pom is mostly ready for a vote (unless you're
having issues with the build due to any particular now-locked-down
plugin that you weren't having before).
-Rahul
>
> Greg
>
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, May 2, 2008 at 10:42 AM, Paul Spencer <pa...@apache.org> wrote:
> Greg,
> Thank you for the update.
>
> For clarification, what are you artifacts are you planning on releasing in
> the near future.
We are going to try to do a 1.0.5 release of the entire framework. But
there are a few changes that need to be made to the master pom first.
So the plan is:
1) Bring the master pom up to date and release it.
2) Release 1.0.5 of all framework components.
Then I will start looking at getting 1.1.0 up to snuff for a release.
Greg
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Paul Spencer <pa...@apache.org>.
Greg,
Thank you for the update.
For clarification, what are you artifacts are you planning on releasing
in the near future.
Paul Spencer
Greg Reddin wrote:
> On Fri, Apr 18, 2008 at 6:58 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> > I was hoping to just redo it. It has not been sync'ed yet so I'll just
>> > svn rm the tag and the artifacts on the staging repo and to it over.
>> >
>
> In case anyone's wondering, I'm still planning to continue the release
> process. I was going to get back on it this week, but I've decided to
> wait until the svn issues are resolved. In the meantime, when I can
> find time I will track down the further changes needed to the master
> pom.
>
> Thanks,
> Greg
>
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, Apr 18, 2008 at 6:58 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> > I was hoping to just redo it. It has not been sync'ed yet so I'll just
> > svn rm the tag and the artifacts on the staging repo and to it over.
> >
In case anyone's wondering, I'm still planning to continue the release
process. I was going to get back on it this week, but I've decided to
wait until the svn issues are resolved. In the meantime, when I can
find time I will track down the further changes needed to the master
pom.
Thanks,
Greg
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Rahul Akolkar <ra...@gmail.com>.
On 4/18/08, Greg Reddin <gr...@gmail.com> wrote:
> On Fri, Apr 18, 2008 at 3:19 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> >
> > None, thanks for doing this. If the master pom v3 hasn't been sync'ed
> > to central, I don't mind doing a take 2 on it (otherwise we can move
> > on to v4).
>
>
> I was hoping to just redo it. It has not been sync'ed yet so I'll just
> svn rm the tag and the artifacts on the staging repo and to it over.
>
<snip/>
Sure.
-Rahul
Re: Master pom changes (was: Release Shale Master POM Version 3)
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, Apr 18, 2008 at 3:19 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>
> None, thanks for doing this. If the master pom v3 hasn't been sync'ed
> to central, I don't mind doing a take 2 on it (otherwise we can move
> on to v4).
I was hoping to just redo it. It has not been sync'ed yet so I'll just
svn rm the tag and the artifacts on the staging repo and to it over.
Greg