You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/04/15 21:23:00 UTC

[jira] Created: (GERONIMO-1860) Tests of optional ConfigID components

Tests of optional ConfigID components
-------------------------------------

         Key: GERONIMO-1860
         URL: http://issues.apache.org/jira/browse/GERONIMO-1860
     Project: Geronimo
        Type: Test
    Security: public (Regular issues) 
  Components: general  
    Versions: 1.1    
    Reporter: Aaron Mulder
    Priority: Blocker
     Fix For: 1.1


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


[jira] Updated: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Chris Cardona (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]

Chris Cardona updated GERONIMO-1860:
------------------------------------

    Attachment: testplans.zip

I attached the plans I used for my tests (jar and configuration dependencies). The following are the results of my tests:

- deploy a module with a JAR dependency where only the artifactId is specified 

Result: Deployed
  Plan:
      ...
      <dep:dependency>
        <dep:artifactId>commons-modeler</dep:artifactId>
      </dep:dependency>
      ...

 - deploy a module with a JAR dependency where only the artifactId and groupId are specified 

Result: Deployed
  Plan:
      ...
      <dep:dependency>
        <dep:groupId>commons-modeler</dep:groupId>
        <dep:artifactId>commons-modeler</dep:artifactId>
      </dep:dependency>
      ...

 - deploy a module with a JAR dependency where the type is not specified 

Result: Deployed
  Plan:
      ...
      <dep:dependency>
        <dep:groupId>commons-modeler</dep:groupId>
        <dep:artifactId>commons-modeler</dep:artifactId>
        <dep:version>1.2-GERONIMO-SNAPSHOT</dep:version>
      </dep:dependency>
      ...

 - deploy a module with a JAR dependency where the version is not specified 

Result: Deployed
  Plan:
      ...
      <dep:dependency>
        <dep:groupId>commons-modeler</dep:groupId>
        <dep:artifactId>commons-modeler</dep:artifactId>
        <dep:type>jar</dep:type>
      </dep:dependency>
      ...

 - deploy a module with a configuration dependency where only the artifactId is specified 

Result: Not Deployed

    Error: Unable to distribute webapp.war: Unable to create
    configuration for deployment

        load of test/TestWebApp1/1.1/car failed

        Unable to resolve dependency /system-database//jar

  Plan:
      ...
      <dep:dependency>
        <dep:artifactId>system-database</dep:artifactId>
      </dep:dependency>
      ...

 - deploy a module with a configuration dependency where only the artifactId and groupId are specified 

Result: Not Deployed

    Error: Unable to distribute webapp.war: Unable to create
    configuration for deployment

        load of test/TestWebApp1/1.1/car failed

        Unable to resolve dependency geronimo/system-database//jar

  Plan:
      ...
      <dep:dependency>
        <dep:groupId>geronimo</dep:groupId>
        <dep:artifactId>system-database</dep:artifactId>
      </dep:dependency>
      ...

 - deploy a module with a configuration dependency where the type is not specified 

Result: Not Deployed (assumes it's a jar)

    Error: Unable to distribute webapp.war: Unable to create
    configuration for deployment

        load of test/TestWebApp1/1.1/car failed

        Error starting configuration gbean test/TestWebApp1/1.1/car

        Unable to resolve dependency
    geronimo/system-database/1.1-SNAPSHOT/jar

  Plan:
      ...
      <dep:dependency>
        <dep:groupId>geronimo</dep:groupId>
        <dep:artifactId>system-database</dep:artifactId>
        <dep:version>1.1-SNAPSHOT</dep:version>
      </dep:dependency>
      ...

 - deploy a module with a configuration dependency where the version is not specified 

Result: Deployed

    Deployed test/TestWebApp1/1.1/car @
    http://CCARDONA:8080/testwebapp1

  Plan:
      ...
      <dep:dependency>
        <dep:groupId>geronimo</dep:groupId>
        <dep:artifactId>system-database</dep:artifactId>
        <dep:type>car</dep:type>
      </dep:dependency>
      ...


> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>     Priority: Blocker
>      Fix For: 1.1
>  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


[jira] Commented: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=comments#action_12414506 ] 

Jacek Laskowski commented on GERONIMO-1860:
-------------------------------------------

ccardona is in geronimo-contributor group. He can assign the issue to himself whenever he intend to. Welcome Chris!

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  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


[jira] Commented: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=comments#action_12376300 ] 

Aaron Mulder commented on GERONIMO-1860:
----------------------------------------

I was just thinking...  We're going to need a number of simple sample apps for this.  I think we should check them all in (perhaps to the sandbox) and maybe set up batch / shell scripts to run the deployments and check for errors.  It can be a manual process for now (start server, kick off script, stop server) and maybe someone can make an itest-like module out of it later.  But it would be nice to build up a supply of simple test apps for this purpose.

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>     Priority: Blocker
>      Fix For: 1.1

>
> 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


[jira] Updated: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
     [ 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

        

[jira] Assigned: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Paul McMahan (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]

Paul McMahan reassigned GERONIMO-1860:
--------------------------------------

    Assign To:     (was: Paul McMahan)

Chris Cardona (ccardona) has been investigating this JIRA and has provided some test results.   He requested karma so that it could be assigned to him but AFAIK his request has not been granted yet.  Since I am not personally looking at this issue and cannot assign it to Chris I am marking it as unassigned.

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  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


[jira] Assigned: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]

Matt Hogstrom reassigned GERONIMO-1860:
---------------------------------------

    Assign To: Paul McMahan

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>     Priority: Blocker
>      Fix For: 1.1

>
> 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


[jira] Updated: (GERONIMO-1860) Tests of optional ConfigID components

Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]

Matt Hogstrom updated GERONIMO-1860:
------------------------------------

    Fix Version: 1.1.1
                     (was: 1.1)

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1.1
>  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