Re: [ajdt-dev] Running JUnit tests

[Nick Brett <nb271@xxxxxxxxx>]

Just to let you know.

I didn't have any major problems getting AJDT to compile and run on my  
setup. The AspectJ compiler did crash at one point but I wasn't able to  
nail down what I'd done to cause that. But basically there's nothing  
major that stops AJDT running on the Mac with M3.

On Wednesday, October 1, 2003, at 05:28  pm, Ron Bodkin wrote:

> I tried to run AJDT 1.1.4 in Eclipse 3.0M3 on Windows XP and it gave  
> me an NPE (see below). I didn't report it because I assumed that 3.0  
> compatibility wasn't yet being tackled. But when I fixed the project  
> set up just now (by defining missing variables) it compiled  
> successfully, so it looks like AJDT does basically work in 3.0M3.  
> Should we be reporting bugs like this one for AJDT+3.0M3?
>
> java.lang.NullPointerException
> at  
> org.eclipse.ajdt.internal.ui.ajde.ProjectProperties.getProjectSourceFil 
> es(ProjectProperties.java:174)
> at org.eclipse.ajdt.internal.builder.Builder.build(Builder.java:153)
> at  
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:4 
> 40)
> at  
> org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform 
> .java:1016)
> at org.eclipse.core.runtime.Platform.run(Platform.java:420)
> at  
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j 
> ava:128)
> at  
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j 
> ava:184)
> at  
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j 
> ava:194)
> at  
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:1 
> 54)
> at  
> org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform 
> .java:1016)
> at org.eclipse.core.runtime.Platform.run(Platform.java:420)
> at  
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.j 
> ava:168)
> at  
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:2 
> 78)
> at org.eclipse.core.internal.resources.Project.build(Project.java:85)
> at  
> org.eclipse.ajdt.internal.ui.PulldownBuildselectorMenu$1.run(PulldownBu 
> ildselectorMenu.java:295)
> at  
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalCo 
> ntext.java:101)
>
>
> Ron Bodkin
> Chief Technology Officer
> New Aspects of Security
> m: (415) 509-2895
>
> > ------------Original Message-------------
> > From: "Andrew Clement" <CLEMAS@xxxxxxxxxx>
> > To: ajdt-dev@xxxxxxxxxxxxxxx
> > Date: Wed, Oct-1-2003 6:30 AM
> > Subject: Re: [ajdt-dev] Running JUnit tests
> >
> >
> > Hi Nick,
> >
> > > OS: MacOS X 10.2.8
> > > Java: 1.4.1
> > > Eclipse: 3.0M3
> > > AJDT: Latest CVS
> >
> > Now that is on the bleeding edge.  We haven't fully tested AJDT with
> > Eclipse 3.0 - and I don't know of anyone else doing AJDT development
> > on the Mac.  Of course, it should work, its just that you may hit a
> > few issues we haven't...
> >
> > First thing I should say is you might as well ignore the unit tests,
> > AJDT came to life before we 'saw the light' with the Test Driven
> > Development approach.  We have a work item to go back and add some
> > relevant ones ... but we just haven't managed it yet.
> >
> > The approach we *would* take if we had some tests is using the PDE
> > JUnit framework that is specifically for testing plugin projects,
> > rather than the basic JUnit stuff.  Not sure if its built into
> > Eclipse 3.0 or not.  The URL is:
> >
> > http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/ 
> > plugins/org.eclipse.jdt.junit/index.html
> >
> > With this PDE JUnit setup, we define a special kind of Junit runtime
> > configuration which launches a new workbench, runs the junit tests
> > then shuts it down.
> >
> > > Also has anybody thought about using mock objects -  
> > > www.mockobjects.com
> > > - to allow the unit tests to be run without this tight integration  
> > > with
> > > the workbench?
> >
> > Hmmm.  AJDT is kind of a thin Eclipse veneer that links the aspectj
> > compiler into Eclipse.  I'm not quite sure what AJDT would become if
> > the workbench was mocked out ??
> >
> > So basically, ignore the existing unit tests and probably all the
> > framework.  If you want to write some to the PDE Junit structure
> > and contribute them - that would be excellent ;)
> >
> > Andy.
> >
> >
> >
> > _______________________________________________
> > ajdt-dev mailing list
> > ajdt-dev@xxxxxxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/ajdt-dev
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/ajdt-dev