[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [commons-release-plugin] Next


> On May 13, 2018, at 4:18 PM, Gary Gregory <garydgregory@xxxxxxxxx> wrote:
> 
> On Sun, May 13, 2018, 12:00 Rob Tompkins <chtompki@xxxxxxxxx <mailto:chtompki@xxxxxxxxx>> wrote:
> 
>> 
>> 
>>> On May 13, 2018, at 10:26 AM, Gary Gregory <garydgregory@xxxxxxxxx>
>> wrote:
>>> 
>>> To be clear, I think we need a new goal for
>>> http://commons.apache.org/proper/commons-build-plugin/index.html, one
>> that
>>> invokes all. That would mean a new version of the _build_ plugin, as
>>> opposed to the _release_ plugin.
>>> 
>> 
>> Right. That was my impression.
>> 
> 
> I have a first cut done. Can you review?

Looking.


> 
> Gary
> 
> 
>>> Gary
>>> 
>>>> On Sat, May 12, 2018 at 2:51 PM, Rob Tompkins <chtompki@xxxxxxxxx>
>> wrote:
>>>> 
>>>> I can hop in and help out with some of those. And probably can put some
>>>> time into the plugin this week.
>>>> 
>>>>> On May 12, 2018, at 11:40 AM, Gary Gregory <garydgregory@xxxxxxxxx>
>>>> wrote:
>>>>> 
>>>>>> On Fri, May 11, 2018 at 7:53 PM, Rob Tompkins <chtompki@xxxxxxxxx>
>>>> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On May 10, 2018, at 12:11 PM, Gary Gregory <garydgregory@xxxxxxxxx>
>>>>>> wrote:
>>>>>>> 
>>>>>>>> On Thu, May 10, 2018 at 9:53 AM, Matt Sicker <boards@xxxxxxxxx>
>>>> wrote:
>>>>>>>> 
>>>>>>>>> On 10 May 2018 at 09:34, Gary Gregory <garydgregory@xxxxxxxxx>
>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Another item would be to have ONE Maven call instead of SIX for:
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> It would be great to just do "mvn release:prepare release:perform",
>>>> fill
>>>>>>>> out the release candidate version, and then have everything uploaded
>>>> and
>>>>>>>> emailed properly. Unfortunately, I'm not familiar enough with maven
>> to
>>>>>> know
>>>>>>>> how to automate that sort of thing (in the past, I've usually
>>>> offloaded
>>>>>>>> that part to a CI pipeline script of some sort).
>>>>>>>> 
>>>>>>> 
>>>>>>> Right, in a dream world, there would be a simple one-liner for
>> creating
>>>>>> an
>>>>>>> RC and another for promoting an RC to release.
>>>>>> 
>>>>>> All steps in that direction. I figure tackle the hard bits first, then
>>>>>> sort the remainders out. :-)
>>>>>> 
>>>>> 
>>>>> I'd like to release collections, text, pool, lang soon, so the better
>> the
>>>>> plugin, the happier the RM ;-)
>>>>> 
>>>>> I'm not sure how much time I can devote to helping on the plugin but I
>> am
>>>>> around to discuss and test.
>>>>> 
>>>>> Gary
>>>>> 
>>>>> 
>>>>>>> 
>>>>>>> Gary
>>>>>>> 
>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Matt Sicker <boards@xxxxxxxxx>
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
>>>>>> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx
>>>>>> 
>>>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
>>>> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx
>>>> 
>>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx <mailto:dev-unsubscribe@xxxxxxxxxxxxxxxxxx>
>> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx <mailto:dev-help@xxxxxxxxxxxxxxxxxx>