Project Export's build logs are deleted, so it's impossible to know what went wrong [message #895488] |
Fri, 13 July 2012 05:12  |
Eclipse User |
|
|
|
I'm trying to export my scout project, the export fails, an error message such as this can be found in eclipse's log:
org.eclipse.scout.sdk.ui.wizard.AbstractWorkspaceWizard$P_PerformFinishOperation.run(AbstractWorkspaceWizard.java:131)
exception during perfoming finish on wizard page 'org.eclipse.scout.sdk.ui.internal.wizard.export.ExportScoutProjectWizard'.
with asociated stack trace:
org.eclipse.core.runtime.CoreException: could not export server war file
at org.eclipse.scout.sdk.ui.internal.extensions.export.ServerExportEntryHandler.createModule(ServerExportEntryHandler.java:54)
at org.eclipse.scout.sdk.ui.internal.wizard.export.ExportScoutProjectWizard.performFinish(ExportScoutProjectWizard.java:55)
at org.eclipse.scout.sdk.ui.wizard.AbstractWorkspaceWizard$P_PerformFinishOperation.run(AbstractWorkspaceWizard.java:121)
at org.eclipse.scout.sdk.jobs.OperationJob.run(OperationJob.java:105)
at org.eclipse.scout.sdk.jobs.AbstractWorkspaceBlockingJob.doRun(AbstractWorkspaceBlockingJob.java:61)
at org.eclipse.scout.sdk.jobs.AbstractWorkspaceBlockingJob.run(AbstractWorkspaceBlockingJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.eclipse.core.runtime.CoreException: Compilation errors occurred during the operation. A zip file containing the build logs has been generated and placed at f:\temp\LOCALT~1\dir1092557095920430265warExportBuildDir/WEB-INF/eclipse
at org.eclipse.scout.sdk.operation.export.ExportServerWarOperation.buildServerProduct(ExportServerWarOperation.java:165)
at org.eclipse.scout.sdk.operation.export.ExportServerWarOperation.run(ExportServerWarOperation.java:91)
at org.eclipse.scout.sdk.ui.internal.extensions.export.ServerExportEntryHandler.createModule(ServerExportEntryHandler.java:50)
... 6 more
Unfortunately, the zip file mentioned in the stack trace does not exists and there is no other information concerning the failed build process to be found.
Interestingly, I can export a blank scout project just fine (but all the logs from temp are still deleted).
More interestingly, I can export the failing project through eclipse's export wizard (as an eclipse application, which is hardly useful in this case).
|
|
|
|
|
|
|
|
Re: Project Export's build logs are deleted, so it's impossible to know what went wrong [message #895862 is a reply to message #895860] |
Mon, 16 July 2012 07:16   |
Eclipse User |
|
|
|
I'm using windows 7
Finally, I've worked it out.
As suspected, I've had an error in one of my .java files which was not detected by eclipse, but was detected by eclipse compiler... don't really know how it was possible. It looked like this:
@Mixins(EntityFragment.Mixin.class)
^^^^^^^^^^^^^^
The type EntityFragment is ambiguous
EntityFragment is an inner type, defined at the same level as the annotated class. I can't see how how could that cause a problem, since there was no public or package-level type with that name anywhere.
Anyway, after fixing all 'type xxxx is ambiguous' errors the build finally succeeded.
In order to get that simple build error message I had to:
- setup a separate workspace,
- check out scout's sources,
- define run configuration,
- setup a breakpoint at ExportServerWarOperation.java:165,
- run scout in debug mode
- import my projects into debugged instance's workspace
- export project from debugged instance - failed due to PermGen space erors
- increase PermGen space & friends through run config's cmdline options,
- restart, try exporting again
- navigate to builddir in temp folder,
- extract the log files,
- search all of them for errors
Quite a lot of work to get a build error msg.
I think it would be great if export wizard could output all the errors and warnings from compiler into eclipse's log, or at least console. That would've saved so much time.
I would like to thank the community, especially Andreas, for all the help offered.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04044 seconds