[ http://jira.jboss.com/jira/browse/JBREM-11?page=history ]
Tom Elrod updated JBREM-11:
----------------------------
Description:
Need to create seperate CVS module for JBoss Remoting. Requires proper modules
are included as well as seperate build.
Have started by creating the jboss-remoting module within the CVSROOT/module
file. The problem is, remoting now references a lot of other modules and third
party. This includes aop, transaction, server, and system. Before going
further, should break out code that is not core framework, so can trim down the
remoting standalone module. Right now, might as well get the whole jbosss AS,
since is not much bigger than remoting.
Moving this to lower priority, since won't be able to get to it before 1.0.1
alpha release. For that release will build remoting distro by hand.
was:
Need to create seperate CVS module for JBoss Remoting. Requires proper modules
are included as well as seperate build.
Have started by creating the jboss-remoting module within the CVSROOT/module
file. The problem is, remoting now references a lot of other modules and third
party. This includes aop, transaction, server, and system. Before going
further, should break out code that is not core framework, so can trim down the
remoting standalone module. Right now, might as well get the whole jbosss AS,
since is not much bigger than remoting.
Moving this to lower priority, since won't be able to get to it before 1.0.1
alpha release. For that release will build remoting distro by hand.
Environment:
Priority: Critical (was: Optional)
Version: 1.0.1 final
Fix Version: 1.2.0 beta
> Create seperate JBoss Remoting module in CVS
> --------------------------------------------
>
> Key: JBREM-11
> URL: http://jira.jboss.com/jira/browse/JBREM-11
> Project: JBoss Remoting
> Type: Task
> Components: general
> Versions: 1.0.1 final
> Reporter: Tom Elrod
> Assignee: Tom Elrod
> Priority: Critical
> Fix For: 1.2.0 beta
>
>
> Need to create seperate CVS module for JBoss Remoting. Requires proper
> modules are included as well as seperate build.
> Have started by creating the jboss-remoting module within the CVSROOT/module
> file. The problem is, remoting now references a lot of other modules and
> third party. This includes aop, transaction, server, and system. Before
> going further, should break out code that is not core framework, so can trim
> down the remoting standalone module. Right now, might as well get the whole
> jbosss AS, since is not much bigger than remoting.
> Moving this to lower priority, since won't be able to get to it before 1.0.1
> alpha release. For that release will build remoting distro by hand.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
