Mike,

Well, the first 10 or so times that I tried to do "mvn release:perform", the 
nifi-parent and nifi-nar-maven-plugin worked fine. For the nifi application 
release, release:perform failed because it was attempting to "batch upload" 
artifacts to some snapshot repository that I don't have permissions for.

I don't know if it's a feature of the maven release plugin or something in the 
apache parent pom that I don't understand maybe? But when I named the branch 
"nifi-0.1.0-incubating" and then named the SCM tag "nifi-0.1.0-incubating-rc1" 
or "-rc2" or what have you, that happened. Eventually, after many failures I 
found that if I name the branch "release-nifi-0.1.0-incubating" instead, all 
was okay. I have no idea what the naming of the git branch and the SCM tag have 
to do with each other (or it's possible that there's something else going on 
that i don't understand at all), but I just kept incrementing the RC number 
each time the build failed.

Thanks
-Mark


----------------------------------------
> From: [email protected]
> Date: Tue, 12 May 2015 12:51:48 -0500
> Subject: Re: [VOTE] Release Apache NiFi 0.1.0-incubating RC13
> To: [email protected]
>
> As somebody who hasn't been paying that close attention, how did we get up
> to RC13? That seems really high, and I don't feel like I would have missed
> that many votes.
>
> On Tue, May 12, 2015 at 11:28 AM, Sean Busbey <[email protected]> wrote:
>
>> On Tue, May 12, 2015 at 11:04 AM, Sergio Fernández <[email protected]>
>> wrote:
>>
>>>
>>>
>> 2) Also related with the source distribution, but also a personal opinion,
>>> I think such kind of releases with different versioning schemes make
>>> developers' life much harder. For instance, this is what I needed for
>>> building the releases from the source code repository:
>>>
>>> git clone https://git-wip-us.apache.org/repos/asf/incubator-nifi.git
>>> nifi
>>> cd nifi
>>> git checkout 37732bddcfcb2affcba1f3b4a9e3dd5ebd7b5a30
>>> cd nifi-parent/
>>> mvn clean install
>>> cd ..
>>> git checkout 1fc8453b36c1a1d600a911668f10249cf1e52ea7
>>> cd nifi-nar-maven-plugin/
>>> mvn clean install
>>> cd ..
>>> git checkout 65a07b6b634e04f44b5b89bfaf95e0ff35c3c68c
>>> cd nifi
>>> mvn clean install
>>>
>>> which is not very convenient...
>>>
>>>
>>
>> I believe the working assumption has been that normally we won't be doing a
>> nifi-parent or nifi-nar-maven-plugin release.
>>
>> --
>> Sean
>>
                                          

Reply via email to