[Dominic Hanlan]

I have been using myEclipse 6.x for ages, finally upgraded to 7.0 .. great. The problem is that I have an old project which is an EJB project and deploys to a .sar file for JBoss. JBoss requires that there is a META-INF/jboss-services.xml file in the deployment. This exists in the project at the top level. Using ME6.x this deployed fine including the META-INF/*. Now using ME7.0 it only includes the compiled classes. How can I get the deployment to include the META-INF directory?

Regards

/Dominic

[Loyal Water]

Dominic,
I have asked the dev team to look into this issue. I’ll will get back to you as soon as I get a reply from them.

[Dominic Hanlan]

Its a tiny project, just to set up some scheduling which calls the main project. Do you wnat me to zip up the project files and send them?

[Riyad Kalla]

Dominic,

This is a high-priority bug we are working on fixing right now. Your test project would be much appreciated, can you use File > Export > General > Archive and zip all the projects related to the project up and PM them to Nipun for us?

Thank you!

[Riyad Kalla]

Dominic,
After further investigation it seems that the deployer is behaving as-designed… we package up your output contents from your EJB module and deploy them, standard package layout is to have META-INF at the top level of your *src* dir, which looks like:

+ /src
  + /META-INF
  + /com
    + /etc.

I just evaluated the MyEclipse 6.5 deployment code and don’t see that it’s changed in *that* scenario between 6.5 and 7.0 such that it was packaging your META-INF at the top level of your project still with an embedded source dir 1 level down…

Is moving your META-INF an option?

[Dominic Hanlan]

Moving the META dir is no problem, and having done so the project now deploys perfectly. Weird though !! Still thanks for the answer.

[Author]

Posts