geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2653) Inconsistencies between jetty6-builder and tomcat6-builder plan.xml files
Date Fri, 05 Jan 2007 22:23:27 GMT

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

Jarek Gawor closed GERONIMO-2653.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0

The patch in http://issues.apache.org/jira/browse/GERONIMO-2671 resolved the inconsistencies
mentioned in this bug.


> Inconsistencies between jetty6-builder and tomcat6-builder plan.xml files
> -------------------------------------------------------------------------
>
>                 Key: GERONIMO-2653
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2653
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0
>            Reporter: Jarek Gawor
>             Fix For: 2.0
>
>
> 1) One of the plans has an extra dependency on the j2ee-server module while the other
does not (enough though both tomcat6/pom.xml and jetty6/pom.xml have dependency on j2ee-server
module):
> tomcat6-deployer/src/plan/plan.xml contains:
>                 <dependencies>
>                     <dependency>
>                         <groupId>${pom.groupId}</groupId>
>                         <artifactId>j2ee-server</artifactId>
>                         <type>car</type>
>                     </dependency>
>                     <dependency>
>                         <groupId>${pom.groupId}</groupId>
>                         <artifactId>tomcat6</artifactId>
>                         <type>car</type>
>                     </dependency>
>                 </dependencies>           
> while jetty6-deployer/src/plan/plan.xml contains:
>                 <dependencies>
>                     <dependency>
>                         <groupId>${pom.groupId}</groupId>
>                         <artifactId>jetty6</artifactId>
>                         <type>car</type>
>                     </dependency>
>                 </dependencies>
> 2) Also, jetty6-deployer specifies CXFBuilder: 
>         <references name="WebServiceBuilder">
>             <pattern>
>                 <name>CXFBuilder</name>
>             </pattern>
>             <pattern>
>                 <name>WebServiceBuilder</name>
>             </pattern>
>             <pattern>
>                 <name>UnavailableWebServiceBuilder</name>
>             </pattern>
>         </references>
> while tomcat6-deployer does not:
>         <references name="WebServiceBuilder">
>             <pattern>
>                 <name>WebServiceBuilder</name>
>             </pattern>
>             <pattern>
>                 <name>UnavailableWebServiceBuilder</name>
>             </pattern>
>         </references>
> It seems to me like these things should be consistent (unless of course there is a good
reason for it). 

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

        

Mime
View raw message