[jboss-jira] [JBoss JIRA] Commented: (JBREM-538) update remoting dist build to break out transports into individual jars

Tom Elrod (JIRA) jira-events at jboss.com
Fri Jul 21 01:22:11 EDT 2006


    [ http://jira.jboss.com/jira/browse/JBREM-538?page=comments#action_12339854 ] 
            
Tom  Elrod commented on JBREM-538:
----------------------------------

The 'dist.jars' ant target (which is a dependancy of 'dist' and 'dist.quick' targets), will create the following jars in the distribution lib directory:

jboss-remoting.jar - all the remoting classes.

jboss-remoting-core.jar (all the remoting classes minus transport and detection classes)
jboss-remoting-detection.jar (includes both jndi and multiplex implementation classes)
jboss-remoting-socket.jar (includes socket and sslsocket, client and server classes)
jboss-remoting-socket-client.jar (includes socket and sslsocket, client only classes)
jboss-remoting-http.jar (includes http and https, client and server classes)
jboss-remoting-http-client.jar (includes http,https, servlet, and sslservlet, client only classes)
jboss-remoting-servlet.jar (includes servlet and sslservlet, server only classes)
jboss-remoting-rmi.jar (includes rmi and sslrmi, client and server classes)
jboss-remoting-multiplex.jar (includes multiplex and sslmultiplex, client and server classes)

as well as 'servlet-invoker.war ' directory.

> update remoting dist build to break out transports into individual jars
> -----------------------------------------------------------------------
>
>                 Key: JBREM-538
>                 URL: http://jira.jboss.com/jira/browse/JBREM-538
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta2 (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Tom  Elrod
>             Fix For: 2.0.0.CR1 (Boon)
>
>
> Because of JBREM-496 would like to have several binaries output from the dist build.  Need one that includes everything from remoting.  Then need ones for the transports (including one just for the client).  So might look like:
> jboss-remoting-all.jar
> jboss-remoting-core.jar
> jboss-remoting-socket.jar
> jboss-remoting-socket-client.jar
> jboss-remoting-http.jar
> jboss-remoting-http-client.jar
> and so forth.

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

        



More information about the jboss-jira mailing list