The typical pattern used for this is an artefact filter applied to the
configuration of the plugin, rather than information on the dependencies (like
what the dependency plugin goals use). That was a feature of Maven 1 that we
rejected upfront.
In my experience, it's actually less verbose since
I really like the success-icon[1], but I have my doubts about the rest.
The style of the 'I' of info is completely different compared to both the
clouds.
And the vertical alignment between those clouds looks strange because of the
difference in height.
It's just my opinion, I'll try to se
I just gave a try, looks like if the skin already has images, they
won't be replaced.
I just replaced the RSS icon, going to update the report
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Mon, Nov
Hi Robert!
sure, I just published a sample on my personal ASF space[1] applying
the skin on a commons-sandbox component.
I wonder if I could replace the RSS icon as well, but I guess the
checkstyle plugin brought its iconset...
Please let me know what you think about it!
TIA, all the best,
Simo
[1
Maybe a little bit more information :) We need this information just
for the build of the project containing this information. It's read by
a custom plugin. So even if the information would not end up in the
maven repository, we're fine.
Carsten
2011/11/7 Carsten Ziegeler :
> Hi,
>
> in Apache Sl
Hi Simone,
could you add an example of a checkstyle-page to see how those icons would look
like?
-Robert
> Date: Sun, 6 Nov 2011 22:18:42 +0100
> Subject: Fluido skin (almost?) ready to be voted
> From: simonetrip...@apache.org
> To: dev@maven.ap
Am 07.11.2011 16:31 schrieb "Jesse Glick" :
> I do not think Phase should be an enum, just a list of String constants -
you are permitted to define alternative lifecycles, right?
>
New lifecycles: yes, possible (i. e.: which action to perform in which
phase).
New lifecycle *phases*: no, not to my
Hi,
in Apache Sling we have the need to add additional information to a
dependency in a pom, basically it's just an xml attribute, like:
Now, with a little bit of hacking we could get this working in our
plugin be parsing or converting the pom xml file ourselves (we don't
need pom inheritance o
There is code here which I will propose as a candidate of part of what I call
Tesla. I hope that this can be integrated into Maven:
https://github.com/etesla/tesla-plugin-api
On Nov 7, 2011, at 10:30 AM, Jesse Glick wrote:
> On 11/04/2011 07:13 AM, Stephen Connolly wrote:
>> you generate a clas
You guys decided you wanted to wait so let's just wait. I didn't think it would
take this long to get through either but it is what it is. So realistically
we're looking at 3.0.4 in 4 weeks.
On Nov 7, 2011, at 9:24 AM, John Casey wrote:
> On 11/4/11 7:28 AM, Alexander Kurtakov wrote:
>> On 13:0
On 11/04/2011 07:13 AM, Stephen Connolly wrote:
you generate a class that extends
AbstractMojo, has the required injection fields for all the
@parameters and has an execute method that passes through all the
injection fields and then invokes the required method.
By the way this (as well as Help
On 11/4/11 7:28 AM, Alexander Kurtakov wrote:
> On 13:04:06 Friday 04 November 2011 Stephen Connolly wrote:
>> On 4 November 2011 10:22, Benjamin Bentmann
> wrote:
>>> David Jencks wrote:
Another month went by any progress?
>>>
>>> The sources were checked into git according to parallel
12 matches
Mail list logo
