d just need to be a common dependency. reporting-api definitely
> is, but you could easily create a new library for it (and that probably
> makes more sense).
>
> The component definition goes in the same JAR as the class.
>
> - Brett
>
> Mauro Botelho wrote:
>
n dependency of all the plugins
> using this.
>
> - Brett
>
>
>
> Mauro Botelho wrote:
> > I'd like to propose a solution for this. Here's an attempt to describe
> > what I was able to put together, but I'd like the opinion of the
> > comm
I'd like to propose a solution for this. Here's an attempt to describe
what I was able to put together, but I'd like the opinion of the
community before I get too deep :)
First of all, I'm following the approach that has been documented in the
wiki so far. The main difference is that instead o
now where to start :)
Mauro
Brett Porter wrote:
Mauro Botelho wrote:
Did anybody put any more work on this?
No, not yet. I'm thinking of spending some time on it soon.
I started to look at Brett's suggestions, but could not link the names
to the classes.
Looking at some of
Did anybody put any more work on this?
I started to look at Brett's suggestions, but could not link the names
to the classes.
Looking at some of the plugins (Surefire, checkstyle and pmd) I think
that when Brett mentions that we have the parsers, I think he's talking
about the PmdReportListe
Add ability to fail the build on test errors
Key: MPTEST-58
URL: http://jira.codehaus.org/browse/MPTEST-58
Project: maven-test-plugin
Type: Improvement
Versions: 1.8
Reporter: Mauro Botelho
Priority: Trivial
.
Does it make sense?
Mauro
P.S.: Should I move this thread to the users mailing list?
Brett Porter wrote:
Sorry, I don't understand your question here?
Mauro Botelho wrote:
It makes sense, but in what cases would that code be activated then?
It makes sense, but in what cases would that code be activated then?
Mauro
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Does anybody have an easy way of creating a single eclipse project for
the whole m2 code base?
Looking at the source code for the eclipse plug in, it looks like it
would do something like that in reactor mode, but when I do m2
eclipse:eclipse in the top level directory, I get multiple projects
Vincent,
I have something in place today that has a very similar design to what
you have. The only thing is that I decided to implement one single
parser, the dashboard-single report parser :)
I was somehow expecting that the reporting api would provide us with a
hook where that kind of info
[ http://jira.codehaus.org/browse/MNG-411?page=comments#action_40558 ]
Mauro Botelho commented on MNG-411:
---
Could we have all the archives in one single column? In other words merge the
"archive" and "other archives" column int
How would that behave when you have multiple levels of inheritance?
Just assume a flat directory structure?
Mauro
On 5/12/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> A lot of values in the POM, when inherited, need to be extended to add
> the additional path to it. Things like URL, SCM
I am working on the eclipse plugin again, and while trying to run some
tests, I noticed that when running the plugin from the command line I
got the expected behavior, but not when running the unit test.
What I am trying to do is to create a monster eclipse project with all
the modules included, s
13 matches
Mail list logo
