Re: aspectj-dev Digest, Vol 4, Issue 11

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: aspectj-dev Digest, Vol 4, Issue 11

Mike Haladin
Hi Alex,

        A JVM option to turn on a JVM wide basis would be fantastic!  

If this would be available for JRE 1.4 and higher that would be great.

thanks!
Mike

P.S. Please let me know if this is going to be availabe with AJ 1.5 so I
can program accordingly.

> Message: 4
> Date: Thu, 16 Jun 2005 15:40:02 +0200
> From: Alexandre Vasseur <[hidden email]>
> Subject: Re: [aspectj-dev] Re: aspectj-dev Digest, Vol 4, Issue 5
> To: AspectJ developer discussions <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Mike
>
> I do get this classpath / manifest classpath issue.
> My claim is that this is tied to the WeavingURLClassLoader, but not to
> the upcoming more generic load time weaving support.
>
> Would use of a JVM option to turn on weaving on a JVM wide basis would
> be ok - thus not using the WeavingURLClassLoader ?
>
> Alex
>
> On 6/16/05, Mike Haladin <[hidden email]> wrote:
> > Hi Alex,
> >
> >         I am looking to weave existing applications in my project.  There are
> > 100s of jars and they all depend upon each other.  The dependencies are
> > contained within the Class-Path attribute of the manifest of each jar.
> >
> > I do not want to recurse through all the jars in the manifest of the
> > application I am starting.  I would like to just specify the application
> > jar in the aj.class.path and have the weaver find the jars I need from
> > the manifest class-paths.  This is how the default classloader works I
> > believe.
> >
> > Right now I am required to know every single jar that is required and
> > specify it with aj.class.path.
> >
> > example:
> >
> > aj.jar's Class-Path= ../mike.jar /opt/task.jar
> > mike.jar's Class-Path=/opt/james.jar
> > task.jar's Class-Path=
> > james.jar's Class-Path=
> >
> > currently aj.class.path would need be:
> > aj.jar:../mike.jar:/opt/task.jar:../james.jar
> >
> > I would like:
> >
> > aj.class.path=aj.jar
> >
> > or at least
> >
> > aj.class.path= aj.jar:../mike.jar:/opt/task.jar
> >
> > I would like this for 1.4 if possible as I do not know when we will move
> > to 1.5.
> >
> > then we would just supply the original list to the weavingURLCLassloader
> > and it will weave the jars it needs as well.
> >
> > thanks,
> > Mike
> >
> >

_______________________________________________
aspectj-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/aspectj-dev
Reply | Threaded
Open this post in threaded view
|

Re: Re: aspectj-dev Digest, Vol 4, Issue 11

Alexandre Vasseur
this should all surface in M3 (I ddon't say it will be of final
quality) ie mid July and it will thus definitely be in 1.5 final.

Alex

On 6/17/05, Mike Haladin <[hidden email]> wrote:

> Hi Alex,
>
>         A JVM option to turn on a JVM wide basis would be fantastic!
>
> If this would be available for JRE 1.4 and higher that would be great.
>
> thanks!
> Mike
>
> P.S. Please let me know if this is going to be availabe with AJ 1.5 so I
> can program accordingly.
>
> > Message: 4
> > Date: Thu, 16 Jun 2005 15:40:02 +0200
> > From: Alexandre Vasseur <[hidden email]>
> > Subject: Re: [aspectj-dev] Re: aspectj-dev Digest, Vol 4, Issue 5
> > To: AspectJ developer discussions <[hidden email]>
> > Message-ID: <[hidden email]>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Mike
> >
> > I do get this classpath / manifest classpath issue.
> > My claim is that this is tied to the WeavingURLClassLoader, but not to
> > the upcoming more generic load time weaving support.
> >
> > Would use of a JVM option to turn on weaving on a JVM wide basis would
> > be ok - thus not using the WeavingURLClassLoader ?
> >
> > Alex
> >
> > On 6/16/05, Mike Haladin <[hidden email]> wrote:
> > > Hi Alex,
> > >
> > >         I am looking to weave existing applications in my project.  There are
> > > 100s of jars and they all depend upon each other.  The dependencies are
> > > contained within the Class-Path attribute of the manifest of each jar.
> > >
> > > I do not want to recurse through all the jars in the manifest of the
> > > application I am starting.  I would like to just specify the application
> > > jar in the aj.class.path and have the weaver find the jars I need from
> > > the manifest class-paths.  This is how the default classloader works I
> > > believe.
> > >
> > > Right now I am required to know every single jar that is required and
> > > specify it with aj.class.path.
> > >
> > > example:
> > >
> > > aj.jar's Class-Path= ../mike.jar /opt/task.jar
> > > mike.jar's Class-Path=/opt/james.jar
> > > task.jar's Class-Path=
> > > james.jar's Class-Path=
> > >
> > > currently aj.class.path would need be:
> > > aj.jar:../mike.jar:/opt/task.jar:../james.jar
> > >
> > > I would like:
> > >
> > > aj.class.path=aj.jar
> > >
> > > or at least
> > >
> > > aj.class.path= aj.jar:../mike.jar:/opt/task.jar
> > >
> > > I would like this for 1.4 if possible as I do not know when we will move
> > > to 1.5.
> > >
> > > then we would just supply the original list to the weavingURLCLassloader
> > > and it will weave the jars it needs as well.
> > >
> > > thanks,
> > > Mike
> > >
> > >
>
> _______________________________________________
> aspectj-dev mailing list
> [hidden email]
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
_______________________________________________
aspectj-dev mailing list
[hidden email]
https://dev.eclipse.org/mailman/listinfo/aspectj-dev