You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2018/08/25 00:03:32 UTC

[ALL] SHA256/512 hashes

As noted in another thread, I don't think the recent change to the
Apache parent pom is of any use to  Commons.

However it does provide an example of how to use the checksum plugin.

This has been used to create a sample profile that could be added to CP.

See COMMONSSITE-121

Or for local testing, it can be added to a component POM.

It works for me with NET, also tried LANG.

(Using Maven 3.5.4)

There's probably still some work to get the files uploaded to the correct place.

S.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Gilles <gi...@harfang.homelinux.org>.
On Sat, 25 Aug 2018 19:05:55 +0200, Stefan Bodewig wrote:
> On 2018-08-25, Gilles wrote:
>
>> On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote:
>>> On 25 August 2018 at 09:48, Stefan Bodewig <bo...@apache.org>
>>> wrote:
>>>> On 2018-08-25, Gary Gregory wrote:
>
>>>>> Is what you are referring to for a different purpose?
>
>>>> Probably for those who don't want to use the release plugin :-)
>
>>> But yes, it could be used as an alternative hashing method.
>
>> I thought that the release plugin was intended for all
>> components to converge on the same release "recipe"...
>
> That's not my understanding. We vote on the release artifacts; how 
> these
> are created is up to the release manager. The release plugin offers a
> way to make releases easier but it is never going to become the only
> permitted way of cutting releases.

It's not what I meant either, even if it ultimately would
become the preferred, easy and fool-proof, way.
The suggestion is more on sub-project configuration (POM)
convergence.

Regards,
Gilles

>
> Stefan
>
> ---------------------------------------------------------------------
> 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: [ALL] SHA256/512 hashes

Posted by Stefan Bodewig <bo...@apache.org>.
On 2018-08-25, Gilles wrote:

> On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote:
>> On 25 August 2018 at 09:48, Stefan Bodewig <bo...@apache.org>
>> wrote:
>>> On 2018-08-25, Gary Gregory wrote:

>>>> Is what you are referring to for a different purpose?

>>> Probably for those who don't want to use the release plugin :-)

>> But yes, it could be used as an alternative hashing method.

> I thought that the release plugin was intended for all
> components to converge on the same release "recipe"...

That's not my understanding. We vote on the release artifacts; how these
are created is up to the release manager. The release plugin offers a
way to make releases easier but it is never going to become the only
permitted way of cutting releases.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Gilles <gi...@harfang.homelinux.org>.
On Sun, 26 Aug 2018 10:43:02 +0200, Thomas Vandahl wrote:
> On 25.08.18 16:14, Gilles wrote:
>>>> Probably for those who don't want to use the release plugin :-)
>>>
>>> I was mainly following up on the thread about updating CP to AP 21 
>>> [1]
>>>
>>> But yes, it could be used as an alternative hashing method.
>>
>> I thought that the release plugin was intended for all
>> components to converge on the same release "recipe"...
>
> This is unlikely to happen as long as it does not cover multi-module 
> builds.

"Commons RNG" is multi-module and v1.1 was RMed by Rob
with his release-plugin.

Gilles

P.S. I hope that Rob will update the [RNG] step-by-step howto,
      currently in "doc/release" directory, so that anyone else
      can duplicate his feat. ;-)

>
> Bye, Thomas.
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Gilles <gi...@harfang.homelinux.org>.
On Tue, 28 Aug 2018 10:25:54 +0200, Mark Struberg wrote:
>> This is unlikely to happen as long as it does not cover multi-module 
>> builds
>
> The maven-release-plugin covers multi-module releases since many 
> years.
>
> In the projects I'm working on there is no 'release manager'.
> _Everybody_ can do releases without having to know anything special.
> This is where the maven-release-plugin really shines.
> Just use mvn release:prepare + mvn release:perform and be done.
>
> Of course it's fine if projects use ant, etc.
> But ideally there should be a single way to kick of a release (fully
> automated, same target name across projects, etc)

+1

Since the goal is the same the same across components (generate
JAR files and upload them to Nexus), having several ways is
duplicating maintenance effort.

Regards,
Gilles

>
> LieGrue,
> strub
>
>
>> Am 26.08.2018 um 10:43 schrieb Thomas Vandahl <tv...@apache.org>:
>>
>> On 25.08.18 16:14, Gilles wrote:
>>>>> Probably for those who don't want to use the release plugin :-)
>>>>
>>>> I was mainly following up on the thread about updating CP to AP 21 
>>>> [1]
>>>>
>>>> But yes, it could be used as an alternative hashing method.
>>>
>>> I thought that the release plugin was intended for all
>>> components to converge on the same release "recipe"...
>>
>> This is unlikely to happen as long as it does not cover multi-module 
>> builds.
>>
>> Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Mark Struberg <st...@yahoo.de.INVALID>.
> This is unlikely to happen as long as it does not cover multi-module builds

The maven-release-plugin covers multi-module releases since many years.

In the projects I'm working on there is no 'release manager'.
_Everybody_ can do releases without having to know anything special.
This is where the maven-release-plugin really shines. 
Just use mvn release:prepare + mvn release:perform and be done.

