For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 11 replies, 4 voices, and was last updated 21 years, 11 months ago by
.
-
Posts
-
Hello,
I am trying to deploy an EAR to JBoss. My project is structured as follows:
ProjectEAR
ProjectWAR
ProjectUtilityJARProjectUtilityJAR is a project with several utility classes. ProjectWAR references the ProjectUtilityJAR via “Project References” in Eclipse and it is a Required project on the build path. This allows Eclipse to find the output files from that project and include them when building ProjectWAR.
ProjectEAR is set up to reference both ProjectUtilityJAR (though it shouldn’t be necessary) and ProjectWAR in the Project References section. ProjectWAR has also been added to ProjectEAR as a “module project”.
I have configured ProjectEAR to deploy to JBoss, but when it does, only the contents of ProjectWAR are deployed. Without the classes of ProjectUtilityJAR deployed to the WEB-INF/classes folder of ProjectWAR, the application won’t run. I would have expected the MyEclipse deploy feature to traverse referenced projects and deploy their output contents to the default output folder of the referencing project.
Is there a way around this without resorting to an Ant script?
aoneal,
We appologize for you running into this current shortcomming of the deployment tool. Unfortunately this functionality of dependant project deployment won’t be available until MyEclipse 2.8.Currently you might be able to get around it by using linked resources in MyEclipse which in 2.7 our deployment tool will honor by following the link and deploying the linked resource (very much like a sym link in *nix).
@aoneal wrote:
Is there a way around this without resorting to an Ant script?
Now that I look into this some more, perhaps an Ant script is the best approach after all. I can have it package the JAR and deploy to ProjectWAR (as would likely happen for real deployment), and then MyEclipse will pick it up as one of the libs.
Thank you for your prompt reply. I’ll probably test the link approach as well.
That certainly sounds like a good solution as well. Hopefully it will hold you over until our deployment tool becomes flexbile enough to take over for you.
Thank you for being patient.
I just ran into this problem with one of our new developers. I was trying to deploy into Tomcat 4. The developer that was having this problem was using Eclipse 2.1.2 with MyEclipse 2.7.
I’m surprised to read that this feature is not supported yet, as I have been successfully deploying to Tomcat 4 a project with a reference to another project using Eclipse 2.1.1 and MyEclipse 2.6.200 for several months. When I installed the same tools on our new developer’s machine, the problem was instantly solved.
(Edit:)
It occurs to me that I should clarify some: I do use an Ant script to compile all of my linked project source files into WEB-INF/classes prior to deployment. When I deploy, everything in WEB-INF/classes is copied into my Tomcat directory. This is the behavior that was broken in 2.7. Is this the same problem as reported above or a new bug?Thank you,
Terry
Terry,
Our deployment tool prior to 2.7 simply copied the contents recursively from your webroot to the webapps directory in Tomcat. Now with 2.7 we will do the same thing, but we honor links in Eclipse such that we will follow the links and deploy the target file. So from the sounds of things, if you are using the Ant script, deployment should work the same for your team with ME 2.6 and 2.7.The problem above is different in that people need MyEclipse to deploy dependant Projects along with the deployed project, while the problem you mention is just related to the class files in the WEB-INF/classes directory.
Riyad,
Thank you for the reply. The behaviour I was seeing from ME2.7/Eclipse 2.1.2 was that even after compiling the source files from my other project into the WEB-INF/classes directory, they would not be deployed into Tomcat with the class files from the main project.
The problem was solved by running ME2.6 with Eclipse 2.1.1.
Thanks,
Terry
Terry,
Sorry, I understand you better now. This is most likely (I’m 95% sure) caused by the project not refreshing itself to *see* the new files so when our deployment tool runs, it only sees the pre-Ant files and deploys them. I’m not aware of a good workaround for this…Riyad,
Thanks for the followup. For now we’re fine with Eclipse 2.1.1 and ME2.6, so it’s not an immediate concern. It will probably keep us from upgrading until it is fixed. Would this be a bug to report to the Eclipse team or to you guys?
Thanks,
Terry
Hi,
Sorry to keep dragging this out, but I did a little more testing this afternoon.
Okay, so I went ahead and installed (via the install/update perspective) ME2.7 w/ Eclipse 2.1.1 to test whether my deployment problems would still be occurring with that configuration. The point of this was to see if Eclipse 2.1.2 or ME2.7 was causing the problems that I reported yesterday.
I can report that the upgrade from 2.6.2 to 2.7 broke the deployment. I reverted my version back to 2.6.2 and deployed fine without any other changes.
Hope this is helpful.
Terry
Terry,
This *is* odd indeed, but if it worked for you before, we’ll do our best to make it work for you again. I’ll forward this on to S/M and see what they think it might be.I tried to reproduce this with the following:
1) created a web project and deployed it to Tomcat 5
2) created another java project and created a few java files in it
3) copied the class files from the second project into the WEB-INF/classes directory of the first project
4) noticed that all copied classes were deployed to the web app’s WEB-INF/classes dir on the server.The only difference is that I didn’t use Ant, so the problem might be one of:
1)When you run your Ant script, do you have the external tool builder set to refresh the workspace at completion?
2) Do you have the ‘Perform build automatically on resource modification’ under(Window > Preferences > Workbench) checked?
