On 2/23/08, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> We've has discussions about this previously. I stand by my position that
> changes like these should tried out in at least one component release,
> before they are included in the parent pom. It's a way of verifying that
> the changes actu
We've has discussions about this previously. I stand by my position that
changes like these should tried out in at least one component release,
before they are included in the parent pom. It's a way of verifying that
the changes actually works during a release.
James Carman wrote:
All,
I've
On Sat, Feb 23, 2008 at 2:58 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> All,
>
> I've been working on the release candidate for commons-proxy-1.0 (if
> you couldn't tell by the SVN traffic). I have created my own "rc"
> profile in proxy's pom.xml file. I think we should push those changes
>
Okay, here's what I've done to proxy's pom.xml file. I've added my
own "rc" profile which basically does the same thing as the parent's
profile (I copied it). Only, it defines a different site deployment
url. The url is calculated based on a couple of properties. The
first is ${releaseManager}
On 2/23/08, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
> It would help me, if you'd describe the changes relative to the
> previous version rather than displaying the complete profile.
Well, basically I just changed where the generated site will go. The
directory where it will go is now calculat
On Sat, Feb 23, 2008 at 3:58 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> I've been working on the release candidate for commons-proxy-1.0 (if
> you couldn't tell by the SVN traffic). I have created my own "rc"
> profile in proxy's pom.xml file. I think we should push those changes
> to com
All,
I've been working on the release candidate for commons-proxy-1.0 (if
you couldn't tell by the SVN traffic). I have created my own "rc"
profile in proxy's pom.xml file. I think we should push those changes
to commons-parent. Here's what it looks like:
rc
