Bug 230451 - Had problem in extracting '*.jar' given in 'InPath' during weaving.
Summary: Had problem in extracting '*.jar' given in 'InPath' during weaving.
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: IDE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-06 14:17 EDT by Madhava Dass CLA
Modified: 2008-10-24 17:06 EDT (History)
1 user (show)

See Also:


Attachments
It is a word document capturing the screen shot of exception. (48.50 KB, application/msword)
2008-05-06 14:17 EDT, Madhava Dass CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Madhava Dass CLA 2008-05-06 14:17:14 EDT
Created attachment 98901 [details]
It is a word document capturing the screen shot of exception.

Build ID: Build id: M20080221-1800

Steps To Reproduce:
1. Create 3 projects (proj1 for abstract aspect that produces abstractAspect.jar, proj2 for concrete aspect implementing JP in proj1 and generating concreteAspect.jar, proj3 containing myClasses.jar using abstractAspect.jar, and concreteAspect.jar)
2. Build 'proj1', and 'proj2', and 'proj3' so they generate *.jars idependently.
3. Perform 'proj3' as aspect project by providing 'abstractAspect.jar, and concreteAspect.jar in 'aspectPath', and 'myClasses.jar' in InPath.
3.


More information:
How can I provide attachments of a screen shots?
Comment 1 Andrew Clement CLA 2008-08-20 17:00:08 EDT
Exception from the document is:

java.util.zip.ZipException
at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:175)
at java.util.jar.JarOutputStream.putNextEntry(JarOutputStream.java:92)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager$4.writeZipEntry(AjBuildManager.java:1094)

I guess we don't know which project build led to this exception?  or was it just the bottom of the tree (proj3?)

I have seen issues with zip files when the output jar is also on the classpath of the same project - but it doesn't sound like you are setup like that.

I presume the exception doesn't happen in just the 2 project scenario, ie. with just the Abstract Aspect project and the Concrete Aspect project?  You need to have that third project defined.

Where does myClasses.jar come from?  Just some other project or off the filesystem?

Is there an output jar specified for proj3 or does it just output into the bin folder of the project?

How about updating to a recent AJDT and using project dependencies rather than jar dependencies (we have recently added support for project dependencies on the aspectpath and inpath).