Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/12
Don't worry about Coveralls, I see the same behaviour for other projects as
well.
I think this is related to our Travis CI setup using different JDKs and
Coveralls picks whichever b
They won't be signed or hashed if the files are not "attached" because then
they are not officially output artifacts of the build, and won't be
deployed.
You can run hashing and signing plugins manually, but then the ordering of
the phases matter; to avoid a race condition where the assembly plugi
Well, getting SHA-1 hashes is not awesome either, we really need a plugin
updated to use SHA-2/SHA-256
Gary
On Sat, Dec 3, 2016 at 11:57 AM, Matt Sicker wrote:
> The source jar does just include the .java/.scala/etc. files along with
> anything in src/main/resources/ (and anything else configur
I am not mentioning SHA-3 but you get my point.
Gary
On Sat, Dec 3, 2016 at 12:02 PM, Gary Gregory
wrote:
> Well, getting SHA-1 hashes is not awesome either, we really need a plugin
> updated to use SHA-2/SHA-256
>
> Gary
>
> On Sat, Dec 3, 2016 at 11:57 AM, Matt Sicker wrote:
>
>> The source
The source jar does just include the .java/.scala/etc. files along with
anything in src/main/resources/ (and anything else configured, though this
is the default). I think that a source jar is required for distribution on
maven central. Besides making releases on the /dist/ svn repo, there's
reposi
On Dec 3, 2016 9:34 AM, "Charles Honton" wrote:
>
> To follow up the thread on releasing parent 42 and exactly what needs to
signed, etc. I’ve researched asf release policy. Here’s the gist:
>
> 1. Every ASF release must contain a source package, which must be
sufficient for a user to build and
Github user plamentotev commented on the issue:
https://github.com/apache/commons-compress/pull/12
Hmm, looks like @coveralls acts strange. The first time it says my commit
are increasing the code coverage and after that they are decreasing it. And
there is no code changes - I only fi
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/12
[![Coverage
Status](https://coveralls.io/builds/9115191/badge)](https://coveralls.io/builds/9115191)
Coverage decreased (-0.01%) to 82.598% when pulling
**3e8a619ace3e03377fc
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/12
[![Coverage
Status](https://coveralls.io/builds/9115133/badge)](https://coveralls.io/builds/9115133)
Coverage increased (+0.008%) to 82.616% when pulling
**60fe42d6fc19e9e4dd
GitHub user plamentotev opened a pull request:
https://github.com/apache/commons-compress/pull/12
COMPRESS-375 Allow the differed creation of `ZipArchiveEntry` for parallel
zips
This is my attempt to implement the changes suggested in
[COMPRESS-375](https://issues.apache.org/jira/b
To follow up the thread on releasing parent 42 and exactly what needs to
signed, etc. I’ve researched asf release policy. Here’s the gist:
1. Every ASF release must contain a source package, which must be sufficient
for a user to build and test the release provided they have access to the
app
So, when I run:
mvn clean deploy -Duser.name=ggregory -Prelease -Ptest-deploy
The zip and gz files are created but not signed or hashed.
Thoughts?
Gary
On Sat, Dec 3, 2016 at 2:53 AM, Stian Soiland-Reyes
wrote:
> I would prefer the source distribution to also be deployed in Maven
> Central,
On 3 December 2016 at 15:18, Jochen Wiedmann wrote:
> On Sat, Dec 3, 2016 at 4:12 PM, Gary Gregory wrote:
>
>> *.asc
>> *.asc.asc
>> *.asc.asc.asc
>> *.asc.asc.asc.asc
>>
>> I've never seen x4 the ASC. That can't be right. Did you do not mvn tasks
>> over and over without cleaning or something li
On Sat, Dec 3, 2016 at 4:12 PM, Gary Gregory wrote:
> *.asc
> *.asc.asc
> *.asc.asc.asc
> *.asc.asc.asc.asc
>
> I've never seen x4 the ASC. That can't be right. Did you do not mvn tasks
> over and over without cleaning or something like that?
I did release:prepare repeatedly. However, I did a si
*.asc
*.asc.asc
*.asc.asc.asc
*.asc.asc.asc.asc
I've never seen x4 the ASC. That can't be right. Did you do not mvn tasks
over and over without cleaning or something like that?
Gary
-- Forwarded message --
From: Nexus Repository Manager
Date: Sat, Dec 3, 2016 at 7:05 AM
Subject
On Sat, 3 Dec 2016 10:53:27 +, Stian Soiland-Reyes wrote:
I would prefer the source distribution to also be deployed in Maven
Central, as most Maven projects now do through the Apache super pom
(but
then called -source-release). This means the Maven distribution for a
particular version sho
I would prefer the source distribution to also be deployed in Maven
Central, as most Maven projects now do through the Apache super pom (but
then called -source-release). This means the Maven distribution for a
particular version should be completely reproducible without having to hunt
around the a
17 matches
Mail list logo