- This topic has 6 replies, 3 voices, and was last updated 19 years, 1 month ago by jnikolai.
-
AuthorPosts
-
sidereanMemberI have a fairly complicated project consisting of:
2 Java projects with dependant jars in my workspace. The jars they depend on are in a lib folder in each project:
JavaProject1
– src
– lib
– bin
JavaProject2
– src
– lib
– bin2 web projects
1 ejb projectI have created an EA project which has the EJB and 2 Web projects added as modules.
I added the 2 java projects to the EA project under Project References.
My systems configuration is as follows:
What operating system and version are you running? Windows XP, SP1
What Eclipse version and build id are you using? 3.0.1 (200409161125)
– Was Eclipse freshly installed for MyEclipse? Yes, two months ago
– Are any other external plugins installed? no
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*: 8
What MyEclipse version are you using? 200412061200-3.8.3
What JDK version are you using to run Eclipse? Sun JDK 1.4.2_06
What JDK version are you using to launch your application server? n/a
What application server are you using? JBoss 3.2.6 (not running)I have edited the Manifest.mf file in the EA project to include the names of the dependant project jars in the classpath:
Class-Path: javaproject1.jar javaproject2.jarFirst I attempted exploded deployment:
Result: Successfully deployed.
Details:
The first java project is packaged in a jar file and deployed just fine.
The second java project has a jar file that is 0 bytes in size.Then I attempted packaged deployment:
Result: Error during deployment: Exception deploying bin
Details:
No ear file was created.You’ll find the contents of my log file below.
Do you have any ideas what might be causing the problem?
Thanks, Donald!ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Dec 21, 2004 12:01:36.406
!MESSAGE Deploy failed
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Exception deploying bin
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.packageEARLibraries(Unknown Source)
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.redeploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.ą(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.access$2(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$5.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.runWithEvent(Unknown Source)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:266)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:206)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$8.handleEvent(ActionContributionItem.java:824)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)
Caused by: java.io.IOException: Exception deploying bin
at com.genuitec.eclipse.ast.deploy.core.DeploymentUtil.jarDependentProjects(Unknown Source)
… 40 more
Riyad KallaMemberDonald,
Thank you for the detailed description of your problem, it was very easy to follow.Right off the bat let us try some sanity checking. If you reorder the Java Projects as modules to the EA Project, does the deployment still fail on the 2nd project, or is it the 1st again? If its the 1st again, then there is something funky with that project. Double check its Source and Output directories. Try and rebuild it. Use the navigator view to double check the /bin dir infact as output in it and that Eclipse can read/write to it.
Let’s see where we go from here.
sidereanMemberI checked the problematic project and it had a folder in it called .settings. I don’t remember ever having seen this kind of folder in a plain java project so I deleted it, refreshed everything, redeployed and it worked. Terribly sorry for sucking up bandwidth.
Riyad KallaMemberNo problem, we are just glad its working now.
jnikolaiMember@support-rkalla wrote:
No problem, we are just glad its working now.
FYI – I was experiencing the exact same problem with my project. My setup is only slightly different:
– commons: java module
– services: ejb module
– web: web module
– ear: enterprise moduleThe problem was with the commons module. I had created a package within the commons module: org.foo.commons but did not put any classes into that package yet. Every time I tried an exploded deployment the resulting commons.jar was always empty (0 bytes). Which makes sense because there were currently no classes in the commons module yet. The packaged deployment failed with the above mentioned exception.
I did find a .settings directory in the commons workspace directory and promptly removed it as suggested by siderean. Unfortunately this didn’t solve my problem.
However, once I added a dummy class to the commons module; org.foo.commons.FooBar the deployment went through just fine.
Not sure if this is a bug/feature with eclipse or a MyEclipse problem… or what… Just thought the information may come in handy.
Riyad KallaMemberThank you fishfarp for the heads up.
jnikolaiMemberSorry, one more thing to note… Be sure to setup the Project References properly otherwise the deployment will be OK. For my project here are the Project References for each module:
– EAR: commons, services, web
– services: commons
– web: commons, services
– commons: <none>I THINK that is everything needed to reproduce the problem…
Let me know if you need any more information.It would be interesting to know if this is considered a problem with MyEclipse or Eclipse…
Thanks!
– John -
AuthorPosts