[seam-issues] [JBoss JIRA] Moved: (SEAMCONFIG-13) The princess-rescue example does not follow the Seam example naming convention

Jason Porter (JIRA) jira-events at lists.jboss.org
Tue Apr 19 17:12:44 EDT 2011


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

Jason Porter moved SEAMXML-41 to SEAMCONFIG-13:
-----------------------------------------------

              Project: Seam Config (fixed)  (was: Seam Config)
                  Key: SEAMCONFIG-13  (was: SEAMXML-41)
             Workflow: Seam Workflow  (was: GIT Pull Request workflow )
    Affects Version/s:     (was: 3.0.0.CR4)
          Component/s: Build Infrastructure
                           (was: Build Infrastructure)
        Fix Version/s:     (was: 3.0.0.Final)


> The princess-rescue example does not follow the Seam example naming convention
> ------------------------------------------------------------------------------
>
>                 Key: SEAMCONFIG-13
>                 URL: https://issues.jboss.org/browse/SEAMCONFIG-13
>             Project: Seam Config (fixed)
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Jozef Hartinger
>            Assignee: Shane Bryzak
>
> The following naming convention is enforced:
> * folder name in the seam distribution - <module name>-<example name> (e.g. rest-tasks)
> * example final name (context path after deployment) - should be the same as above (e.g. rest-tasks)
> * maven artifactId - seam-<module name>\-example\-<example name> (e.g. seam-rest-example-tasks)
> The princess-rescue example should declare "config-princess-rescue" as its final name.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list