> On May 31, 2018, at 11:40 AM, Gary Gregory <[email protected]> wrote:
> 
> Is it more complicated that creating an Ant task that executes svn mucc?

Maybe. It depends on how general we’re trying to be. Are we trying to 
accommodate a multi-module project? Does svn mucc accommodate directory 
recursive moves?

-Rob

> 
> Gary
> 
> On Thu, May 31, 2018 at 7:31 AM, Rob Tompkins <[email protected]> wrote:
> 
>> Still chipping away at that one.
>> 
>>> On May 30, 2018, at 5:24 PM, Gary Gregory <[email protected]>
>> wrote:
>>> 
>>> BTW, where are you on doing the SVN mucc from
>>> http://commons.apache.org/releases/release.html?
>>> 
>>> Gary
>>> 
>>> On Wed, May 30, 2018 at 3:22 PM, Gary Gregory <[email protected]>
>>> wrote:
>>> 
>>>> 
>>>> 
>>>>> On Wed, May 30, 2018 at 1:08 PM, Rob Tompkins <[email protected]>
>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> On May 30, 2018, at 2:40 PM, Gary Gregory <[email protected]>
>>>>> wrote:
>>>>>> 
>>>>>> Hi Rob:
>>>>>> 
>>>>>> The
>>>>>> method org.apache.commons.release.plugin.mojos.CommonsDistributionD
>>>>> etachmentMojo.hashArtifacts()
>>>>>> seems like it is only used for logging. Surely we can log hashes the
>>>>> first
>>>>>> time we compute them. It looks like we are computing them x2.
>>>>> 
>>>>> I think what I just committed accomplishes what we’re going for there.
>>>>> Yeah?
>>>>> 
>>>> 
>>>> Yep, that works, thank you,
>>>> Gary
>>>> 
>>>> 
>>>>>> 
>>>>>> Gary
>>>>>> 
>>>>>> On Wed, May 30, 2018 at 10:49 AM, Gary Gregory <
>> [email protected]>
>>>>>> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Tue, May 29, 2018 at 2:11 PM, Gary Gregory <
>> [email protected]>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Hi Rob and All:
>>>>>>>> 
>>>>>>>> I see the following TODOs before releasing 1.3:
>>>>>>>> 
>>>>>>>> - Commit the site as is to the dist folder so that links in a VOTE
>>>>> email
>>>>>>>> work (like 'The CLIRR report is here). I am not sure we still need
>>>>> the site
>>>>>>>> zip. I am not sure we need to make that an option, needs feedback.
>>>>>>>> - Match the dist path and tag names to match what the vote-txt goal
>>>>>>>> generates (see src/main/resources/commons-xdo
>>>>>>>> c-templates/vote-txt-template.txt)
>>>>>>>> 
>>>>>>> 
>>>>>>> This matching is not an issue, the 46-SNAPSHOT parent now says:
>>>>>>>  <commons.distSvnStagingUrl>scm:svn:https://dist.apache.
>>>>>>> org/repos/dist/dev/commons/${commons.componentid}/${
>>>>>>> commons.release.version}-${commons.rc.version}</commons.dist
>>>>> SvnStagingUrl>
>>>>>>> 
>>>>>>> 
>>>>>>> So until 46 comes out, a component POM needs to say the same thing to
>>>>> use
>>>>>>> the vote-txt goal (when it comes out in the release plugin 1.3.)
>>>>>>> 
>>>>>>> Gary
>>>>>>> 
>>>>>>> 
>>>>>>>> Extra Credit: How do we get the NNNN after a deploy for a URL
>>>>>>>> https://repository.apache.org/content/repositories/orgap
>>>>>>>> achecommons-NNNN/org/apache/commons/@ARTIFACTID@/@VERSION@/
>>>>>>>> 
>>>>>>>> Gary
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>> 
>>>>> 
>>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to