Hi Jan,
See also https://github.com/apache/maven-shade-plugin/pull/14 and MSHADE-259
I stalled on it because it appears to be a lot of work to create unit tests for
maven plugins — and there weren’t examples to follow in the shade plugin.
That said, I’m not sure what I did is the right way to fix
pon., 2 gru 2019 o 09:52 Jochen Wiedmann
napisał(a):
> On Thu, Nov 28, 2019 at 9:46 PM Slawomir Jaranowski
> wrote:
>
> > I'm writing some maven plugins - some for fun and with public code but
> more
> > maven plugins I'm writing for job in my company.
> >
> > Maven from version 3.1.x use slf4j
Hi Jochen,
Would you like to help in writing such documentation ?
We have a black page currently, just the default website auto generated
for every plugin
Enrico
Il giorno lun 2 dic 2019 alle ore 12:49 Jochen Wiedmann <
jochen.wiedm...@gmail.com> ha scritto:
> On Mon, Nov 11, 2019 at 11:02 PM
On Mon, Nov 11, 2019 at 11:02 PM Robert Scholte wrote:
>
> I'd say start a release. As it is based on JSR223 is should be very easy for
> any scripting language to be supported.
Before a release, I'd recommend to have at least *some* documentation.
Jochen
--
On Thu, Nov 28, 2019 at 9:46 PM Slawomir Jaranowski
wrote:
> I'm writing some maven plugins - some for fun and with public code but more
> maven plugins I'm writing for job in my company.
>
> Maven from version 3.1.x use slf4j for logging.
>
> But plugin api still use simple logging api
> org.apa
Hi Hervé,
testing remove-scm-tag at our site (we use a customized version of
maven-release where I already merged the code), i found this:
https://issues.apache.org/jira/browse/MRELEASE-1034
This is something between blocker and critical and i would like to have
it in 3.0.0-M1.
When i prov
