facebook

ME 2015 – Unable to deploy project due to Utility Module

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #351080 Reply

    minhur
    Member

    I am unable to deploy my project to a locahost jetty 7 server.

    The error I get is:
    Project facet Utility Module version 1.0 is not supported.

    Things to note:
    – My project doesn’t have Utility Module checked
    – Deployment works for Tomcat
    – Deployment doesn’t work for Jetty 7

    I’ll attach screenshots of the issue

    Attachments:
    You must be logged in to view attached files.
    #351120 Reply

    minhur,

    Can you please open Project/.settings/org.eclipse.wst.common.project.facet.core.xml file and remove the utility facet information (following two lines) from the file and then try deploying the application to Jetty Server. (To find the .settings folder of the project, you need to open Window > Show View > Other > General > Navigator.)

    <fixed facet=”jst.utility”/>
    <installed facet=”jst.utility” version=”1.0″/>

    If you are still facing issues, please attach the project configuration files (.project, .classpath, .settings folder and other .* files), so that we can try to replicate the problem at our end.

    Let us know how it works for you.

    #351155 Reply

    minhur
    Member

    I’ve tried that as well, but doing that stops the dependent project from deploying when main project is deployed.

    If I were to deploy the main project, I’m able to deploy it.
    When I link up other projects in the main project’s build path, it won’t let me deploy the main project because of utility in the external projects (which doesn’t happen in 2014)

    If i edit the facets.core.xml file to remove the utility facets, that deploys the main project, but it only deploys the main one, not the external ones.

    I don’t understand why ME 2015 won’t let me deploy my main project when the problematic facet (utility) is set for the external project.
    This issue doesn’t happen with ME 2014, and the facet.core.xml file looks identical in 2014 and 2015.

    #351156 Reply

    minhur
    Member

    I’m going to explain this better since I’ve found a workaround, but it’s more of a sign that this is indeed a bug.

    – create a main project that’s to be deployed
    – create 2-3 external projects that will need to be deployed when main project is deployed (but these projects don’t deploy by themselves)
    – main project should have Dynamic Web Moudule facet
    – external projects would have utility module facet
    – goto Deployment Assembly of main project, verify that it’s not trying to deploy the external projects (yet)
    – at this point project deploys correctly to a localhost jetty7 server
    – go back to deployment assembly of main project, add the external projects so they would deploy when main project is deployed.
    – (if the main project had already been deployed at this point, external projects deploy fine to localhost jetty7)
    – if main project hasn’t been deployed and jetty7 is empty, try deploying the main project (at this point it has external projects added in deployment assembly)
    – ME 2015 complains that utility module facet conflicts with dynamic web module

    The current workaround has been to deploy the main project WITHOUT adding any external projects to deployment assembly.

    once the main project is deployed, then I go to properties and add the external projects to the deployment assembly, which updates the already deployed main project with the external project deployments.

    again this is a new issue in 2015, this doesn’t happen with 2014 with exact same setup.

    #351169 Reply

    minhur,

    Thanks for the detailed steps. We could replicate the issue at our end and I have raised a bug report for our dev team to investigate on this issue.
    Sorry for the inconvenience caused.

    #351330 Reply

    minhur
    Member

    Thank you. Can the issue be escalated to be fixed with the next update?
    We’re currently blocked on development until this issue is fixed.

    #351346 Reply

    minhur,

    Our dev team is working on the fix for this issue and the fix will be out in the next MyEclipse 2015 CI update.

    Sorry for the inconvenience caused.

    #351655 Reply

    Brian Fernandes
    Moderator

    minhur,

    The MyEclipse 2015 CI 5 release includes a fix for this issue. Do let us know if it works for you.

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: ME 2015 – Unable to deploy project due to Utility Module

You must be logged in to post in the forum log in