RE: [ajdt-dev] Can't determine superclass of missing type (was Weaving i

["Neale Upstone" <neale.upstone@xxxxxxxxxx>]

We've completed a full circle.  That's the original problem.

If I only add the project as a dependency on inpath, the jars that it uses internally are not consulted.  Therefore, to get things to compile I had to export them.

I've gotta call it a day now.   Perhaps the .classpaths will clear things up.

This is the .classpath for base-facade:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="all/src/main/aspectj"/>
	<classpathentry excluding="**/.svn/" kind="src" path="all/src/main/java"/>
	<classpathentry excluding="**/.svn/" kind="src" path="all/src/test/java"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	<classpathentry kind="src" path="/base">
		<attributes>
			<attribute name="org.eclipse.ajdt.inpath" value="org.eclipse.ajdt.inpath"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.ajdt.core.ASPECTJRT_CONTAINER"/>
	<classpathentry kind="lib" path="/base/all/lib/ide/itext.jar">
		<attributes>
			<attribute name="org.eclipse.ajdt.inpath" value="org.eclipse.ajdt.inpath"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="output" path="bin"/>
</classpath>

And this is the .classpath for base:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry excluding="**/.svn/" kind="src" path="all/src/main/java"/>
	<classpathentry kind="lib" path="all/lib/ide/itext.jar"/>
	<classpathentry kind="lib" path="all/lib/ide/jbcl.jar"/>
	<classpathentry kind="lib" path="all/lib/ide/jcommon.jar"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	<classpathentry kind="output" path="bin"/>
</classpath>

The result is:
can't determine superclass of missing type com.borland.jbcl.layout.PaneLayout
when weaving type [base].Dialogs.JDL_ColorChooser
when weaving classes 
when weaving 
when batch building BuildConfig[**C:\Apps\eclipse\**base-facade] #Files=83 AopXmls=#0
 [Xlint:cantFindType]

P.S. Note the stuff in ** **.  You've got ECLIPSE_HOME when it should be workspace home.


> -----Original Message-----
> From: ajdt-dev-bounces@xxxxxxxxxxx 
> [mailto:ajdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Eisenberg
> Sent: 02 March 2009 19:10
> To: ajdt-dev@xxxxxxxxxxx
> Subject: Re: [ajdt-dev] Can't determine superclass of missing 
> type (was Weaving into a "read-only" project)
> 
> AJDT's behavior is that if a jar in a project that is on the inpath is
> exported, then that jar gets put on the inpath.  Otherwise, it does
> not.
> 
> So, if you were to make jbcl.jar and jcommon.jar not exported, then
> they should not be touched by the weaver.
> 
> Is it a requirement that they be exported?
> 
> On Mon, Mar 2, 2009 at 10:48 AM, Neale Upstone 
> <neale.upstone@xxxxxxxxxx> wrote:
> >   - jbcl.jar (exported - I don't want to have to export this)
> >   - jcommon.jar (exported - nor this)
> >
> >
> > Essentially, my view is that if I do not specifically 
> include a jar on
> > the inpath, I don't want it woven, and don't expect to see 
> it's .class
> > files appearing in /bin
> >
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
> 
**********************************************************************
IMPORTANT NOTICE.
Confidentiality:  This e-mail and its attachments are intended for the above named only and may be confidential.  If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this e-mail and highlight the error.
Security Warning:  Please note that this e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium.
We advise that you understand and observe this lack of security when e-mailing us.
Viruses:  Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Monitoring and Scanning:  Cambridge Cognition has monitoring and scanning systems in place in relation to emails sent and received to: monitor / record business communications; prevent and detect crime; investigate the use of the Company's internal and external email system; and provide evidence of compliance with business practices.

Cambridge Cognition Limited
Company Registration Number 4338746
Registered address:
Tunbridge Court
Tunbridge Lane
Bottisham
Cambridge
CB25 9TU
UK
**********************************************************************