Thanks Karl for the response.
I just logged an issue as follows. It was caused by the bad packaging (it's
'pom' instead of 'jar'). Would you comment on it? Thanks.
https://issues.apache.org/jira/browse/MSHADE-198
Regards,
Kai
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba
Hi,
just simply use
client-api-all
..
Kind regards
Karl Heinz Marbaise
On 7/13/15 1:02 AM, Zheng, Kai wrote:
Hi experts,
With the following, it generates a uber-jar, but the generated jar file name
isn't expected, being client-api-all.jar.pom. Note the content is correct,
containing classes
Hi experts,
With the following, it generates a uber-jar, but the generated jar file name
isn't expected, being client-api-all.jar.pom. Note the content is correct,
containing classes files, not any POM stuff.
Would anyone help? Thanks a lot.
org.apache.maven.plugins
Yes, it's to do with the forked execution. I've made a test case and
created https://issues.apache.org/jira/browse/MRELEASE-915.
I haven't tried the yet, I will in a moment and
annotate the JIRA.
On Sun, Jul 12, 2015 at 1:08 PM, Benson Margulies wrote:
> On Sat, Jul 11, 2015 at 5:04 AM, Robert
On Sat, Jul 11, 2015 at 5:04 AM, Robert Scholte wrote:
> You know that release:perform doesn't do any magic. It would be the same as:
> cd target/checkout
> mvn deploy (or mvn deploy site-deploy)
>
> If this works as expected (without failures), then it looks like something
> is leaking.
> Could y
