On 11/07/2006 3:14 PM, Vincent Massol wrote:
One solution would be to create a profile for the main lifecycle and another
one for the clover lifecycle but that's not very handy for end users I
think. I'll try experimenting with this later on but I think it would only
be a hack and not a proper so
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 11 juillet 2006 03:22
> To: Maven Developers List
> Subject: Re: General issue with clover plugin requiring creative
> thinking...
>
> Isn't the problem that the clovered part is meant to be a separate,
> f
Isn't the problem that the clovered part is meant to be a separate,
forked, lifecycle - but the PMD goals (etc) are still bound when they
are only wanted on the main lifecycle?
- Brett
On 11/07/2006 6:33 AM, Mike Perham wrote:
I think Maven 2.1 needs to differentiate between the original proj
There shouldn't be any reason you can't test as POJOs now (as long as
you add getters and setters). I was initially reluctant about the extent
of using the testing harness for testing - they do seem more like
integration tests, but it has really been used as an assistant for
populating values (
This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name some,
are rather empty. The jar plugin just extracts information from the
MavenProject, giving it to maven-archiver (plexus-archiver under water),
and later updates the
On Tue, 11 Jul 2006, Carlos Sanchez wrote:
Indeed.
The mojo's should be as lightweight as possible - just the glue between
maven and the actual actions it performs.
This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name so
http://docs.codehaus.org/display/CONTINUUM/Security
Please take a look and provide feedback on the semantics of what to
secure and to what level.
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
I think that's defenitely what we look for, pojos wrapped in mojos, or
at least mojos that can be used as pojos as much as possible
On 7/10/06, Mike Perham <[EMAIL PROTECTED]> wrote:
I would like to see plugins be made a little more independent from
Maven. You know how J2EE code is difficult to
I would like to see plugins be made a little more independent from
Maven. You know how J2EE code is difficult to test due to the need for
a container? Well, Maven is the container for plugins and that need for
a container makes it more difficult than necessary to test and reuse
plugins. There's
Hi,
in the last weeks I have thought a little bit about Maven plugins. The
initial question was my desire to reuse another plugin.
There are good reasons for reusing plugins. As an example, think of a
plugin, which creates a jar file. Might be the retro* plugins or
something like that.I would th
The maven-source-plugin is ignoring the includes/excludes sections of
resources. This issue was logged (
http://jira.codehaus.org/browse/MSOURCES-6). I proposed a patch for this
issue and was wondering if the developers responsible for this plugin would
be able to take a look at it.
Thanks,
Mic
I think Maven 2.1 needs to differentiate between the original project
sources and "currently effective" generated sources. Report plugins act
on the former, build plugins on the latter. I don't know that it is
possible to solve this problem in 2.0.x.
-Original Message-
From: Vincent Mass
> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: lundi 10 juillet 2006 21:57
> To: Maven Developers List
> Subject: RE: General issue with clover plugin requiring creative
> thinking...
>
> Please correct me if I'm misunderstanding something (since it's been
> m
Please correct me if I'm misunderstanding something (since it's been months
since I looked at clover) but isn't the heart of the problem that you add the
clover source to the project sources? I don't think you should do this. It's
not technically part of the project source and source reports s
Hi,
I have found an important issue with the clover plugin use case. Clover
instrument sources. The clover plugin redirect maven sources to point to the
clovered sources. This is all fine for most plugins as they'll now operate
on the modified sources (compile, jar, install, deploy, etc).
However
+1
On 7/10/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Does it? I just thought it was 3 votes. Can I get some love, PMC
members?
-Original Message-
From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 9:05 AM
To: Maven Developers List
Subject: Re: [result] re
Does it? I just thought it was 3 votes. Can I get some love, PMC
members?
-Original Message-
From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 9:05 AM
To: Maven Developers List
Subject: Re: [result] release maven-pmd-plugin 2.1
Doesn't a release need 3 bi
Doesn't a release need 3 binding +1 votes ?
Mvgr,
Martin
Mike Perham wrote:
Binding +1: Mike, Brett
Non-Binding +1: Fabrice
I will release it today and update the site docs.
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 2:31 PM
To: M
Binding +1: Mike, Brett
Non-Binding +1: Fabrice
I will release it today and update the site docs.
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 2:31 PM
To: Maven Developers List
Subject: [vote] release maven-pmd-plugin 2.1
I think PMD is i
Hi Rinku,
There is an open issue for it.. please see
http://jira.codehaus.org/browse/MNG-1712
regards,
allan
Rinku wrote:
Hi,
I have meant to ask this everytime I run into similar error with wagon
providers.
Why is it that the wagon provider lib needs to be copied to under M2
Home? Shou
Hi,
I have meant to ask this everytime I run into similar error with wagon
providers.
Why is it that the wagon provider lib needs to be copied to under M2
Home? Shouldn't this be downloaded to local repo and used from there? Is
it something to do with Classworlds' realms.
Cheers,
Rahul
--
21 matches
Mail list logo
