Re: MCOMPILER-165

2012-02-24 Thread Kristian Rosenvold
There's always tons of exceptions, most of the time we're actually
busy doing DayJobs.

So if we have been looking the other way for too long, do
ping us. MCOMPILER-140 was just closed ;)

Kristian


2012/2/23 Jesse Glick jesse.gl...@oracle.com:
 On 02/17/2012 08:14 AM, Kristian Rosenvold wrote:

 As long as the patch is to the appropriate
 code style and containst test-cases,  we will review it.


 Not true in the case of e.g. MCOMPILER-140.


 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Subject: [VOTE] Release Maven Checkstyle Plugin version 2.9.1

2012-02-24 Thread Dennis Lundberg
Hi Chris

Since version 2.4 of maven-checkstyle-plugin it is stated on its start
page which version of Checkstyle is used by the plugin. Follow the
link to the staging site below. Replace the version number in the URL
to look at the docs for another version of the plugin.

On Fri, Feb 24, 2012 at 2:38 AM, Chris Graham chrisgw...@gmail.com wrote:
 Hey Guys,

 Can I get some site updates rolled into this or is it too late?

 What's missing from the site is a cross reference of what versions
 ofcheckstyle  the maven plugin uses per maven plugin release!

 It was a real PITA - the only way I could do it was to troll through
 each and every maven-checksyle-plugin pom.xml and look.

 Can we roll it into this release?

 Or should I open a separate issue, with a patch and let it get roll
 over to the next one, when ever that will be?

 -Chris

 On Fri, Feb 24, 2012 at 6:21 AM, Tony Chemit che...@codelutin.com wrote:
 On Wed, 22 Feb 2012 14:50:55 +0100
 Dennis Lundberg denn...@apache.org wrote:

 +1 (non binding)

 thansk,

 tony.

 Hi,

 We solved 1 issue:
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=18335

 There are still a couple of issues left in JIRA:
 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1

 Staging repo:
 https://repository.apache.org/content/repositories/maven-007/

 Staging site:
 http://maven.apache.org/plugins/maven-checkstyle-plugin-2.9.1/

 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1



 --
 Tony Chemit
 
 tél: +33 (0) 2 40 50 29 28
 email: che...@codelutin.com
 http://www.codelutin.com

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Dennis Lundberg

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Subject: [VOTE] Release Maven Checkstyle Plugin version 2.9.1

2012-02-24 Thread Hervé BOUTEMY
+1

Hervé

Le mercredi 22 février 2012 14:50:55 Dennis Lundberg a écrit :
 Hi,
 
 We solved 1 issue:
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=H
 tmlversion=18335
 
 There are still a couple of issues left in JIRA:
 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127sta
 tus=1
 
 Staging repo:
 https://repository.apache.org/content/repositories/maven-007/
 
 Staging site:
 http://maven.apache.org/plugins/maven-checkstyle-plugin-2.9.1/
 
 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html
 
 Vote open for 72 hours.
 
 [ ] +1
 [ ] +0
 [ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Functional distinction between install and deploy operations

2012-02-24 Thread Chas Emerick

On Feb 23, 2012, at 8:35 PM, Chris Graham wrote:

 I can imagine that many of the Maven-interoperability issues that ivy 
 had/has (I've not been near it for some years) are attributable to the lack 
 of a usable specification of repository layouts, operational semantics, etc.
 
 I think that you've found the real issue there. It's the same one as Ivy has.
 
 What I think you have, is an 'impedance mismatch' between two systems,
 one with a well defined lifecycle and structure (maven) and one
 without (Ant/Ivy).

I think the lack of clear answers on this thread demonstrates that Maven 
_doesn't_ have a well-defined structure and semantics (talking here about the 
repository, operations on it, etc., not the modes and knobs of `mvn`).  If it 
did, and it was documented, then Ivy's interoperability with Maven repositories 
would be on par with `mvn`.

- Chas
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org