Le jeudi 9 juillet 2015 09:48:13 Tibor Digana a écrit :
> Nice project indeed.
> Maybe only JRE has the benefit from multi-version JAR, but I cannot imaging
> this feature in ordinal projects.
+1
currently, there are not so much projects that produce a different artifact for
different JREs, but th
that's it: I couldn't find this in assembly descriptor configuration
fix merged
thank you Robert
Le jeudi 9 juillet 2015 19:15:29 Robert Scholte a écrit :
>
>
> /META-INF/**
>
>
> ?
>
> Robert
>
> Op Thu, 09 Jul 2015 01:07:52 +0200 schre
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/56#issuecomment-120199784
I'm generally against changing anything to do with resolving strategies and
it has the potential for breaking everything because it's not just what you
might use, but what
GitHub user barthel opened a pull request:
https://github.com/apache/maven/pull/56
MNG-3092: strategy based version resolver
These changes replaces the default version range resolver with a strategy
based version range resolver.
You can merge this pull request into a Git repository
/META-INF/**
?
Robert
Op Thu, 09 Jul 2015 01:07:52 +0200 schreef Hervé BOUTEMY
:
Hi,
In april, we had a discussion about Multi-Version JAR Files.
Since then, we worked to create a sample project built with Maven, to
see how
Maven confi
Nice project indeed.
Maybe only JRE has the benefit from multi-version JAR, but I cannot imaging
this feature in ordinal projects. Who has benefit from writing the code
three times if API of module matters. Maybe performance will be different
only.
On Thu, Jul 9, 2015 at 1:08 AM, Hervé BOUTEMY [vi
