Hi Hervé,
I'm there on Saturday and Sunday...
Kind regards
Karl Heinz Marbaise
On 1/18/16 12:52 AM, Hervé BOUTEMY wrote:
Hi,
Last year, a few Maven devs met at FOSDEM, and this was great.
This year, who will be there?
I will be there on sunday.
Regards,
Hervé
https://cwiki.apache.org/con
Hi,
Last year, a few Maven devs met at FOSDEM, and this was great.
This year, who will be there?
I will be there on sunday.
Regards,
Hervé
https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2016
-
To unsubscribe, e-ma
Hi Robert,
I fixed the transitive artifact resolution. See the branch 3.0-rc1.
The only remaining to fix is Java packages relocation of *-shared artifacts
in maven-surefire-common.
Cheers
Tibor
On Sun, Jan 17, 2016 at 8:09 PM, Tibor Digana
wrote:
> I used transformer
>
>
>implementation="
I used transformer
which threw exception in maven-surefire-plugin runtime :
*[WARNING] Error injecting:
org.apache.maven.surefire.shade.org.apache.maven.shared.artifact.resolve.internal.DefaultArtifactResolverjava.lang.TypeNotPresentException:
Type
org.apache.maven.surefire.shade.org.a
Hi Tibor,
I actually had the same question about the other dependencies which are
shaded.
Based on the exception I would expect that you need a transformer[1],
based on the excepted I would say the PluginXmlResourceTransformer
(otherwise ComponentsXmlResourceTransformer).
The other option i
Hi Robert,
A new problem with maven-artifact-transfer.
Should we really shade it?
Not able to inject ArtifactResolver as it seems:
[INFO] --- maven-surefire-plugin:2.19.2-SNAPSHOT:test (default-test) @
child ---
[WARNING] Error injecting: org.apache.maven.plugin.surefire.SurefirePlugin
com.google
Hi,
check SHA1, Tested with the following Maven versions:
3.0.5, 3.1.1, 3.2.5, 3.3.9...without any issue.
So +1 from me...
Kind regards
Karl Heinz Marbaise
On 1/17/16 12:03 AM, Andreas Gudian wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330