[GRADLE-1441] Add Web Facet to Module iml Created: 14/Mar/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Stéphane Toussaint Assignee: Unassigned
Resolution: Won't Fix Votes: 5


 Description   

It would be good to have the Web Facet section automatically generated in the .iml file for war module.

The Web Facet section looks like this :

<component name="FacetManager">
  <facet type="web" name="Web">
    <configuration>
      <descriptors>
        <deploymentDescriptor name="web.xml" url="file://$MODULE_DIR$/src/main/webapp/WEB-INF/web.xml" />
      </descriptors>
      <webroots>
        <root url="file://$MODULE_DIR$/src/main/webapp" relative="/" />
      </webroots>
      <sourceRoots>
        <root url="file://$MODULE_DIR$/src/main/java" />
        <root url="file://$MODULE_DIR$/src/main/resources" />
      </sourceRoots>
    </configuration>
  </facet>
</component>

deploymentDescriptor and root elements are subject to customization based on layout configuration.

 Comments   
Comment by Stéphane Toussaint [ 15/Mar/11 ]

Hi,

I have an implementation of this at git://github.com/stoussaint/gradle.git in the idea-webfacet branch.

I've not that work on the best way to provide facet properties and build the facet node. Seem's to need a Factory here. Happy to talk about that point.

The next step is to provide Artifact support in .ipr (War/Exploded War for instance). This will give the ability to only reload resources in Idea (within Tomcat local run for instance).

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:55:36 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.