+1!
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 08, 2006 12:27 PM
To: 'Maven Developers List'
Subject: [VOTE] Release Clover plugin 2.1
Hi,
I've made quite a lot of improvements to the Clover plugin and I'd like to
release it. It's all the m
A few issues:
1) The howto doc still has not been updated to explain the check goals.
2) I'd prefer the check goal to be named pmd-check for symmetry with the
cpd-check goal.
3) I'd prefer the check violation statement to say "You have XX PMD|CPD
violations" so it is a little more obvious why the
Dennis Lundberg wrote:
Hello
I've been doing some work on the Maven Confluence wiki lately. There is
one thing that I am not allowed to do though and that is remove pages.
There are currently 4 orphaned pages [1] that are the results of people
trying to learn the wiki.
It would be nice if s
Hello
I've been doing some work on the Maven Confluence wiki lately. There is
one thing that I am not allowed to do though and that is remove pages.
There are currently 4 orphaned pages [1] that are the results of people
trying to learn the wiki.
It would be nice if someone with administrati
I should get to it shortly. I've been traveling a ton in the past 3
weeks.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 08, 2006 10:20 AM
To: Maven Developers List
Subject: dependency plugin?
Brian,
Any news on importing this plugin?
- Brett
-
I have just read through the docs that Alexandre has written and there
is good stuff in there. The content is presented in a fashion similar to
"The Java Tutorial" with trails. One trail for each level of knowledge:
beginner, intermediate, etc. This is a nice way to do it and I think
that this
+1
On 4/8/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've made quite a lot of improvements to the Clover plugin and I'd like to
> release it. It's all the more urgent that the current released clover
> plugin
> has its Clover license expired.
>
> Release Notes - Maven 2.x Clover Plu
+1
Vincent Massol wrote:
Hi,
I've made quite a lot of improvements to the Clover plugin and I'd like to
release it. It's all the more urgent that the current released clover plugin
has its Clover license expired.
Release Notes - Maven 2.x Clover Plugin - Version 2.1
** Bug
* [MCLOVER-7] -
Hi,
I've made quite a lot of improvements to the Clover plugin and I'd like to
release it. It's all the more urgent that the current released clover plugin
has its Clover license expired.
Release Notes - Maven 2.x Clover Plugin - Version 2.1
** Bug
* [MCLOVER-7] - "mvn clover:report" generat
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: samedi 8 avril 2006 16:15
> To: Maven Developers List
> Subject: Re: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> It doesn't sound right, classifier is the right one. Relying on a
Does it look ok now?
Mike Perham wrote:
> -1
>
> The PMD and CPD check goals are not documented at all. I just checked
> in a simple update to howto.apt which adds some check details. I would
> like to see this fleshed out a little.
>
> I would also like to see http://jira.codehaus.org/browse/
Has anyone had a chance to look at the wiki content? It seems to be
coming along, but I'm too pressed for time right now...
Are any docs able to be reintegrated back into the Maven site?
- Brett
Alexandre Poitras wrote:
> Thank Brett, I'll do my best.
> In the first part, where I explain basic c
Brian,
Any news on importing this plugin?
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
It doesn't sound right, classifier is the right one. Relying on a
packaging plugin having the 'classifier' configuration element is too
fragile in either case, even if they all had it.
So if I understand, you are forking the lifecycle (should it be package
instead of install?), passing in the conf
Ok here's some feedback on this.
I've succeeded in implementing it. However I've found that not all plugins
support classifiers (the ear plugin does not for example). As a consequence
some main artifacts are generated with clovered stuff in them. That's wrong
as clovered stuff should not be mixed
I actually haven't played with the combined webapp yet, just the initial
prototype I put together and the individual components. I'm not sure if
the indexing was wired up automatically.
There is an indexing CLI you might be able to use in the -application
module to create the index in the reposito
Leave out the executions on the test phase. See the cobertura plugin
instead - its closer to EMMA (I believe).
- Brett
Andreas Rudolf wrote:
> Hi,
>
> I develop a plugin for emma and have a question about lifecycle
> configuration.
>
> I setup a custom lifecycle "emma" (just like the clover pl
Jason van Zyl wrote:
> Brett Porter wrote:
>> Jason,
>>
>> Does it work with 2.0.1? Doesn't it require 2.1-SNAPSHOT to merge
>> components.xml?
>
> I used what I knew was released for know. I'm twiddling the bootstrap as
> you can't start from scratch and have it work using an snapshot. But
> yes,
(catching up on mail).
This is certainly something I'd like to revisit in 2.1 or 2.2, as well
as i18n of the app itself. Thanks for filing those issues to look at and
for helping out.
- Brett
Trustin Lee wrote:
> Hello everyone,
>
> First off, I'd like to thank Maven team for developing this gr
package to type mappings are predefined in maven-artifact's
components.xml, however any plugin can provide it's own through the
extensions mechanism, which I believe you were using in the other rar
example. The first part of your email is completely correct in how it works.
Cheers,
Brett
Jian.Wu
Did you first do mvn install on the first project? Where did it end up?
I can see this will probably be a limitation - it may not be able to
associate the built artifact of the first project with the latter in the
reactor, but I'm not sure. Still, it should definitely work if you
install it first
Hi Vincent,
Vincent Siveton wrote:
> Brett,
>
> I took time to test your amazing stuff. Very nice feature :) Thanks!
>
> You've probably know these but just in case they can help you:
> - error 404 for subprojects links from a multi project case:
> http://localhost:8080/index.html
> Clicks on a
Not at present, but its anticipated for the future.
Cheers,
Brett
Adam Leggett wrote:
> Thanks Brett,
>
> The checkstyle individual mojo based approach seems more flexible.
> Having thought about my requirement some more i have a further question.
> Bascially what i want to do is create a 'bui
The "correct" version is the exploded form (for backwards
compatibility). I agree the flat version is preferred, but that's not
how it is in the current release.
- Brett
Jacek Laskowski wrote:
> Hi,
>
> Could anyone explain what version is really correct. I took a look at
> PropertiesConverter f
The working directory is always the execution root so that it behaves
consistently between forking and non-forking. user.dir is always set to
that directory.
- Brett
anita kulshreshtha wrote:
> Hi,
> I have a project with the following directory
> structure :
> --myproject
> --modules
>
Good eye - fixed. Thanks!
- Brett
Allison, Bob wrote:
> I was looking at the commit of r386543 which added a couple parameters
> to the javadoc plugin for selecting classes based on package. The
> Javadoc for the two parameters reads:
>/**
> * Specifies the source path where the subpacka
fixed (MONE-1)
Vincent Massol wrote:
> Hi,
>
> There's no JIRA for the maven one plugin so I'm posting here for now (I've
> opened a MPA issue for creating the maven one plugin jira project).
>
> When I run "mvn install" in my maven 1 project I get a valid jar. However
> when it's run as part of
I've no objection to reviewing provided in 2.1 - please make sure it is
in JIRA and/or the wiki roadmap. I'm not exactly sure if I have reasons
not to make it transitive (I don't think it will break things), it just
doesn't sit well with the view of what provided means - the dependency
shouldn't kn
FYI: we have the same problem with M1 plugins. We might need to consider any
solution for m1 as well.
Stéphane
On 4/1/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I recently noticed a lot of duplicated effort in order to implement
> similar things in the eclipse and idea plugins. Do
Pfiou, I am bit tired and I read your mail way too fast.
You can't specify dependency injections parameters in your ComplexObject.
Those tags are only allowed in your Mojo.
s/
On 4/8/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> Hi Christophe,
>
> Good to see that you're using maven in your
Hi Christophe,
Good to see that you're using maven in your organisation.
Yes, it is possible to map complex types in Mojo. However, you need to pay
attention to the following:
- The ComplexObject needs to be public with a default public constructor and
needs to be in the same package as your Moj
Too late but +1 anyway
On 3/31/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Just giving all devs a heads up that I discussed adding Milos as a
> committer on Maven for his work on the embedder and the Netbeans plugin.
> There were enough +1s on the PMC list to bring Milos in but want
32 matches
Mail list logo
