You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2018/06/06 03:39:01 UTC
Re: [release-plugin] TODOs
On Thu, May 31, 2018 at 3:54 PM, Gilles <gi...@harfang.homelinux.org>
wrote:
> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
>
>> [...]
>>
>>>
>>>
>> I think we KISS it for the next release: let's not worry about
>> multi-module
>> projects. One bite at a time ;-)
>>
>
> Maybe I'm missing something (Should I have updated the components
> which I maintain in some other way than refer to the newest CP?),
> but are you aware that that recent versions have broken what used
> to work?[1]
> How are we supposed to use CP for multi-modules projects?
>
Note that you do not have to use our newish release plugin... it works
obviously, but we are still improving it.
Gary
>
> Thanks,
> Gilles
>
> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
> COMMONSSITE-114
>
> [...]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [release-plugin] TODOs
Posted by Rob Tompkins <ch...@gmail.com>.
> On Jun 5, 2018, at 11:39 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> On Thu, May 31, 2018 at 3:54 PM, Gilles <gi...@harfang.homelinux.org>
> wrote:
>
>>> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
>>>
>>> [...]
>>>
>>>>
>>>>
>>> I think we KISS it for the next release: let's not worry about
>>> multi-module
>>> projects. One bite at a time ;-)
>>>
>>
>> Maybe I'm missing something (Should I have updated the components
>> which I maintain in some other way than refer to the newest CP?),
>> but are you aware that that recent versions have broken what used
>> to work?[1]
>> How are we supposed to use CP for multi-modules projects?
>>
>
> Note that you do not have to use our newish release plugin... it works
> obviously, but we are still improving it.
I’m also hoping the the japicmp changes I added help us not have the problems we’ve seen. Though, that doesn’t mean that japicmp will work properly, only that including it in the project won’t break us.
-Rob
>
> Gary
>
>
>>
>> Thanks,
>> Gilles
>>
>> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
>> COMMONSSITE-114
>>
>> [...]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [release-plugin] TODOs
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, Jun 15, 2018 at 5:49 PM Rob Tompkins <ch...@gmail.com> wrote:
>
>
> > On Jun 15, 2018, at 7:10 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Now that 1.3 is in the VOTE process, I'd like to see the following for
> 1.4:
> >
> > - Post VOTE:
> > -- Perform the equivalent of svnmucc from dist/rev to dist/release
> > -- After the above runs, remove all remaining files and the site from
> > dist/dev
> >
>
> +1. Now that I’ve got a better bead on the svn-scm-provider it shouldn’t
> be too hard.
>
Sweet, as this was a pain point with multi-module components.
Gary
>
> > Gary
> >
> >
> >
> >> On Wed, Jun 6, 2018 at 6:06 AM Gilles <gi...@harfang.homelinux.org>
> wrote:
> >>
> >>> On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
> >>> On Thu, May 31, 2018 at 3:54 PM, Gilles
> >>> <gi...@harfang.homelinux.org>
> >>> wrote:
> >>>
> >>>>> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
> >>>>>
> >>>>> [...]
> >>>>>
> >>>>>>
> >>>>>>
> >>>>> I think we KISS it for the next release: let's not worry about
> >>>>> multi-module
> >>>>> projects. One bite at a time ;-)
> >>>>>
> >>>>
> >>>> Maybe I'm missing something (Should I have updated the components
> >>>> which I maintain in some other way than refer to the newest CP?),
> >>>> but are you aware that that recent versions have broken what used
> >>>> to work?[1]
> >>>> How are we supposed to use CP for multi-modules projects?
> >>>>
> >>>
> >>> Note that you do not have to use our newish release plugin... it
> >>> works
> >>> obviously,
> >>
> >> It worked for you, you mean; I evoked local problems, demonstrated
> >> by maven console logs.
> >> The COMMONSSITE-114 issue was one of incompatibility between maven
> >> and new (or upgraded) plugins; but the requirement was not documented.
> >>
> >> COMMONSSITE-115 is still a *blocker* for me. And I kindly remind that
> >> I've delayed (for more than 6 months now) the release of [RNG] on the
> >> premise that it would serve as a testing ground for ensuring that the
> >> release plugin did not make any wrong assumption about multi-module
> >> projects.
> >> Currently, none of the CP versions works for "mvn site" on my machine.
> >>
> >>> but we are still improving it.
> >>
> >> Great.
> >> But while developing *common* tools, shouldn't it be ensured that they
> >> do not break the build environment of any released component?
> >>
> >>
> >> Regards,
> >> Gilles
> >>
> >>>
> >>> Gary
> >>>
> >>>
> >>>>
> >>>> Thanks,
> >>>> Gilles
> >>>>
> >>>> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
> >>>> COMMONSSITE-114
> >>>>
> >>>> [...]
> >>>>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [release-plugin] TODOs
Posted by Rob Tompkins <ch...@gmail.com>.
> On Jun 15, 2018, at 7:10 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> Now that 1.3 is in the VOTE process, I'd like to see the following for 1.4:
>
> - Post VOTE:
> -- Perform the equivalent of svnmucc from dist/rev to dist/release
> -- After the above runs, remove all remaining files and the site from
> dist/dev
>
+1. Now that I’ve got a better bead on the svn-scm-provider it shouldn’t be too hard.
> Gary
>
>
>
>> On Wed, Jun 6, 2018 at 6:06 AM Gilles <gi...@harfang.homelinux.org> wrote:
>>
>>> On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
>>> On Thu, May 31, 2018 at 3:54 PM, Gilles
>>> <gi...@harfang.homelinux.org>
>>> wrote:
>>>
>>>>> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
>>>>>
>>>>> [...]
>>>>>
>>>>>>
>>>>>>
>>>>> I think we KISS it for the next release: let's not worry about
>>>>> multi-module
>>>>> projects. One bite at a time ;-)
>>>>>
>>>>
>>>> Maybe I'm missing something (Should I have updated the components
>>>> which I maintain in some other way than refer to the newest CP?),
>>>> but are you aware that that recent versions have broken what used
>>>> to work?[1]
>>>> How are we supposed to use CP for multi-modules projects?
>>>>
>>>
>>> Note that you do not have to use our newish release plugin... it
>>> works
>>> obviously,
>>
>> It worked for you, you mean; I evoked local problems, demonstrated
>> by maven console logs.
>> The COMMONSSITE-114 issue was one of incompatibility between maven
>> and new (or upgraded) plugins; but the requirement was not documented.
>>
>> COMMONSSITE-115 is still a *blocker* for me. And I kindly remind that
>> I've delayed (for more than 6 months now) the release of [RNG] on the
>> premise that it would serve as a testing ground for ensuring that the
>> release plugin did not make any wrong assumption about multi-module
>> projects.
>> Currently, none of the CP versions works for "mvn site" on my machine.
>>
>>> but we are still improving it.
>>
>> Great.
>> But while developing *common* tools, shouldn't it be ensured that they
>> do not break the build environment of any released component?
>>
>>
>> Regards,
>> Gilles
>>
>>>
>>> Gary
>>>
>>>
>>>>
>>>> Thanks,
>>>> Gilles
>>>>
>>>> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
>>>> COMMONSSITE-114
>>>>
>>>> [...]
>>>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [release-plugin] TODOs
Posted by Gary Gregory <ga...@gmail.com>.
Now that 1.3 is in the VOTE process, I'd like to see the following for 1.4:
- Post VOTE:
-- Perform the equivalent of svnmucc from dist/rev to dist/release
-- After the above runs, remove all remaining files and the site from
dist/dev
Gary
On Wed, Jun 6, 2018 at 6:06 AM Gilles <gi...@harfang.homelinux.org> wrote:
> On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
> > On Thu, May 31, 2018 at 3:54 PM, Gilles
> > <gi...@harfang.homelinux.org>
> > wrote:
> >
> >> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
> >>
> >>> [...]
> >>>
> >>>>
> >>>>
> >>> I think we KISS it for the next release: let's not worry about
> >>> multi-module
> >>> projects. One bite at a time ;-)
> >>>
> >>
> >> Maybe I'm missing something (Should I have updated the components
> >> which I maintain in some other way than refer to the newest CP?),
> >> but are you aware that that recent versions have broken what used
> >> to work?[1]
> >> How are we supposed to use CP for multi-modules projects?
> >>
> >
> > Note that you do not have to use our newish release plugin... it
> > works
> > obviously,
>
> It worked for you, you mean; I evoked local problems, demonstrated
> by maven console logs.
> The COMMONSSITE-114 issue was one of incompatibility between maven
> and new (or upgraded) plugins; but the requirement was not documented.
>
> COMMONSSITE-115 is still a *blocker* for me. And I kindly remind that
> I've delayed (for more than 6 months now) the release of [RNG] on the
> premise that it would serve as a testing ground for ensuring that the
> release plugin did not make any wrong assumption about multi-module
> projects.
> Currently, none of the CP versions works for "mvn site" on my machine.
>
> > but we are still improving it.
>
> Great.
> But while developing *common* tools, shouldn't it be ensured that they
> do not break the build environment of any released component?
>
>
> Regards,
> Gilles
>
> >
> > Gary
> >
> >
> >>
> >> Thanks,
> >> Gilles
> >>
> >> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
> >> COMMONSSITE-114
> >>
> >> [...]
> >>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [release-plugin] TODOs
Posted by Gilles <gi...@harfang.homelinux.org>.
On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
> On Thu, May 31, 2018 at 3:54 PM, Gilles
> <gi...@harfang.homelinux.org>
> wrote:
>
>> On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:
>>
>>> [...]
>>>
>>>>
>>>>
>>> I think we KISS it for the next release: let's not worry about
>>> multi-module
>>> projects. One bite at a time ;-)
>>>
>>
>> Maybe I'm missing something (Should I have updated the components
>> which I maintain in some other way than refer to the newest CP?),
>> but are you aware that that recent versions have broken what used
>> to work?[1]
>> How are we supposed to use CP for multi-modules projects?
>>
>
> Note that you do not have to use our newish release plugin... it
> works
> obviously,
It worked for you, you mean; I evoked local problems, demonstrated
by maven console logs.
The COMMONSSITE-114 issue was one of incompatibility between maven
and new (or upgraded) plugins; but the requirement was not documented.
COMMONSSITE-115 is still a *blocker* for me. And I kindly remind that
I've delayed (for more than 6 months now) the release of [RNG] on the
premise that it would serve as a testing ground for ensuring that the
release plugin did not make any wrong assumption about multi-module
projects.
Currently, none of the CP versions works for "mvn site" on my machine.
> but we are still improving it.
Great.
But while developing *common* tools, shouldn't it be ensured that they
do not break the build environment of any released component?
Regards,
Gilles
>
> Gary
>
>
>>
>> Thanks,
>> Gilles
>>
>> [1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
>> COMMONSSITE-114
>>
>> [...]
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org