geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Cabrera (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1860) Tests of optional ConfigID components
Date Sun, 16 Jul 2006 07:06:22 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]

Alan Cabrera updated GERONIMO-1860:
-----------------------------------

    Fix Version/s: 1.1.x
                       (was: 1.1.1)

Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all
probability, 1.1.2 patch.

> Tests of optional ConfigID components
> -------------------------------------
>
>                 Key: GERONIMO-1860
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>             Project: Geronimo
>          Issue Type: Test
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>            Priority: Blocker
>             Fix For: 1.1.x
>
>         Attachments: testplans.zip
>
>
> Before shipping 1.1, we need to make sure the following things work:
>  - deploy a web app with no Geronimo plan
>  - redeploy the same web app with no Geronimo plan
>  - deploy a module with a Geronimo plan with an environment with no configId
>  - redeploy the same module with a Geronimo plan with an environment with no configId
>  - deploy a module with a Geronimo plan with no type in the configId
>  - redeploy the same module with a Geronimo plan with no type in the configId
>  - deploy a module with a Geronimo plan with no version in the configId
>  - redeploy the same module with a Geronimo plan with no version in the configId
>  - deploy a module with a Geronimo plan with no type or version in the configId
>  - redeploy the same module with a Geronimo plan with no type or version in the configId
>  - deploy a module with a Geronimo plan with only an artifactId in the configId
>  - redeploy the same module with a Geronimo plan with only an artifactId in the configId
>  - deploy a module with a JAR dependency where only the artifactId is specified
>  - deploy a module with a JAR dependency where only the artifactId and groupId are specified
>  - deploy a module with a JAR dependency where the type is not specified
>  - deploy a module with a JAR dependency where the version is not specified
>  - deploy a module with a configuration dependency where only the artifactId is specified
>  - deploy a module with a configuration dependency where only the artifactId and groupId
are specified
>  - deploy a module with a configuration dependency where the type is not specified
>  - deploy a module with a configuration dependency where the version is not specified

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message