> -Markus
>
> -Ursprüngliche Nachricht-
> Von: Elliotte Rusty Harold [mailto:elh...@ibiblio.org]
> Gesendet: Montag, 13. April 2020 19:02
> An: Maven Developers List
> Betreff: Re: Maven intern projects
>
> On Mon, Apr 13, 2020 at 11:50 AM Robert Scholte w
> -Original Message-
> From: Markus KARG
> Sent: Monday, April 13, 2020 1:44 PM
>
> What users finally expect is to have multirelease JAR building being a Maven
> native
> functionality. This means, it should be as-easy-as putting code in these
> folders:
>
> src/main/java/9/
>
On Mon, Apr 13, 2020 at 11:50 AM Robert Scholte wrote:
>
> Just to be clear: Multirelease jars is a JDK 9+ feature. With Maven it is
> possible to make them, to test them and to run them. But they are pretty hard
> to maintain.
> So I would prefer NOT to try make Multirelease Jars of our
Just to be clear: Multirelease jars is a JDK 9+ feature. With Maven it is
possible to make them, to test them and to run them. But they are pretty hard
to maintain.
So I would prefer NOT to try make Multirelease Jars of our libraries, unless
there's a very good reason.
The next version of Maven
On Fri, Apr 10, 2020 at 1:17 PM Markus KARG wrote:
> Having said this, it would be a really great feature to get an easy-to-use
> solution for creating multi-version-JARs.
>
This is probably the best idea so far. (Google specifically does not
want interns working on refactoring or maintenance
Am 2020-04-10 um 16:12 schrieb Elliotte Rusty Harold:
Due to external developments, I am suddenly able to recruit, fund, and
manage as many as five interns, probably undergraduates, to work on
open source projects such as Maven and its plugins for 12 weeks this
summer.
My management chain has a
nice!
on Reproducible Builds for Maven, we're pretty finished:
- few plugins still need to support reproducible output: m-shade-p in vote,
remains m-war-p, Felix bundle:bundle
- on making our sub-projects builds reproducible [1], only 2 sub-project are
not yet finished, waiting for previous
My wishlist: Maven Central web (https://search.maven.org/) to show the
health of artifacts. For example, the health includes how much their
dependencies are up-to-date, presence of license element in pom.xml, and so
on.
I recently found pub.dev (Dart/Flutter repo system) has such tab for every
