[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [aspectj-dev] Binary Weaving: Class-Path JAR Manifest Attribute
|
> -----Original Message-----
> From: aspectj-dev-admin@xxxxxxxxxxx [mailto:aspectj-dev-admin@xxxxxxxxxxx]
> On Behalf Of Wes Isberg
> Sent: Tuesday, November 11, 2003 9:47 PM
> To: aspectj-dev@xxxxxxxxxxx
> Subject: Re: [aspectj-dev] Binary Weaving: Class-Path JAR Manifest
> Attribute
>
> Mik: To amplify what Matthew might have meant by his title:
> This might also be among the options that make sense only or primarily
> to a binary weaver. I believe the weaver can work without the
> compiler, and that we haven't surfaced an official API for it. This
> option might be one to restrict to the weaver API, and pull into
> the compiler only as needed. You might pull it in when editing
> the classpath in the project, with a checkbox for generating
> additional entries for those referenced in input jar manifests.
...
Yup. Having it available for the weaver only doesn't trigger the concerns I
had for surfacing it in the IDE's compiler.
> However, I don't understand this:
>
> >>Doing this would also require a change to the current resource copying
> >>behaviour.
>
> Don't we now "handle" manifest collisions like other resource
> collisions, with first-wins and warn thereafter?
You might want special behavior in this case, e.g. to concatenate the paths
specified by the manifest of each injars into the Class-Path attribute of
the outjar.
Mik
--
http://kerstens.org/mik