| Project Export's build logs are deleted, so it's impossible to know what went wrong [message #895488] |
Fri, 13 July 2012 05:12  |
 Filip Paczyński
Messages: 4
Registered: July 2012 |
Junior Member |
|
|
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).
Best regards - Filip Paczyński
|
|
|
|
| Re: Project Export's build logs are deleted, so it's impossible to know what went wrong [message #895519 is a reply to message #895504] |
Fri, 13 July 2012 07:20  |
Filip Paczyński
Messages: 4
Registered: July 2012 |
Junior Member |
|
|
Thanks for your fast reply.
I'm using eclipse 4.2 with scout 3.8 updated from the nightly, but I've encountered the same problem on eclipse 3.7 with scout 3.8.
My help -> about eclipse -> installation details
are attached in installation_details.txt
Projects in my workspace involved in the build process:
pl.biz.concept.erp.client
pl.biz.concept.erp.qi4j
pl.biz.concept.erp.server
pl.biz.concept.erp.shared
pl.biz.concept.erp.ui.swing
pl.biz.concept.erp.ui.swt
pl.biz.concept.libs
pl.biz.concept.qi4jtools
pl.biz.concept.scout.addons.client
pl.biz.concept.utils
The product files were migrated from eclipse 3.7 with scout 3.8.
I took extra care to compare with product files from newly-generated simple scout app and customize them accordingly (i.e. jetty)
Product file and config.ini are attached.
And the best would be a screenshot of every page in the export wizard. To answer the following questions:
- I've attached them to this post
Does the export path contain any special characters?
- No, the path is ok - the empty scout project exports just fine to that path.
Which product are you trying to export?
- /pl.biz.concept.erp.server/products/production/erp-server.product
attached
Which client product is included in the export?
- Swing or none - does not matter. Swing client alone exports just fine. Server alone fails.
Do you export also a RAP server?
- No, I have currently no rap target installed.
Are you trying to export a war or an ear file?
- Currently WAR, but ear fails in the same way.
Of course I might have messed something up. The problem is that I have no way to know what, because the logs are deleted.
Best regards - Filip Paczyński
|
|
|
|
| Re: Project Export's build logs are deleted, so it's impossible to know what went wrong [message #895822 is a reply to message #895661] |
Mon, 16 July 2012 04:22 |
Filip Paczyński
Messages: 4
Registered: July 2012 |
Junior Member |
|
|
Thank for the patch.
Unfortunately - the logs are still deleted...
I could actually see the builddir disappearing from temp.
This is what I did step by step:
1. Downloaded Eclipse for scout developers
2. checked the version numbers - they were ok
3. replaced the two plugin files
4. started eclipse with -clean
5. downloaded missing plugins necessary for the build to succeed - rayo & guava
6. restarted exlipse
7. tried to export the project again
I am pretty sure that eclipse loaded the replaced plugin files correctly, because the "Scout SDK" plugin is listed in the "Eclipse Installations Details" window as having no signature - as opposed to any other plugin from Eclipse Scout Project.
Maybe I should setup a separate eclipse workspace for scout debugging, That way I will be able to set a breakpoint somewhere and keep the build logs from being deleted...
Best regards - Filip Paczyński
|
|
|
|
| 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 |
Filip Paczyński
Messages: 4
Registered: July 2012 |
Junior Member |
|
|
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.
Best regards - Filip Paczyński
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02496 seconds
] 
Search
Help
Register
Login
Home
