is inside the class file.
Any idea?
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Mittwoch, 21. September 2016 19:03
> An: dev@ant.apache.org
> Betreff: Re: Multi-Release JARs
>
> On 2016-09-21, Jan Matèrne (jhm)
On 2016-09-21, Jan Matèrne (jhm) wrote:
> I did a simple version using plain and .
Nice.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
On Wed, Sep 21, 2016 at 2:08 PM, Jan Matèrne (jhm)
wrote:
> I did a simple version using plain and .
>
Nice and simple. Great test. I like it! --DD
I did a simple version using plain and .
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Sonntag, 18. September 2016 12:21
> An: dev@ant.apache.org
> Betreff: Re: Multi-Release JARs
>
> On 2016-09-17, Ja
On 2016-09-17, Jan Matèrne (jhm) wrote:
>> * Multi-Release JARs need a special manifest attribute, we should add an
>> attribute to the jar task that sets this.
> I dont think so. We could set this flag by ourself if the
> is set.
Agreed. People who want to manually pu
> * provide a new kind of that mimics the selection logic
> when reading from a jar. I.e.
>
>
>
> will include the contents and meta-data like timestamp of
> META-INF/versions/9/org/example/Foo.class using the name
> org/example/Foo.class
>
> * Multi-R
Hi all
Jan an I met at a local JUG last Thursday and quickly chatted about ways
Ant could support Multi-Release JARs.
For details see http://openjdk.java.net/jeps/238
In short the jar is a ZIP file as it has always been. It is possible to
bundle classes and resources targeting different Java
