Lennart,
Your attachments are missing.
/Anders
On Thu, Dec 6, 2012 at 11:49 PM, Lennart Jörelid
wrote:
> Hello all,
>
> I have a few reactors where two separate parent poms exist; one parent is
> used exclusively for reactor projects [with pom] and
> the other parent is exclusively used for al
> I'm interested to help working on adding a metadata to enable slf4j
> visibility
> from a plugin: by default, slf4j is not visible, plugins are expected to
> use
> plugin-api's Log. But if the plugin wants to use core's slf4j, he would be
> able to add an annotation in the goal requiring shared c
On Dec 6, 2012, at 4:34 PM, Hervé BOUTEMY wrote:
> I'm interested to help working on adding a metadata to enable slf4j
> visibility
> from a plugin: by default, slf4j is not visible, plugins are expected to use
> plugin-api's Log. But if the plugin wants to use core's slf4j, he would be
> ab
I'm interested to help working on adding a metadata to enable slf4j visibility
from a plugin: by default, slf4j is not visible, plugins are expected to use
plugin-api's Log. But if the plugin wants to use core's slf4j, he would be
able to add an annotation in the goal requiring shared core slf4j
Hello all,
I have a few reactors where two separate parent poms exist; one parent is
used exclusively for reactor projects [with pom] and
the other parent is exclusively used for all other projects [with
... something not pom ...].
The build itself works as expected - but the *mvn site:stage* bui
