- This topic has 8 replies, 3 voices, and was last updated 14 years, 10 months ago by kosmi.
-
AuthorPosts
-
kosmiMemberHello,
there seems to be a problem with the
com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder. The automatic deployment after changing a sourcefile of a webproject copies class and configuration files of required projects into the projects .war.The Configuration of my eclipse is set to:
“Ignore dependent Java projects” but the DeploymentBuilder shows the behaviour of the
“Use Smart Deployment for dependent Java projects” configuration. (see http://www.myeclipseide.com/documentation/quickstarts/webprojects/#dependent_projects)All my Projects are converted from MyEclipse 7.0.
Here is the Info about my actual MyEclipse Version (sorry, I’ve xxxxed some information):*** Date: Freitag, 11. September 2009 15:50:53 Deutschland
<SNIP, please use MyEclipse > Installation Summary > Installation Details in the future>
support-shaliniMemberkosmi,
I could not replicate this issue. I tested with MyEclipse Tomcat and the deployment worked as expected.
Can you give some more information to replicate this issue?
1. What are your installation details? You can get them from MyEclipse > installation Summary > Installation Details.
2. What is the server that you are using?
3. Are you deploying in packaged mode or in exploded mode?
kosmiMemberHello support-shalini,
thanks for your quick reply, I’m out of office today , so i can’t send you my installation details.
I will give it to you on monday morning.The answers to your other questions are easy to give:
2.What is the server that you are using?
JBoss 4.2.1.GA with JBoss Portal 2.7.1 – Seperatly in the filesystem under c:/dev/server/…3. Are you deploying in packaged mode or in exploded mode?
I use the exploded mode
kosmiMemberHello support-shalini,
here is the missing information:*** Date:
Montag, 14. September 2009 09:27 Uhr MESZ** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.5
Build id: 7.5-20090609*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 7.5
Build id: 7.5-20090609Eclipse Project SDK
Version: 3.4.2.R342_v20090122-7O7S7GApJ3_vCyk7ETmsfcmjhz0eHnqw7MIjk9Vdhe4Ic
Build id: M20090211-1700Eclipse Plug-in Development Environment
Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS
Build id: M20090211-1700Eclipse Platform
Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
Build id: M20090211-1700Eclipse Graphical Editing Framework GEF
Version: 3.4.2.v20090218-1145-67728084A56B4I233613552
Build id: 200902181337Eclipse RCP
Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63
Build id: M20090211-1700Eclipse Java Development Tools
Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI
Build id: M20090211-1700Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\DEV\MYECLIPSE75.BSP\myeclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\DEV\MYECLIPSE75.BSP\myeclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\DEV\MYECLIPSE75.BSP\myeclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-exitdata
d5c_44
-configuration
C:\DEV\MYECLIPSE75.BSP\myeclipse\configuration
-data
C:\DEV\MYECLIPSE75.BSP\workspaceBSP
-vm
C:\DEV\MYECLIPSE75.BSP\jre\bin\javaw.exe
Riyad KallaMemberkosmi,
We need a bit of clarification as to what is going on here…
there seems to be a problem with the
com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder. The automatic deployment after changing a sourcefile of a webproject copies class and configuration files of required projects into the projects .war.Correct, that’s the way it is meant to behave by default.
The Configuration of my eclipse is set to:
“Ignore dependent Java projects” but the DeploymentBuilder shows the behaviour of the
“Use Smart Deployment for dependent Java projects” configuration. (see http://www.myeclipseide.com/documentation/quickstarts/webprojects/#dependent_projects)Can you share some screenshots of what you mean? Project’s can have their own deployment settings that override the workspace defaults if selected, and the workspace can have it’s own default settings. I don’t understand the reference to “DeploymentBuilder” here. I think some screenshots of what your settings are and which screens you are referring to would clear up exactly what’s going on and what we need to test very quickly for us.
kosmiMemberHello support-rkalla,
my Projectspecific settings are not configured to override the general configuration settings.
Anyhow here are the requested Screenshots:
Settings of a WebProject and Myeclipse :
[url=http://www.turboimagehost.com/p/2123910/webProj.jpg.html][img=http://s1d4.turboimagehost.com/t/2123910_webProj.jpg][/url] [url=http://www.turboimagehost.com/p/2123911/myeclipsePref.jpg.html][img=http://s1d4.turboimagehost.com/t/2123911_myeclipsePref.jpg][/url][URL=http://www.turboimagehost.com/p/2123910/webProj.jpg.html][/URL] [URL=http://www.turboimagehost.com/p/2123911/myeclipsePref.jpg.html][/URL]
My hint to the DeploymentBuilder means that he could be responsible for the behaviour. With MyEclipse 7.1 the deployment works as expected. In 7.5 the DeploymentBuilder is new – now the behavior is incorrect.
My suggestion is that the Method webProjectBuildDelta() which searches all dependencys does not care for the user settings. Unfortunately your source code is not
OpenSource, so I’m not able to have a closer look on the problem.Greets,
DanielThanks to TurboImageHost for [URL=http://www.turboimagehost.com]Free Image Hosting[/URL]
kosmiMemberHello support-rkalla,
i didn’t hear anything from you – are you able to reproduce the issue or
do you need some further information?In the meantime we downgraded to MyEclipse 7.1.1, which works properly..
.. but we want to use 7.5.Thanks for your help,
Daniel
kosmiMemberHello support-rkalla
we solved the problem. I think there is missing a possibility to disable the
Export/Deployment of related Projects
under WebProject->Properties->Java Build Path->Projects,
like it is possible for jars under WebProject->Properties->Java Build Path->Order and Export.In our Project structure we have several webprojects and many Java projects
which are needed by the webprojects. We deploy these projects as jar files
into different lib folders of the server. This job is done by an ant task.The jar projects are attached to the webprojects by the jar files under
WebProject->Properties->Java Build Path->Order and Export with
an unchecked export check box.
Some of these Projects are also attached to the webproject via
WebProject->Properties->Java Build Path->Projects.This causes the new deployment builder to deploy the classes
of these projects into the webproject .war too. Therefore the project
is deployed twice – once as .class files in the war and secondly as .jar in a
lib folder of the server. The server crashes on start up.The old deployment builder doesn’t care about these projects,
everything worked as supposed.I assume that the new deployment builder looks into the .project
files of the Java projects. There he finds an entry
<name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name>
which causes this instance of the deployment bulider to deploy the
Java Project into the webproject of the calling deployment builder.If I remove the entry in the .project file and everything works fine.
Unfortunately, after some starts of MyEclipse, the entry is rewritten
by MyEclipse.As solution I can remove the project dependency’s under
WebProject->Properties->Java Build Path->Projects.
But why is Eclipse deploying these projects into my server? I think
there must be a possibility to tell eclipse not to deploy these projects.Are my assumptions correct?
Best wishes,
Daniel
kosmiMemberHello Forum,
I posted my last assumptions a copy in my blog. The genuitec guys saw my post and
confirmed the problem.
I want to say thanks for the fast assistance!
Here’s what Ryad said:
“We dug into this and you found a bug that we are working on fixing right now for 8.0M1.First there is a bit of confusion around how to filter out the deployment of dependent projects — historically we’ve always done this by going to Project Properties > MyEclipse > Web > Deployment, then in the top group select “Ignore” — so the dependent Java projects won’t be deployed with your Web projects. Our deployer doesn’t key off the Export and Order settings at this time.
However, it looks this works on initial deploy, but if any classes change in the dependent projects during dev time, the hot-sync process will fire and then deploy the dependent Java projects. That is the bug we are fixing.
So if you guys aren’t working on those Java projects and are just working with the Web Project, using the “Ignore” setting will do exactly what you need it to do and will stop putting those additional classes on the server.
Then in 8.0M1 we’ll get it fixed so it never ignores that setting for you.
Thanks for the heads up!”
Thanks,
Daniel -
AuthorPosts