[forge-issues] [JBoss JIRA] (FORGE-1102) Support detection/registration/installation of undeclared dependent facets

[Lincoln Baxter III (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lincoln Baxter III closed FORGE-1102.
-------------------------------------

         Assignee: Lincoln Baxter III
    Fix Version/s: 2.0.0.Alpha12
                       (was: 2.x Future)
       Resolution: Done


Done. Breaks Facets API.
                
> Support detection/registration/installation of undeclared dependent facets
> --------------------------------------------------------------------------
>
>                 Key: FORGE-1102
>                 URL: https://issues.jboss.org/browse/FORGE-1102
>             Project: Forge
>          Issue Type: Feature Request
>    Affects Versions: 1.3.3.Final
>            Reporter: Vineet Reynolds
>            Assignee: Lincoln Baxter III
>             Fix For: 2.0.0.Alpha12
>
>
> Based on FORGE-1101, facets that are not declared via {{@RequiresFacet}} may not be visible via {{Project.hasFacet()}} at the right time since the {{ProjectFactory}}'s registry may not process these facets in the right order. It would be a good idea to hint the {{ProjectFactory}} that a particular Facet may have to be registered.
> To explain further, the {{RestFacet}} does not declare any dependencies on the {{RestWebXmlFacet}} and the {{RestApplicationFacet}}. These facets are therefore not always detected via the {{project.hasFacet()}} invocations. 
> Declaring them as facets via a {{@RequiresOnlyOneFacet}} annotation could be one solution to ensure that only one facet within a group should be sufficient to satisfy the desired constraints on a Faceted type. Likewise, we could also add support for optional facets that are may be installed if possible, via a {{@OptionalFacets}} annotation.
> This would probably be better supported in 2.x instead of 1.x.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira