I totally agree. This feels like a royally bad idea that is totally counter to
the idea for slim runtime and fast startup times. I would much rather have some
additional info somewhere in the archive that documents used bytecode,
supported runtime and things like that.
On the Maven side it
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Dennis Lundberg, Jason van Zyl, Hervé Boutemy
I will promote the artifacts to the central repo.
Thanks to all the voters!
On Sun, Mar 15, 2015 at 8:14 PM, Dennis Lundberg denn...@apache.org wrote:
Hi,
We
This can be a candidate of Delta SNAPSHOT JAR.
Not much advantages with release version JAR, however useful in Release
Candidates RCx.
--
View this message in context:
http://maven.40175.n5.nabble.com/DISCUSSION-JEP-238-Multi-Version-JAR-Files-tp5829748p5829837.html
Sent from the Maven
Hey all,
A question on life cycle participants - it would seem that they don't appear to
be enabled when called from a child module/reactor build.
I just added the invoker-plugin to the `tiles-maven-plugin` to add some real
usage cases/tests [1] and it seems that when the child module is run
Hi folks,
I'd like to feel your temperature wrt the following improvement I would
like to make to Maven before I start working on it.
*== Artifact-based Reposi**tories* ==
In Tycho we have these constructs:
Put a test project somewhere and I'm happy to look, I need something I can
debug through to try and help.
There are several tests for participants in the ITs so I think they are all
right. And I don't believe we broke anything along the way to 3.3.1 either.
On Mar 20, 2015, at 9:49 PM, Mark
The Maven team is pleased to announce the release of the Apache Maven
Checkstyle Plugin, version 2.15
Generates a report on violations of code style and optionally fails the build
if violations are detected.
http://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the
On 21 Mar 2015, at 15:23, Jason van Zyl wrote:
Put a test project somewhere and I'm happy to look, I need something I can
debug through to try and help.
An extracted test project using the current version of the plugin can be
downloaded from:
It looks good to me
On Thu, Mar 19, 2015 at 8:02 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
nothing more to improve ?
Kind regards
Karl Heinz Marbaise
On 3/18/15 10:21 PM, Karl Heinz Marbaise wrote:
Hi,
i have incorporated the suggestions/ideas/improvements
Hi Hervé,
what do you think of the following first patch ? I haven't generated the
corresponding html yet, just throwing some ideas..
Regards,
Jon
Index: pom.apt
===
--- pom.apt (révision 1668105)
+++ pom.apt (copie de
GitHub user rtack opened a pull request:
https://github.com/apache/maven-archetype/pull/4
grammar fix in exception message
The current project does not built an archetype -- should be either
The current project does not build an archetype or The current project has
not built an
I think a use-case that supports the JEP would be the Spring Framework.
They are typically supporting a couple versions of Java at once *in one
release* and they have some utility code to access the latest features *if*
they are available in the running JRE. However, to do that, they use class
I'm just reading http://openjdk.java.net/jeps/238 and I encourage everyone else
to as well. Mark talked about this at EclipseCon and I'm not sure what this
buys you. I can see the goals in the JEP but it isn't really clear about the
problem this JEP is trying to solve. I will pop on the mailing
I agree on the feels wrong.
I don't think it will become that much heavier, assuming most of the time
you don't need multi-version classes in an archive. Now you know for sure
that a number of classes won't be used, but in general you always get
overhead from classes in jars which aren't
Also have a look at
http://cr.openjdk.java.net/~psandoz/jdk9/MultiVersionJar-8u60-9-design.md
it looks more complete and has some additional usecases
Robert
Op Fri, 20 Mar 2015 17:24:08 +0100 schreef Jason van Zyl ja...@takari.io:
I'm just reading http://openjdk.java.net/jeps/238 and I
Dear Maven Users,
based on the End of Life of Maven 2.2.1 (a year ago) now the time has
come to make the final releases of Apache Maven Plugins which support
Maven 2.X.
If you continue to use Maven 2.2.1 or earlier you have to be aware of
using an completely unsupported Maven version as well as
16 matches
Mail list logo