Of course it's fine if projects use ant, etc.
But ideally there should be a single way to kick of a release (fully automated, same target name across projects, etc)

LieGrue,
strub


> Am 26.08.2018 um 10:43 schrieb Thomas Vandahl <tv...@apache.org>:
> 
> On 25.08.18 16:14, Gilles wrote:
>>>> Probably for those who don't want to use the release plugin :-)
>>> 
>>> I was mainly following up on the thread about updating CP to AP 21 [1]
>>> 
>>> But yes, it could be used as an alternative hashing method.
>> 
>> I thought that the release plugin was intended for all
>> components to converge on the same release "recipe"...
> 
> This is unlikely to happen as long as it does not cover multi-module builds.
> 
> Bye, Thomas.
> 
> ---------------------------------------------------------------------
> 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: [ALL] SHA256/512 hashes

Posted by Thomas Vandahl <tv...@apache.org>.
On 25.08.18 16:14, Gilles wrote:
>>> Probably for those who don't want to use the release plugin :-)
>>
>> I was mainly following up on the thread about updating CP to AP 21 [1]
>>
>> But yes, it could be used as an alternative hashing method.
> 
> I thought that the release plugin was intended for all
> components to converge on the same release "recipe"...

This is unlikely to happen as long as it does not cover multi-module builds.

Bye, Thomas.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Gilles <gi...@harfang.homelinux.org>.
On Sat, 25 Aug 2018 14:06:44 +0100, sebb wrote:
> On 25 August 2018 at 09:48, Stefan Bodewig <bo...@apache.org> 
> wrote:
>> On 2018-08-25, Gary Gregory wrote:
>>
>>> Our release plugin already creates SHA256 and SHA512 files and 
>>> saves those
>>> to Apache's dev/dist for an RC as part of creating an RC, pushing 
>>> it to
>>> Nexus and dist/dev.
>
> Ah, I've not looked at that yet.
>
>>> Is what you are referring to for a different purpose?
>>
>> Probably for those who don't want to use the release plugin :-)
>
> I was mainly following up on the thread about updating CP to AP 21 
> [1]
>
> But yes, it could be used as an alternative hashing method.

I thought that the release plugin was intended for all
components to converge on the same release "recipe"...

> In which case, if it is going to be put in CP rather than individual
> POMs, it should be in its own profile.
> (Or possibly two, one for SHA256 and one for SHA512?)

+1 for *one* profile that leaves no room for working around
global policy (thus simplifying release review work).
Couldn't CP use a "property" from AP to ensure that the
required hash is generated or the build will fail?

Gilles

>
> [1]
> 
> https://lists.apache.org/thread.html/a130864e39cc4ffb15c4018dc05142a405861b523fd14573010ea3e0@%3Cdev.commons.apache.org%3E
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by sebb <se...@gmail.com>.
On 25 August 2018 at 09:48, Stefan Bodewig <bo...@apache.org> wrote:
> On 2018-08-25, Gary Gregory wrote:
>
>> Our release plugin already creates SHA256 and SHA512 files and saves those
>> to Apache's dev/dist for an RC as part of creating an RC, pushing it to
>> Nexus and dist/dev.

Ah, I've not looked at that yet.

>> Is what you are referring to for a different purpose?
>
> Probably for those who don't want to use the release plugin :-)

I was mainly following up on the thread about updating CP to AP 21 [1]

But yes, it could be used as an alternative hashing method.
In which case, if it is going to be put in CP rather than individual
POMs, it should be in its own profile.
(Or possibly two, one for SHA256 and one for SHA512?)

[1] https://lists.apache.org/thread.html/a130864e39cc4ffb15c4018dc05142a405861b523fd14573010ea3e0@%3Cdev.commons.apache.org%3E

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Stefan Bodewig <bo...@apache.org>.
On 2018-08-25, Gary Gregory wrote:

> Our release plugin already creates SHA256 and SHA512 files and saves those
> to Apache's dev/dist for an RC as part of creating an RC, pushing it to
> Nexus and dist/dev.

> Is what you are referring to for a different purpose?

Probably for those who don't want to use the release plugin :-)

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [ALL] SHA256/512 hashes

Posted by Gary Gregory <ga...@gmail.com>.
Our release plugin already creates SHA256 and SHA512 files and saves those
to Apache's dev/dist for an RC as part of creating an RC, pushing it to
Nexus and dist/dev.

Is what you are referring to for a different purpose?

Gary

On Fri, Aug 24, 2018 at 6:03 PM sebb <se...@gmail.com> wrote:

> As noted in another thread, I don't think the recent change to the
> Apache parent pom is of any use to  Commons.
>
> However it does provide an example of how to use the checksum plugin.
>
> This has been used to create a sample profile that could be added to CP.
>
> See COMMONSSITE-121
>
> Or for local testing, it can be added to a component POM.
>
> It works for me with NET, also tried LANG.
>
> (Using Maven 3.5.4)
>
> There's probably still some work to get the files uploaded to the correct
> place.
>
> S.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>