Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » producing a "deployable plugin with AspectJ support" fails
producing a "deployable plugin with AspectJ support" fails [message #67830] Fri, 17 November 2006 08:25 Go to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
I have finalized a plugin (i.e. it works fine when I start it in the
runtime workbench) and so I would now like to convert it into some
distributable form.

Thus, I started with File => Export.... and selected "Deployable plugins
and fragments with AspectJ support". I select my project and enter the
..zip file name into which to pack up everything and also selected to
save the procedure as ant script and then pressed "Finish".

That runs for a while and then for some - to me inexpliccable - reason
that process terminates telling me that there were 14 compile errors.
And no .zip is produced.

???? But this compiled and ran fine before! So where do these compile
errors suddenly come from? And why does this recompile things in the
first place? It should just export (i.e. pack and wrap up) things - at
least that's what I would have expected...

Any ideas?

This is on eclipse 3.2.1 and I tried this with the same result using
ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
provided).

Michael
Re: producing a "deployable plugin with AspectJ support" fails [message #67850 is a reply to message #67830] Fri, 17 November 2006 12:51 Go to previous messageGo to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Maybe this helps analyzing this problem: the log shows a couple of error
messages that read e.g.:

----------------------------
....
C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
The following error occurred while executing this line:
C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
The following error occurred while executing this line:
C:\JavaDevt\myproject\build.xml:195: The following error occurred while
executing this line:
C:\JavaDevt\myproject\build.xml:170: compile errors: 14
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
at
org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
at
org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
The following error occurred while executing this line:
....
(this continue about 3 times, every 2 or 3 "Caused by: ..." there is a
line "Nested Exception:" and then things seem to repeat from the
beginning again. This continues about 3 times, except for the last
segment which finally reads:
....
--- Nested Exception ---
C:\JavaDevt\myproject\build.xml:170: compile errors: 14
at
org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
at
org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
at
org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
----------------------------

Strange enough - there is no "build.xml" file (mentioned in lines 3 & 4)
in my project! Or is this file temporarily created only?

Michael


"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:ejjrla$c0o$1@utils.eclipse.org...
>I have finalized a plugin (i.e. it works fine when I start it in the
>runtime workbench) and so I would now like to convert it into some
>distributable form.
>
> Thus, I started with File => Export.... and selected "Deployable
> plugins and fragments with AspectJ support". I select my project and
> enter the .zip file name into which to pack up everything and also
> selected to save the procedure as ant script and then pressed
> "Finish".
>
> That runs for a while and then for some - to me inexpliccable - reason
> that process terminates telling me that there were 14 compile errors.
> And no .zip is produced.
>
> ???? But this compiled and ran fine before! So where do these compile
> errors suddenly come from? And why does this recompile things in the
> first place? It should just export (i.e. pack and wrap up) things - at
> least that's what I would have expected...
>
> Any ideas?
>
> This is on eclipse 3.2.1 and I tried this with the same result using
> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
> provided).
>
> Michael
>
Re: producing a "deployable plugin with AspectJ support" fails [message #67871 is a reply to message #67850] Fri, 17 November 2006 14:37 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Michael,

That export wizard does the equivalent of the non-AspectJ version, which
is to generate a build.xml file and then run it, in order to create the
deployable plugin in the same way as in an automated PDE build process.
If you don't want this rebuild step, you could export the project as a
zip file and choose the contents manually.

The log messages confirm that the AJC ant task is correctly being used
instead of the regular Javac task. But unfortunately it's not telling us
what those 14 compiler errors, plus it cleans up the generated build.xml
as you discovered.

To diagnose this further, you should ensure you have an accurate
build.properties file for your plugin, and then right-click on the
plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant Build
File with AspectJ support". You should then have a build.xml file which
you can run, and see the output in the console.

Regards,

Matt.

Michael Moser wrote:
> Maybe this helps analyzing this problem: the log shows a couple of error
> messages that read e.g.:
>
> ----------------------------
> ...
> C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
> The following error occurred while executing this line:
> C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
> The following error occurred while executing this line:
> C:\JavaDevt\myproject\build.xml:195: The following error occurred while
> executing this line:
> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
> at
> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>
> at
> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> Caused by: C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
> The following error occurred while executing this line:
> ...
> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is a
> line "Nested Exception:" and then things seem to repeat from the
> beginning again. This continues about 3 times, except for the last
> segment which finally reads:
> ...
> --- Nested Exception ---
> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
> at
> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>
> at
> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> ----------------------------
>
> Strange enough - there is no "build.xml" file (mentioned in lines 3 & 4)
> in my project! Or is this file temporarily created only?
>
> Michael
>
>
> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
> news:ejjrla$c0o$1@utils.eclipse.org...
>> I have finalized a plugin (i.e. it works fine when I start it in the
>> runtime workbench) and so I would now like to convert it into some
>> distributable form.
>>
>> Thus, I started with File => Export.... and selected "Deployable
>> plugins and fragments with AspectJ support". I select my project and
>> enter the .zip file name into which to pack up everything and also
>> selected to save the procedure as ant script and then pressed "Finish".
>>
>> That runs for a while and then for some - to me inexpliccable - reason
>> that process terminates telling me that there were 14 compile errors.
>> And no .zip is produced.
>>
>> ???? But this compiled and ran fine before! So where do these compile
>> errors suddenly come from? And why does this recompile things in the
>> first place? It should just export (i.e. pack and wrap up) things - at
>> least that's what I would have expected...
>>
>> Any ideas?
>>
>> This is on eclipse 3.2.1 and I tried this with the same result using
>> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
>> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
>> provided).
>>
>> Michael
>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #67892 is a reply to message #67871] Fri, 17 November 2006 16:19 Go to previous messageGo to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Followed your advice, but using that generated build.xml I now have 998
errors! 8-O

But at least I can now see, that it's apparently deeply diving down the
type tree and produces tons of message like:
<some.jar> [error] can't determine whether missing type
org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance of
<some type>
etc. etc.

That's apparently all stuff from some logging and other libraries that I
am using. Seems, I have to work on my classpaths again (Aaargh! Compared
with Java's constant classpath issues any DLL-hell I ever encountered
was a piece of cake, but that's a different story...).

But why does this behavior differ from normal compilation, i.e. why can
I happily compile and even run things otherwise? Why is this
export-build different? Puzzles over puzzles...

Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
analysis short at some level?

Michael


"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ejkhf8$nus$1@utils.eclipse.org...
> Hi Michael,
>
> That export wizard does the equivalent of the non-AspectJ version,
> which is to generate a build.xml file and then run it, in order to
> create the deployable plugin in the same way as in an automated PDE
> build process. If you don't want this rebuild step, you could export
> the project as a zip file and choose the contents manually.
>
> The log messages confirm that the AJC ant task is correctly being used
> instead of the regular Javac task. But unfortunately it's not telling
> us what those 14 compiler errors, plus it cleans up the generated
> build.xml as you discovered.
>
> To diagnose this further, you should ensure you have an accurate
> build.properties file for your plugin, and then right-click on the
> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
> Build File with AspectJ support". You should then have a build.xml
> file which you can run, and see the output in the console.
>
> Regards,
>
> Matt.
>
> Michael Moser wrote:
>> Maybe this helps analyzing this problem: the log shows a couple of
>> error messages that read e.g.:
>>
>> ----------------------------
>> ...
>> C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>> The following error occurred while executing this line:
>> C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>> The following error occurred while executing this line:
>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>> while executing this line:
>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>> at
>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>> at
>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>> Caused by: C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>> The following error occurred while executing this line:
>> ...
>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>> a line "Nested Exception:" and then things seem to repeat from the
>> beginning again. This continues about 3 times, except for the last
>> segment which finally reads:
>> ...
>> --- Nested Exception ---
>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>> at
>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>> at
>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>> ----------------------------
>>
>> Strange enough - there is no "build.xml" file (mentioned in lines 3 &
>> 4) in my project! Or is this file temporarily created only?
>>
>> Michael
>>
>>
>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>> news:ejjrla$c0o$1@utils.eclipse.org...
>>> I have finalized a plugin (i.e. it works fine when I start it in the
>>> runtime workbench) and so I would now like to convert it into some
>>> distributable form.
>>>
>>> Thus, I started with File => Export.... and selected "Deployable
>>> plugins and fragments with AspectJ support". I select my project and
>>> enter the .zip file name into which to pack up everything and also
>>> selected to save the procedure as ant script and then pressed
>>> "Finish".
>>>
>>> That runs for a while and then for some - to me inexpliccable -
>>> reason that process terminates telling me that there were 14 compile
>>> errors. And no .zip is produced.
>>>
>>> ???? But this compiled and ran fine before! So where do these
>>> compile errors suddenly come from? And why does this recompile
>>> things in the first place? It should just export (i.e. pack and wrap
>>> up) things - at least that's what I would have expected...
>>>
>>> Any ideas?
>>>
>>> This is on eclipse 3.2.1 and I tried this with the same result using
>>> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
>>> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
>>> provided).
>>>
>>> Michael
>>>
>>
Re: producing a "deployable plugin with AspectJ support" fails [message #67912 is a reply to message #67892] Fri, 17 November 2006 16:45 Go to previous messageGo to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Grrrr - down by 18, i.e. still 980 errors. :-(

Why is this thing telling telling me almost 1000 times, that it is
unable to check, whether some javax.* or commonj.timers.* or
org.eclipse.hyades.logging.* or whatever other types my 25+ .jar
libraries contain is an instance of one of my interfaces??? The answer
to all these can easily be given and is "certainly not!". I urgently
need some way to stop this!

Michael


"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:ejknea$lp$1@utils.eclipse.org...
> Followed your advice, but using that generated build.xml I now have
> 998 errors! 8-O
>
> But at least I can now see, that it's apparently deeply diving down
> the type tree and produces tons of message like:
> <some.jar> [error] can't determine whether missing type
> org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance
> of <some type>
> etc. etc.
>
> That's apparently all stuff from some logging and other libraries that
> I am using. Seems, I have to work on my classpaths again (Aaargh!
> Compared with Java's constant classpath issues any DLL-hell I ever
> encountered was a piece of cake, but that's a different story...).
>
> But why does this behavior differ from normal compilation, i.e. why
> can I happily compile and even run things otherwise? Why is this
> export-build different? Puzzles over puzzles...
>
> Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
> analysis short at some level?
>
> Michael
>
>
> "Matt Chapman" <mpchapman@gmail.com> wrote in message
> news:ejkhf8$nus$1@utils.eclipse.org...
>> Hi Michael,
>>
>> That export wizard does the equivalent of the non-AspectJ version,
>> which is to generate a build.xml file and then run it, in order to
>> create the deployable plugin in the same way as in an automated PDE
>> build process. If you don't want this rebuild step, you could export
>> the project as a zip file and choose the contents manually.
>>
>> The log messages confirm that the AJC ant task is correctly being
>> used instead of the regular Javac task. But unfortunately it's not
>> telling us what those 14 compiler errors, plus it cleans up the
>> generated build.xml as you discovered.
>>
>> To diagnose this further, you should ensure you have an accurate
>> build.properties file for your plugin, and then right-click on the
>> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
>> Build File with AspectJ support". You should then have a build.xml
>> file which you can run, and see the output in the console.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Moser wrote:
>>> Maybe this helps analyzing this problem: the log shows a couple of
>>> error messages that read e.g.:
>>>
>>> ----------------------------
>>> ...
>>> C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>>> The following error occurred while executing this line:
>>> C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>> The following error occurred while executing this line:
>>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>>> while executing this line:
>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>> at
>>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>> at
>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>> at
>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>> Caused by: C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>> The following error occurred while executing this line:
>>> ...
>>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>>> a line "Nested Exception:" and then things seem to repeat from the
>>> beginning again. This continues about 3 times, except for the last
>>> segment which finally reads:
>>> ...
>>> --- Nested Exception ---
>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>> at
>>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>> at
>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>> at
>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>> ----------------------------
>>>
>>> Strange enough - there is no "build.xml" file (mentioned in lines 3
>>> & 4) in my project! Or is this file temporarily created only?
>>>
>>> Michael
>>>
>>>
>>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>>> news:ejjrla$c0o$1@utils.eclipse.org...
>>>> I have finalized a plugin (i.e. it works fine when I start it in
>>>> the runtime workbench) and so I would now like to convert it into
>>>> some distributable form.
>>>>
>>>> Thus, I started with File => Export.... and selected "Deployable
>>>> plugins and fragments with AspectJ support". I select my project
>>>> and enter the .zip file name into which to pack up everything and
>>>> also selected to save the procedure as ant script and then pressed
>>>> "Finish".
>>>>
>>>> That runs for a while and then for some - to me inexpliccable -
>>>> reason that process terminates telling me that there were 14
>>>> compile errors. And no .zip is produced.
>>>>
>>>> ???? But this compiled and ran fine before! So where do these
>>>> compile errors suddenly come from? And why does this recompile
>>>> things in the first place? It should just export (i.e. pack and
>>>> wrap up) things - at least that's what I would have expected...
>>>>
>>>> Any ideas?
>>>>
>>>> This is on eclipse 3.2.1 and I tried this with the same result
>>>> using ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and
>>>> also with 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest
>>>> developer build provided).
>>>>
>>>> Michael
>>>>
>>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #67933 is a reply to message #67912] Fri, 17 November 2006 17:51 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Compiling via the iajc ant task should be the same as via the builder in
Eclipse. Can you check that the ant task in the build.xml is referring
to the right version of the aspectj plugins - in case you have multiple
versions installed. Have you set any AspectJ compiler options in your
project's properties?

--Matt

Michael Moser wrote:
> Grrrr - down by 18, i.e. still 980 errors. :-(
>
> Why is this thing telling telling me almost 1000 times, that it is
> unable to check, whether some javax.* or commonj.timers.* or
> org.eclipse.hyades.logging.* or whatever other types my 25+ .jar
> libraries contain is an instance of one of my interfaces??? The answer
> to all these can easily be given and is "certainly not!". I urgently
> need some way to stop this!
>
> Michael
>
>
> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
> news:ejknea$lp$1@utils.eclipse.org...
>> Followed your advice, but using that generated build.xml I now have
>> 998 errors! 8-O
>>
>> But at least I can now see, that it's apparently deeply diving down
>> the type tree and produces tons of message like:
>> <some.jar> [error] can't determine whether missing type
>> org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance
>> of <some type>
>> etc. etc.
>>
>> That's apparently all stuff from some logging and other libraries that
>> I am using. Seems, I have to work on my classpaths again (Aaargh!
>> Compared with Java's constant classpath issues any DLL-hell I ever
>> encountered was a piece of cake, but that's a different story...).
>>
>> But why does this behavior differ from normal compilation, i.e. why
>> can I happily compile and even run things otherwise? Why is this
>> export-build different? Puzzles over puzzles...
>>
>> Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
>> analysis short at some level?
>>
>> Michael
>>
>>
>> "Matt Chapman" <mpchapman@gmail.com> wrote in message
>> news:ejkhf8$nus$1@utils.eclipse.org...
>>> Hi Michael,
>>>
>>> That export wizard does the equivalent of the non-AspectJ version,
>>> which is to generate a build.xml file and then run it, in order to
>>> create the deployable plugin in the same way as in an automated PDE
>>> build process. If you don't want this rebuild step, you could export
>>> the project as a zip file and choose the contents manually.
>>>
>>> The log messages confirm that the AJC ant task is correctly being
>>> used instead of the regular Javac task. But unfortunately it's not
>>> telling us what those 14 compiler errors, plus it cleans up the
>>> generated build.xml as you discovered.
>>>
>>> To diagnose this further, you should ensure you have an accurate
>>> build.properties file for your plugin, and then right-click on the
>>> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
>>> Build File with AspectJ support". You should then have a build.xml
>>> file which you can run, and see the output in the console.
>>>
>>> Regards,
>>>
>>> Matt.
>>>
>>> Michael Moser wrote:
>>>> Maybe this helps analyzing this problem: the log shows a couple of
>>>> error messages that read e.g.:
>>>>
>>>> ----------------------------
>>>> ...
>>>> C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>>>> The following error occurred while executing this line:
>>>> C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>>> The following error occurred while executing this line:
>>>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>>>> while executing this line:
>>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>>> at
>>>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>>> at
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>>> at
>>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>>> Caused by: C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>>> The following error occurred while executing this line:
>>>> ...
>>>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>>>> a line "Nested Exception:" and then things seem to repeat from the
>>>> beginning again. This continues about 3 times, except for the last
>>>> segment which finally reads:
>>>> ...
>>>> --- Nested Exception ---
>>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>>> at
>>>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>>>>
>>>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>>> at
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>>> at
>>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>>> ----------------------------
>>>>
>>>> Strange enough - there is no "build.xml" file (mentioned in lines 3
>>>> & 4) in my project! Or is this file temporarily created only?
>>>>
>>>> Michael
>>>>
>>>>
>>>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>>>> news:ejjrla$c0o$1@utils.eclipse.org...
>>>>> I have finalized a plugin (i.e. it works fine when I start it in
>>>>> the runtime workbench) and so I would now like to convert it into
>>>>> some distributable form.
>>>>>
>>>>> Thus, I started with File => Export.... and selected "Deployable
>>>>> plugins and fragments with AspectJ support". I select my project
>>>>> and enter the .zip file name into which to pack up everything and
>>>>> also selected to save the procedure as ant script and then pressed
>>>>> "Finish".
>>>>>
>>>>> That runs for a while and then for some - to me inexpliccable -
>>>>> reason that process terminates telling me that there were 14
>>>>> compile errors. And no .zip is produced.
>>>>>
>>>>> ???? But this compiled and ran fine before! So where do these
>>>>> compile errors suddenly come from? And why does this recompile
>>>>> things in the first place? It should just export (i.e. pack and
>>>>> wrap up) things - at least that's what I would have expected...
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> This is on eclipse 3.2.1 and I tried this with the same result
>>>>> using ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and
>>>>> also with 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest
>>>>> developer build provided).
>>>>>
>>>>> Michael
>>>>>
>>>>
>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #67954 is a reply to message #67933] Thu, 23 November 2006 16:30 Go to previous messageGo to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ejksq7$fiv$1@utils.eclipse.org...
> Compiling via the iajc ant task should be the same as via the builder
> in Eclipse. Can you check that the ant task in the build.xml is
> referring to the right version of the aspectj plugins - in case you
> have multiple versions installed.

I saved the a generated ant-script not to build.xml (since there is a
warning, that this name is reserved for PDE), but to a different name.
The file contents reads:

<?xml version="1.0" encoding="UTF-8"?>
<project default="plugin_export" name="build">
<target name="plugin_export">
<pde.exportPlugins destination="C:\JavaDevt\myproject"
exportSource="false" exportType="zip" filename="myproject.zip"
plugins="myproject" useJARFormat="false"/>
</target>
</project>

I can't see anything fishy but I also see no mentioning of aspectj here.
Maybe that's the reason?
A "build.xml" is temporarily created during the export, but removed at
the end of the build process.
As I said initially: the build process fails claiming 14 compile
errors - which could roughly be the number of to-be-weaved and now maybe
missing interfaces.

> Have you set any AspectJ compiler options in your project's
> properties?

No - I haven't modified any AspectJ option. I am using no project
specific settings and the system settings are the default ones.
I added three .jar files to the AspectJ inpath of this project, since I
need to weave aspects into these. That's the only adjustment re. aspects
that I did.

BTW: Again I downloaded and tried the latest build
(ajdt_1.5.0.200611221156) but no change.

Michael
Re: producing a "deployable plugin with AspectJ support" fails [message #68020 is a reply to message #67954] Tue, 28 November 2006 14:37 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Michael Moser wrote:
> I saved the a generated ant-script not to build.xml (since there is a
> warning, that this name is reserved for PDE), but to a different name.
> The file contents reads:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project default="plugin_export" name="build">
> <target name="plugin_export">
> <pde.exportPlugins destination="C:\JavaDevt\myproject"
> exportSource="false" exportType="zip" filename="myproject.zip"
> plugins="myproject" useJARFormat="false"/>
> </target>
> </project>
>
> I can't see anything fishy but I also see no mentioning of aspectj here.
> Maybe that's the reason?

How did you generate that build file? I haven't seen ones like that
before. Try this:

To diagnose this further, you should ensure you have an accurate
build.properties file for your plugin, and then right-click on the
plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant Build
File with AspectJ support". You should then have a build.xml file which
you can run, and see the output in the console.

This should then be the same as the build.xml generated during the
export. It should be much longer, and contain an "iajc" line.

--Matt
Re: producing a "deployable plugin with AspectJ support" fails [message #68784 is a reply to message #68020] Tue, 05 December 2006 10:18 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ekhhjd$u1a$1@utils.eclipse.org...
> Michael Moser wrote:
>> I saved the a generated ant-script not to build.xml (since there is a
>> warning, that this name is reserved for PDE), but to a different
>> name.
>> The file contents reads:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <project default="plugin_export" name="build">
>> <target name="plugin_export">
>> <pde.exportPlugins destination="C:\JavaDevt\myproject"
>> exportSource="false" exportType="zip" filename="myproject.zip"
>> plugins="myproject" useJARFormat="false"/>
>> </target>
>> </project>
>>
>> I can't see anything fishy but I also see no mentioning of aspectj
>> here. Maybe that's the reason?
>
> How did you generate that build file?

That is the file created if one checks "Save as Ant script" on the
options tab of the Export dialog after choosing "File => Export... =>
Deployable plug-ins and fragments with AspectJ support".

> I haven't seen ones like that before. Try this:
>
> To diagnose this further, you should ensure you have an accurate
> build.properties file for your plugin, and then right-click on the
> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
> Build File with AspectJ support". You should then have a build.xml
> file which you can run, and see the output in the console.
> This should then be the same as the build.xml generated during the
> export. It should be much longer, and contain an "iajc" line.

If I do the "PDE Tools > Create Ant Build File with AspectJ support" as
instructed there is a build.xml file created and that one looks indeed
VERY different from the above. However, for some strange reason this
build.xml is always removed as part of the above mentioned Export (i.e.
that export obviously triggers another build and that build seems to
delete the build.xml file). Really very odd!

I still haven't mastered to create anything deployable (plugin and/or
feature) with AspectJ support. And I am 100% sure that this used to work
under 3.1 (because I created earlier plugins using this method), but
obviously not any more under 3.2(.1) nor 3.3M3.

Michael
Re: producing a "deployable plugin with AspectJ support" fails [message #595365 is a reply to message #67830] Fri, 17 November 2006 12:51 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Maybe this helps analyzing this problem: the log shows a couple of error
messages that read e.g.:

----------------------------
....
C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
The following error occurred while executing this line:
C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
The following error occurred while executing this line:
C:\JavaDevt\myproject\build.xml:195: The following error occurred while
executing this line:
C:\JavaDevt\myproject\build.xml:170: compile errors: 14
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
at
org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
at
org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: C:\Documents and
Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
The following error occurred while executing this line:
....
(this continue about 3 times, every 2 or 3 "Caused by: ..." there is a
line "Nested Exception:" and then things seem to repeat from the
beginning again. This continues about 3 times, except for the last
segment which finally reads:
....
--- Nested Exception ---
C:\JavaDevt\myproject\build.xml:170: compile errors: 14
at
org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
at
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
at
org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
at
org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
at
org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
----------------------------

Strange enough - there is no "build.xml" file (mentioned in lines 3 & 4)
in my project! Or is this file temporarily created only?

Michael


"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:ejjrla$c0o$1@utils.eclipse.org...
>I have finalized a plugin (i.e. it works fine when I start it in the
>runtime workbench) and so I would now like to convert it into some
>distributable form.
>
> Thus, I started with File => Export.... and selected "Deployable
> plugins and fragments with AspectJ support". I select my project and
> enter the .zip file name into which to pack up everything and also
> selected to save the procedure as ant script and then pressed
> "Finish".
>
> That runs for a while and then for some - to me inexpliccable - reason
> that process terminates telling me that there were 14 compile errors.
> And no .zip is produced.
>
> ???? But this compiled and ran fine before! So where do these compile
> errors suddenly come from? And why does this recompile things in the
> first place? It should just export (i.e. pack and wrap up) things - at
> least that's what I would have expected...
>
> Any ideas?
>
> This is on eclipse 3.2.1 and I tried this with the same result using
> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
> provided).
>
> Michael
>
Re: producing a "deployable plugin with AspectJ support" fails [message #595373 is a reply to message #67850] Fri, 17 November 2006 14:37 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Michael,

That export wizard does the equivalent of the non-AspectJ version, which
is to generate a build.xml file and then run it, in order to create the
deployable plugin in the same way as in an automated PDE build process.
If you don't want this rebuild step, you could export the project as a
zip file and choose the contents manually.

The log messages confirm that the AJC ant task is correctly being used
instead of the regular Javac task. But unfortunately it's not telling us
what those 14 compiler errors, plus it cleans up the generated build.xml
as you discovered.

To diagnose this further, you should ensure you have an accurate
build.properties file for your plugin, and then right-click on the
plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant Build
File with AspectJ support". You should then have a build.xml file which
you can run, and see the output in the console.

Regards,

Matt.

Michael Moser wrote:
> Maybe this helps analyzing this problem: the log shows a couple of error
> messages that read e.g.:
>
> ----------------------------
> ...
> C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
> The following error occurred while executing this line:
> C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
> The following error occurred while executing this line:
> C:\JavaDevt\myproject\build.xml:195: The following error occurred while
> executing this line:
> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
> at
> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>
> at
> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> Caused by: C:\Documents and
> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
> The following error occurred while executing this line:
> ...
> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is a
> line "Nested Exception:" and then things seem to repeat from the
> beginning again. This continues about 3 times, except for the last
> segment which finally reads:
> ...
> --- Nested Exception ---
> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
> at
> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at
> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>
> at
> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>
> at
> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> ----------------------------
>
> Strange enough - there is no "build.xml" file (mentioned in lines 3 & 4)
> in my project! Or is this file temporarily created only?
>
> Michael
>
>
> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
> news:ejjrla$c0o$1@utils.eclipse.org...
>> I have finalized a plugin (i.e. it works fine when I start it in the
>> runtime workbench) and so I would now like to convert it into some
>> distributable form.
>>
>> Thus, I started with File => Export.... and selected "Deployable
>> plugins and fragments with AspectJ support". I select my project and
>> enter the .zip file name into which to pack up everything and also
>> selected to save the procedure as ant script and then pressed "Finish".
>>
>> That runs for a while and then for some - to me inexpliccable - reason
>> that process terminates telling me that there were 14 compile errors.
>> And no .zip is produced.
>>
>> ???? But this compiled and ran fine before! So where do these compile
>> errors suddenly come from? And why does this recompile things in the
>> first place? It should just export (i.e. pack and wrap up) things - at
>> least that's what I would have expected...
>>
>> Any ideas?
>>
>> This is on eclipse 3.2.1 and I tried this with the same result using
>> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
>> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
>> provided).
>>
>> Michael
>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #595378 is a reply to message #67871] Fri, 17 November 2006 16:19 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Followed your advice, but using that generated build.xml I now have 998
errors! 8-O

But at least I can now see, that it's apparently deeply diving down the
type tree and produces tons of message like:
<some.jar> [error] can't determine whether missing type
org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance of
<some type>
etc. etc.

That's apparently all stuff from some logging and other libraries that I
am using. Seems, I have to work on my classpaths again (Aaargh! Compared
with Java's constant classpath issues any DLL-hell I ever encountered
was a piece of cake, but that's a different story...).

But why does this behavior differ from normal compilation, i.e. why can
I happily compile and even run things otherwise? Why is this
export-build different? Puzzles over puzzles...

Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
analysis short at some level?

Michael


"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ejkhf8$nus$1@utils.eclipse.org...
> Hi Michael,
>
> That export wizard does the equivalent of the non-AspectJ version,
> which is to generate a build.xml file and then run it, in order to
> create the deployable plugin in the same way as in an automated PDE
> build process. If you don't want this rebuild step, you could export
> the project as a zip file and choose the contents manually.
>
> The log messages confirm that the AJC ant task is correctly being used
> instead of the regular Javac task. But unfortunately it's not telling
> us what those 14 compiler errors, plus it cleans up the generated
> build.xml as you discovered.
>
> To diagnose this further, you should ensure you have an accurate
> build.properties file for your plugin, and then right-click on the
> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
> Build File with AspectJ support". You should then have a build.xml
> file which you can run, and see the output in the console.
>
> Regards,
>
> Matt.
>
> Michael Moser wrote:
>> Maybe this helps analyzing this problem: the log shows a couple of
>> error messages that read e.g.:
>>
>> ----------------------------
>> ...
>> C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>> The following error occurred while executing this line:
>> C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>> The following error occurred while executing this line:
>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>> while executing this line:
>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>> at
>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>> at
>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>> Caused by: C:\Documents and
>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>> The following error occurred while executing this line:
>> ...
>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>> a line "Nested Exception:" and then things seem to repeat from the
>> beginning again. This continues about 3 times, except for the last
>> segment which finally reads:
>> ...
>> --- Nested Exception ---
>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>> at
>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at
>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>> at
>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>> at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>> at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>> at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>> at
>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>> at
>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>> ----------------------------
>>
>> Strange enough - there is no "build.xml" file (mentioned in lines 3 &
>> 4) in my project! Or is this file temporarily created only?
>>
>> Michael
>>
>>
>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>> news:ejjrla$c0o$1@utils.eclipse.org...
>>> I have finalized a plugin (i.e. it works fine when I start it in the
>>> runtime workbench) and so I would now like to convert it into some
>>> distributable form.
>>>
>>> Thus, I started with File => Export.... and selected "Deployable
>>> plugins and fragments with AspectJ support". I select my project and
>>> enter the .zip file name into which to pack up everything and also
>>> selected to save the procedure as ant script and then pressed
>>> "Finish".
>>>
>>> That runs for a while and then for some - to me inexpliccable -
>>> reason that process terminates telling me that there were 14 compile
>>> errors. And no .zip is produced.
>>>
>>> ???? But this compiled and ran fine before! So where do these
>>> compile errors suddenly come from? And why does this recompile
>>> things in the first place? It should just export (i.e. pack and wrap
>>> up) things - at least that's what I would have expected...
>>>
>>> Any ideas?
>>>
>>> This is on eclipse 3.2.1 and I tried this with the same result using
>>> ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and also with
>>> 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest developer build
>>> provided).
>>>
>>> Michael
>>>
>>
Re: producing a "deployable plugin with AspectJ support" fails [message #595389 is a reply to message #67892] Fri, 17 November 2006 16:45 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
Grrrr - down by 18, i.e. still 980 errors. :-(

Why is this thing telling telling me almost 1000 times, that it is
unable to check, whether some javax.* or commonj.timers.* or
org.eclipse.hyades.logging.* or whatever other types my 25+ .jar
libraries contain is an instance of one of my interfaces??? The answer
to all these can easily be given and is "certainly not!". I urgently
need some way to stop this!

Michael


"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:ejknea$lp$1@utils.eclipse.org...
> Followed your advice, but using that generated build.xml I now have
> 998 errors! 8-O
>
> But at least I can now see, that it's apparently deeply diving down
> the type tree and produces tons of message like:
> <some.jar> [error] can't determine whether missing type
> org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance
> of <some type>
> etc. etc.
>
> That's apparently all stuff from some logging and other libraries that
> I am using. Seems, I have to work on my classpaths again (Aaargh!
> Compared with Java's constant classpath issues any DLL-hell I ever
> encountered was a piece of cake, but that's a different story...).
>
> But why does this behavior differ from normal compilation, i.e. why
> can I happily compile and even run things otherwise? Why is this
> export-build different? Puzzles over puzzles...
>
> Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
> analysis short at some level?
>
> Michael
>
>
> "Matt Chapman" <mpchapman@gmail.com> wrote in message
> news:ejkhf8$nus$1@utils.eclipse.org...
>> Hi Michael,
>>
>> That export wizard does the equivalent of the non-AspectJ version,
>> which is to generate a build.xml file and then run it, in order to
>> create the deployable plugin in the same way as in an automated PDE
>> build process. If you don't want this rebuild step, you could export
>> the project as a zip file and choose the contents manually.
>>
>> The log messages confirm that the AJC ant task is correctly being
>> used instead of the regular Javac task. But unfortunately it's not
>> telling us what those 14 compiler errors, plus it cleans up the
>> generated build.xml as you discovered.
>>
>> To diagnose this further, you should ensure you have an accurate
>> build.properties file for your plugin, and then right-click on the
>> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
>> Build File with AspectJ support". You should then have a build.xml
>> file which you can run, and see the output in the console.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Moser wrote:
>>> Maybe this helps analyzing this problem: the log shows a couple of
>>> error messages that read e.g.:
>>>
>>> ----------------------------
>>> ...
>>> C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>>> The following error occurred while executing this line:
>>> C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>> The following error occurred while executing this line:
>>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>>> while executing this line:
>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>> at
>>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>> at
>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>> at
>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>> Caused by: C:\Documents and
>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>> The following error occurred while executing this line:
>>> ...
>>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>>> a line "Nested Exception:" and then things seem to repeat from the
>>> beginning again. This continues about 3 times, except for the last
>>> segment which finally reads:
>>> ...
>>> --- Nested Exception ---
>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>> at
>>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at
>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>> at
>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>> at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>> at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>> at
>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>> at
>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>> at
>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>> at
>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>> at
>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>> ----------------------------
>>>
>>> Strange enough - there is no "build.xml" file (mentioned in lines 3
>>> & 4) in my project! Or is this file temporarily created only?
>>>
>>> Michael
>>>
>>>
>>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>>> news:ejjrla$c0o$1@utils.eclipse.org...
>>>> I have finalized a plugin (i.e. it works fine when I start it in
>>>> the runtime workbench) and so I would now like to convert it into
>>>> some distributable form.
>>>>
>>>> Thus, I started with File => Export.... and selected "Deployable
>>>> plugins and fragments with AspectJ support". I select my project
>>>> and enter the .zip file name into which to pack up everything and
>>>> also selected to save the procedure as ant script and then pressed
>>>> "Finish".
>>>>
>>>> That runs for a while and then for some - to me inexpliccable -
>>>> reason that process terminates telling me that there were 14
>>>> compile errors. And no .zip is produced.
>>>>
>>>> ???? But this compiled and ran fine before! So where do these
>>>> compile errors suddenly come from? And why does this recompile
>>>> things in the first place? It should just export (i.e. pack and
>>>> wrap up) things - at least that's what I would have expected...
>>>>
>>>> Any ideas?
>>>>
>>>> This is on eclipse 3.2.1 and I tried this with the same result
>>>> using ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and
>>>> also with 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest
>>>> developer build provided).
>>>>
>>>> Michael
>>>>
>>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #595399 is a reply to message #67912] Fri, 17 November 2006 17:51 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Compiling via the iajc ant task should be the same as via the builder in
Eclipse. Can you check that the ant task in the build.xml is referring
to the right version of the aspectj plugins - in case you have multiple
versions installed. Have you set any AspectJ compiler options in your
project's properties?

--Matt

Michael Moser wrote:
> Grrrr - down by 18, i.e. still 980 errors. :-(
>
> Why is this thing telling telling me almost 1000 times, that it is
> unable to check, whether some javax.* or commonj.timers.* or
> org.eclipse.hyades.logging.* or whatever other types my 25+ .jar
> libraries contain is an instance of one of my interfaces??? The answer
> to all these can easily be given and is "certainly not!". I urgently
> need some way to stop this!
>
> Michael
>
>
> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
> news:ejknea$lp$1@utils.eclipse.org...
>> Followed your advice, but using that generated build.xml I now have
>> 998 errors! 8-O
>>
>> But at least I can now see, that it's apparently deeply diving down
>> the type tree and produces tons of message like:
>> <some.jar> [error] can't determine whether missing type
>> org.eclipse.hyades.logging.events.cbe.CreateSituation is an instance
>> of <some type>
>> etc. etc.
>>
>> That's apparently all stuff from some logging and other libraries that
>> I am using. Seems, I have to work on my classpaths again (Aaargh!
>> Compared with Java's constant classpath issues any DLL-hell I ever
>> encountered was a piece of cake, but that's a different story...).
>>
>> But why does this behavior differ from normal compilation, i.e. why
>> can I happily compile and even run things otherwise? Why is this
>> export-build different? Puzzles over puzzles...
>>
>> Can one somehow tell AJDT to leave .jar files alone, i.e. cut this
>> analysis short at some level?
>>
>> Michael
>>
>>
>> "Matt Chapman" <mpchapman@gmail.com> wrote in message
>> news:ejkhf8$nus$1@utils.eclipse.org...
>>> Hi Michael,
>>>
>>> That export wizard does the equivalent of the non-AspectJ version,
>>> which is to generate a build.xml file and then run it, in order to
>>> create the deployable plugin in the same way as in an automated PDE
>>> build process. If you don't want this rebuild step, you could export
>>> the project as a zip file and choose the contents manually.
>>>
>>> The log messages confirm that the AJC ant task is correctly being
>>> used instead of the regular Javac task. But unfortunately it's not
>>> telling us what those 14 compiler errors, plus it cleans up the
>>> generated build.xml as you discovered.
>>>
>>> To diagnose this further, you should ensure you have an accurate
>>> build.properties file for your plugin, and then right-click on the
>>> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
>>> Build File with AspectJ support". You should then have a build.xml
>>> file which you can run, and see the output in the console.
>>>
>>> Regards,
>>>
>>> Matt.
>>>
>>> Michael Moser wrote:
>>>> Maybe this helps analyzing this problem: the log shows a couple of
>>>> error messages that read e.g.:
>>>>
>>>> ----------------------------
>>>> ...
>>>> C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:29:
>>>> The following error occurred while executing this line:
>>>> C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>>> The following error occurred while executing this line:
>>>> C:\JavaDevt\myproject\build.xml:195: The following error occurred
>>>> while executing this line:
>>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>>> at
>>>> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>>> at
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>>> at
>>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>>> Caused by: C:\Documents and
>>>> Settings\mmo\workspace\.metadata\.plugins\org.eclipse.pde.co re\temp\org.eclipse.pde.container.feature\build.xml:10:
>>>> The following error occurred while executing this line:
>>>> ...
>>>> (this continue about 3 times, every 2 or 3 "Caused by: ..." there is
>>>> a line "Nested Exception:" and then things seem to repeat from the
>>>> beginning again. This continues about 3 times, except for the last
>>>> segment which finally reads:
>>>> ...
>>>> --- Nested Exception ---
>>>> C:\JavaDevt\myproject\build.xml:170: compile errors: 14
>>>> at
>>>> org.aspectj.tools.ant.taskdefs.AjcTask.executeInOtherVM(AjcT ask.java:1414)
>>>>
>>>> at org.aspectj.tools.ant.taskdefs.AjcTask.execute(AjcTask.java: 1082)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTarge ts(SingleCheckExecutor.java:37)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor .executeTargets(EclipseSingleCheckExecutor.java:30)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
>>>> at
>>>> org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>>>> at org.apache.tools.ant.Task.perform(Task.java:364)
>>>> at org.apache.tools.ant.Target.execute(Target.java:341)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>>>> at
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:706)
>>>> at
>>>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:457)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:64)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:615)
>>>> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:356)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.runScript(FeatureExportOperation.java:307)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureExportOperatio n.doExport(FeatureExportOperation.java:196)
>>>> at
>>>> org.eclipse.ajdt.internal.core.exports.FeatureBasedExportOpe ration.run(FeatureBasedExportOperation.java:47)
>>>> at
>>>> org.eclipse.ajdt.internal.ui.wizards.exports.AJFeatureExport Job.run(AJFeatureExportJob.java:54)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>>> ----------------------------
>>>>
>>>> Strange enough - there is no "build.xml" file (mentioned in lines 3
>>>> & 4) in my project! Or is this file temporarily created only?
>>>>
>>>> Michael
>>>>
>>>>
>>>> "Michael Moser" <mmo@zurich.ibm.com> wrote in message
>>>> news:ejjrla$c0o$1@utils.eclipse.org...
>>>>> I have finalized a plugin (i.e. it works fine when I start it in
>>>>> the runtime workbench) and so I would now like to convert it into
>>>>> some distributable form.
>>>>>
>>>>> Thus, I started with File => Export.... and selected "Deployable
>>>>> plugins and fragments with AspectJ support". I select my project
>>>>> and enter the .zip file name into which to pack up everything and
>>>>> also selected to save the procedure as ant script and then pressed
>>>>> "Finish".
>>>>>
>>>>> That runs for a while and then for some - to me inexpliccable -
>>>>> reason that process terminates telling me that there were 14
>>>>> compile errors. And no .zip is produced.
>>>>>
>>>>> ???? But this compiled and ran fine before! So where do these
>>>>> compile errors suddenly come from? And why does this recompile
>>>>> things in the first place? It should just export (i.e. pack and
>>>>> wrap up) things - at least that's what I would have expected...
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> This is on eclipse 3.2.1 and I tried this with the same result
>>>>> using ajdt_1.4_for_eclipse_3.2.zip (i.e. the latest release) and
>>>>> also with 1.4.1.200611081052 for Eclipse 3.2 (i.e. the latest
>>>>> developer build provided).
>>>>>
>>>>> Michael
>>>>>
>>>>
>>
>
Re: producing a "deployable plugin with AspectJ support" fails [message #595403 is a reply to message #67933] Thu, 23 November 2006 16:30 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ejksq7$fiv$1@utils.eclipse.org...
> Compiling via the iajc ant task should be the same as via the builder
> in Eclipse. Can you check that the ant task in the build.xml is
> referring to the right version of the aspectj plugins - in case you
> have multiple versions installed.

I saved the a generated ant-script not to build.xml (since there is a
warning, that this name is reserved for PDE), but to a different name.
The file contents reads:

<?xml version="1.0" encoding="UTF-8"?>
<project default="plugin_export" name="build">
<target name="plugin_export">
<pde.exportPlugins destination="C:\JavaDevt\myproject"
exportSource="false" exportType="zip" filename="myproject.zip"
plugins="myproject" useJARFormat="false"/>
</target>
</project>

I can't see anything fishy but I also see no mentioning of aspectj here.
Maybe that's the reason?
A "build.xml" is temporarily created during the export, but removed at
the end of the build process.
As I said initially: the build process fails claiming 14 compile
errors - which could roughly be the number of to-be-weaved and now maybe
missing interfaces.

> Have you set any AspectJ compiler options in your project's
> properties?

No - I haven't modified any AspectJ option. I am using no project
specific settings and the system settings are the default ones.
I added three .jar files to the AspectJ inpath of this project, since I
need to weave aspects into these. That's the only adjustment re. aspects
that I did.

BTW: Again I downloaded and tried the latest build
(ajdt_1.5.0.200611221156) but no change.

Michael
Re: producing a "deployable plugin with AspectJ support" fails [message #595429 is a reply to message #67954] Tue, 28 November 2006 14:37 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Michael Moser wrote:
> I saved the a generated ant-script not to build.xml (since there is a
> warning, that this name is reserved for PDE), but to a different name.
> The file contents reads:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project default="plugin_export" name="build">
> <target name="plugin_export">
> <pde.exportPlugins destination="C:\JavaDevt\myproject"
> exportSource="false" exportType="zip" filename="myproject.zip"
> plugins="myproject" useJARFormat="false"/>
> </target>
> </project>
>
> I can't see anything fishy but I also see no mentioning of aspectj here.
> Maybe that's the reason?

How did you generate that build file? I haven't seen ones like that
before. Try this:

To diagnose this further, you should ensure you have an accurate
build.properties file for your plugin, and then right-click on the
plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant Build
File with AspectJ support". You should then have a build.xml file which
you can run, and see the output in the console.

This should then be the same as the build.xml generated during the
export. It should be much longer, and contain an "iajc" line.

--Matt
Re: producing a "deployable plugin with AspectJ support" fails [message #595503 is a reply to message #68020] Tue, 05 December 2006 10:18 Go to previous message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
"Matt Chapman" <mpchapman@gmail.com> wrote in message
news:ekhhjd$u1a$1@utils.eclipse.org...
> Michael Moser wrote:
>> I saved the a generated ant-script not to build.xml (since there is a
>> warning, that this name is reserved for PDE), but to a different
>> name.
>> The file contents reads:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <project default="plugin_export" name="build">
>> <target name="plugin_export">
>> <pde.exportPlugins destination="C:\JavaDevt\myproject"
>> exportSource="false" exportType="zip" filename="myproject.zip"
>> plugins="myproject" useJARFormat="false"/>
>> </target>
>> </project>
>>
>> I can't see anything fishy but I also see no mentioning of aspectj
>> here. Maybe that's the reason?
>
> How did you generate that build file?

That is the file created if one checks "Save as Ant script" on the
options tab of the Export dialog after choosing "File => Export... =>
Deployable plug-ins and fragments with AspectJ support".

> I haven't seen ones like that before. Try this:
>
> To diagnose this further, you should ensure you have an accurate
> build.properties file for your plugin, and then right-click on the
> plugin.xml or MANIFEST.MF file and select "PDE Tools > Create Ant
> Build File with AspectJ support". You should then have a build.xml
> file which you can run, and see the output in the console.
> This should then be the same as the build.xml generated during the
> export. It should be much longer, and contain an "iajc" line.

If I do the "PDE Tools > Create Ant Build File with AspectJ support" as
instructed there is a build.xml file created and that one looks indeed
VERY different from the above. However, for some strange reason this
build.xml is always removed as part of the above mentioned Export (i.e.
that export obviously triggers another build and that build seems to
delete the build.xml file). Really very odd!

I still haven't mastered to create anything deployable (plugin and/or
feature) with AspectJ support. And I am 100% sure that this used to work
under 3.1 (because I created earlier plugins using this method), but
obviously not any more under 3.2(.1) nor 3.3M3.

Michael
Previous Topic:AJDT 1.4.1 for Eclipse 3.2 released (and more!)
Next Topic:NPE when exporting a product with AspectJ support
Goto Forum:
  


Current Time: Mon Sep 15 09:29:27 GMT 2014

Powered by FUDForum. Page generated in 0.03170 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software