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

2006-07-16 Thread Alan Cabrera (JIRA)
 [ 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] Updated: (GERONIMO-1860) Tests of optional ConfigID components

2006-06-12 Thread Matt Hogstrom (JIRA)
 [ 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



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

2006-05-17 Thread Chris Cardona (JIRA)
 [ 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:
  ...
  
commons-modeler
  
  ...

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

Result: Deployed
  Plan:
  ...
  
commons-modeler
commons-modeler
  
  ...

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

Result: Deployed
  Plan:
  ...
  
commons-modeler
commons-modeler
1.2-GERONIMO-SNAPSHOT
  
  ...

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

Result: Deployed
  Plan:
  ...
  
commons-modeler
commons-modeler
jar
  
  ...

 - 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:
  ...
  
system-database
  
  ...

 - 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:
  ...
  
geronimo
system-database
  
  ...

 - 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:
  ...
  
geronimo
system-database
1.1-SNAPSHOT
  
  ...

 - 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:
  ...
  
geronimo
system-database
car
  
  ...


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