[jira] Updated: (GERONIMO-2286) app client plan still uses Strings for dependency Module IDs

2007-09-25 Thread Donald Woods (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-2286:
---

Fix Version/s: (was: 2.0.x)

updated Fixed For field

> app client plan still uses Strings for dependency Module IDs
> 
>
> Key: GERONIMO-2286
> URL: https://issues.apache.org/jira/browse/GERONIMO-2286
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: application client, deployment
>Affects Versions: 1.1
>Reporter: Aaron Mulder
>Assignee: David Jencks
> Fix For: 2.0
>
>
> The geronimo-application-client schema has:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> That would typically be used like this:
>   
> tranql/tranql-connector/1.2/rar
>
> Everywhere else we've changed elements holding module IDs to be of 
> patternType, using separate groupId, artifactId, version, and type elements.  
> There's no reason external-rar should still be a single slash-delimited 
> String here (though internal-rar should be since it's presumably a path 
> within the JAR?).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-2286) app client plan still uses Strings for dependency Module IDs

2007-07-25 Thread Prasad Kashyap (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Kashyap updated GERONIMO-2286:
-

Fix Version/s: (was: 2.0-M5)
   2.0

> app client plan still uses Strings for dependency Module IDs
> 
>
> Key: GERONIMO-2286
> URL: https://issues.apache.org/jira/browse/GERONIMO-2286
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: application client, deployment
>Affects Versions: 1.1
>Reporter: Aaron Mulder
> Fix For: 1.x, 2.0
>
>
> The geronimo-application-client schema has:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> That would typically be used like this:
>   
> tranql/tranql-connector/1.2/rar
>
> Everywhere else we've changed elements holding module IDs to be of 
> patternType, using separate groupId, artifactId, version, and type elements.  
> There's no reason external-rar should still be a single slash-delimited 
> String here (though internal-rar should be since it's presumably a path 
> within the JAR?).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-2286) app client plan still uses Strings for dependency Module IDs

2006-12-07 Thread Vamsavardhana Reddy (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-2286?page=all ]

Vamsavardhana Reddy updated GERONIMO-2286:
--

Fix Version/s: 1.x
   2.0
   (was: 1.2)

> app client plan still uses Strings for dependency Module IDs
> 
>
> Key: GERONIMO-2286
> URL: http://issues.apache.org/jira/browse/GERONIMO-2286
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: application client, deployment
>Affects Versions: 1.1
>Reporter: Aaron Mulder
> Fix For: 1.x, 2.0
>
>
> The geronimo-application-client schema has:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> That would typically be used like this:
>   
> tranql/tranql-connector/1.2/rar
>
> Everywhere else we've changed elements holding module IDs to be of 
> patternType, using separate groupId, artifactId, version, and type elements.  
> There's no reason external-rar should still be a single slash-delimited 
> String here (though internal-rar should be since it's presumably a path 
> within the JAR?).

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