Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
From: =?UTF-8?Q?Jan_Mat=C3=A8rne_=28jhm=29?= <apache@materne.de>
To: "'Ant Developers List'" <dev@ant.apache.org>
References: <87mvj6h91c.fsf@v45346.1blu.de>	<003901d21101$270a4670$751ed350$@de> <877fa97bld.fsf@v45346.1blu.de>
In-Reply-To: <877fa97bld.fsf@v45346.1blu.de>
Subject: AW: Multi-Release JARs
Date: Wed, 21 Sep 2016 14:08:15 +0200
Message-ID: <002e01d21400$d596c8b0$80c45a10$@de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdIRll7G4c1A9pQRQcqlw4y2MyCwlgCamCCQ
Content-Language: de
archived-at: Wed, 21 Sep 2016 12:08:35 -0000

I did a simple version using plain <jar> and <zipfileset>.

Jan

> -----Urspr=C3=BCngliche Nachricht-----
> Von: Stefan Bodewig [mailto:bodewig@apache.org]
> Gesendet: Sonntag, 18. September 2016 12:21
> An: dev@ant.apache.org
> Betreff: Re: Multi-Release JARs
>=20
> On 2016-09-17, Jan Mat=C3=A8rne (jhm) wrote:
>=20
> >> * Multi-Release JARs need a special manifest attribute, we should
> add an
> >>   attribute to the jar task that sets this.
>=20
> > I dont think so. We could set this flag by ourself if the
> > <new-kind-of-zipfileset> is set.
>=20
> Agreed. People who want to manually put together the jar would have to
> set the attribute themselves, then.
>=20
> > We discussed also the possibility of merging different jars.
> > Say you have a Java8 jar, a Java9 jar and a Java10 jar, you could
> > merge these into a multirelease jar.
>=20
> > Because of the different classfile versions, the common files of
> these
> > jars arent identical, so we cant find them easily. So the easy, but
> > not smart, solution ends in having the common files in every version
> branch of the jar.
>=20
> <jar ....>
>   <zipfileset src=3D"java8.jar"/>
>   <new-kind-of-zipfileset src=3D"java9.jar" version=3D"9"/>
>   ...
> </jar>
>=20
> could work that way. Likely would need to perform some fiddling WRT
> manifest attributes.
>=20
> > Another idea I had (for few minutes) is combining the jar'ing with
> the
> > compiling.
> >   <mrjar ...>
> >      <default targetdir=3D""><src-resource-collection></default>
> >      <version version=3D"9" targetdir=3D""><src-resource-collection>
> point
> > to
> > Java9 only </version>
> >      <version version=3D"10" =
targetdir=3D""><src-resource-collection>
> > point to Java10 only </version> <mrjar> would do three compile runs
> > now
> > * default: Java8
> > * version=3D9: Java9, with classes from previous runs on classpath
> > (havent thought about the identical names yet ... ;)
> > * version=3D10: Java10, ...
> > Finally create the MRJar.
>=20
> I guess configuration of the task will be quite longish but I can see
> how this would streamline hte process.
>=20
> Stefan
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org