@Karl
off-topic but still related to maven-shared-utils, please see my question
https://github.com/apache/maven-shared/commit/29737d2cc1a168905705c81dcd3e213091efc551
On Thu, Oct 1, 2015 at 10:17 PM, Karl Heinz Marbaise-3 [via Maven] <
ml-node+s40175n5846713...@n5.nabble.com> wrote:
> Hi,
>
> jus
Hi,
just a question on understanding...
Can someone explain me why maven-shared-utils produces a shaded artifact
instead a usual jar file ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apa
> The current version of buildnumber-maven-plugin results in a buildnumber
> "null" instead of the actual SHA1. I am not sure why this is, the current
> master version works.
>
> I provided a new integration test to ensure Git is always checked:
>
> https://github.com/mojohaus/buildnumber-maven-p
The current version of buildnumber-maven-plugin results in a buildnumber
"null" instead of the actual SHA1. I am not sure why this is, the current
master version works.
I provided a new integration test to ensure Git is always checked:
https://github.com/mojohaus/buildnumber-maven-plugin/pull/19
Github user romani closed the pull request at:
https://github.com/apache/maven-plugins/pull/63
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
Joining this discussion...
Based on my experience when I joined, Maven core and maven plugins are
different beasts. Sure, if you understand the inner parts of Maven core it
is easier to understand plugins, but core also depends on many different
libraries which handle different aspects of the logi
Hi Larry,
it would be nice if you start working (or trying to sometimes it's hard
i know this) on a particular issue that you might give a note here on
the dev list so we know where you are working on so this will prevent
duplicate work...just to prevent an other one to work on the same
issue
