Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4

Do we want a Jenkins at CloudBees? Might be easier for people to grok? On Tuesday, 19 March 2013, Robert Scholte wrote: > Let me go through all the jobs. > It looks to me something has changed, because I'm pretty sure I configured > notifications for failed builds and first successful to all comm

[mojo-dev] [jira] (MBUILDHELPER-54) Define the maven property with the initial value if the regex don't match...

Baptiste Mathus

[mojo-dev] [jira] (MBUILDHELPER-53) regex-property goal should allow an empty replacement

Baptiste

Re: [mojo-dev] Mojo Staging Ruleset to check for hashes consistency? (was: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3)

OK, thanks. Just created https://jira.codehaus.org/browse/HAUS-2300 I guess it's easier to track than mails :-). Cheers 2013/3/19 Robert Scholte > I don't think anybody of us has those rights. > These kind of questions can be send to supp...@codehaus.org > If it requires an action, create a ji

Re: [mojo-dev] [VOTE] Release animal sniffer signatures-parent 1.2, java16 1.1, java17 1.0

"Just a thought, the parent pom and java17 site is deployed using new skin, we should then redeploy other sites (using m-siteskinner-p ?)" +1, shouldn't be that hard, only quite a number of subsites On Mon, 18 Mar 2013 23:58:09 +0100, Tony Chemit wrote: Just a thought, the parent pom and

Re: [mojo-dev] Mojo Staging Ruleset to check for hashes consistency? (was: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3)

I don't think anybody of us has those rights. These kind of questions can be send to supp...@codehaus.org If it requires an action, create a jira issue at https://jira.codehaus.org/browse/HAUS (you don't have to be a despot to do that ;) otherwise I can ask it for you) Robert On Tue, 19 Ma

[mojo-dev] [jira] (MEXEC-86) outputFile support for capturing exec not functional

Robert Scholte

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4

Let me go through all the jobs. It looks to me something has changed, because I'm pretty sure I configured notifications for failed builds and first successful to all committers (users who have committed to the build) for every mojo job. No real need to keep checking Bamboo as long as its gr

[mojo-dev] [jira] (MBUILDHELPER-54) Define the maven property with the initial value if the regex don't match...

Baptiste

[mojo-dev] [jira] (MEXEC-86) outputFile support for capturing exec not functional

Tuure Laurinolli

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3

In case anyone is wondering: this vote is *not cancelled*. It's still running. Thanks 2013/3/19 Baptiste MATHUS > Hi, > Well, what you want is actually not possible since take 1 and 2 were > normally dropped (and never promoted outside mojo staging repos), so I > haven't the corresponding hash

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3

Hi, Well, what you want is actually not possible since take 1 and 2 were normally dropped (and never promoted outside mojo staging repos), so I haven't the corresponding hashes anymore. "Nothing to distinguish it by" is a bit strong-worded, I guess. There're file dates (which is a bit naively simp

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3

Fred, could you please discuss this in a separate thread? It's not unique to this vote. If you think something could be improved in the voting process, update the guidelines or similar. Baptiste has followed the current guidelines. /Anders On Tue, Mar 19, 2013 at 12:14 PM, Fred Cooke wrote: >

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3

Because there are now three distinct 1.0-alpha-4 variants out there, I'd like you to explicitly tell me which one is "take 3", by giving us the md5/sha1 for each artifact of variety "take 3". IE, if I just get one from a repo somewhere, it could be cached/old/take2/take1/take0?/etc, and although th

[mojo-dev] Mojo Staging Ruleset to check for hashes consistency? (was: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3)

Hi, As a follow-up to the vote still being run, I'd like to check if we have the "Staging Checksum Validation" as a ruleset for our staging repositories? (See [1] Though this does not seem to be the case here, that would prevent pushing stale data, isn't it? I checked and it seems I'm not allowed

[mojo-dev] [jira] (MOJO-1886) osxappbundle doesn't correctly detect MacOS on OpenJDK

  Daniel Muhra edited a c

[mojo-dev] [jira] (MOJO-1886) osxappbundle doesn't correctly detect MacOS on OpenJDK

Daniel Muhra

[mojo-dev] [jira] (MBUILDHELPER-54) Define the maven property with the initial value if the regex don't match...

PÉRIÉ Fabien

[mojo-dev] [jira] (MBUILDHELPER-54) Define the maven property with the initial value if the regex don't match...

PÉRIÉ Fabien

[mojo-dev] [jira] (MBUILDHELPER-53) regex-property goal should allow an empty replacement

PÉRIÉ Fabien

[mojo-dev] [jira] (MBUILDHELPER-54) Define the maven property with the initial value if the regex don't match...

PÉRIÉ Fab

Re: [mojo-dev] [VOTE] Release extra-enforcer-rules version 1.0-alpha-4 - take 3

Hi, Could you please give more precisions about the issue you're having with MD5/SHA1? Which artifacts have wrong hashes from your tests? It would help. I just verified the extra-enforcer-rules jar

[mojo-dev] [jira] (MLICENSE-72) Download licenses from third-party definition

Tony Chemit