[
https://issues.apache.org/activemq/browse/SMX4-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Anstey updated SMX4-30:
--------------------------------
Attachment: SMX4-30.patch
Here's the first stab at getting SMX3 components & samples into the SMX4
assembly.
Basically, the SMX3 components are downloaded separately and copied into the
<smx4-install>/hotdeploy directory. The samples are copied in from the SMX3
binary distribution.
I'm assuming that there will eventually be a top level components & samples
directory off of http://svn.apache.org/repos/asf/servicemix/. When those exist
we can move SMX4 over to using those.
> Build SMX4 Assembly
> -------------------
>
> Key: SMX4-30
> URL: https://issues.apache.org/activemq/browse/SMX4-30
> Project: ServiceMix 4
> Issue Type: Task
> Affects Versions: 4.0-m2
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 4.0-m2
>
> Attachments: SMX4-30.patch
>
>
> We need to add the JBI components and demos from SMX3 to the SMX4 assembly
> Phase 1
> Haul in components and demos from the SMX3 trunk with the exception of
> servicemix-lwcontainer and servicemix-wsn2005.
> * servicemix-lwcontainer is SMX3 specific and will not be supported for
> SMX4
> * servicemix-wsn2005 will not in supported for SMX4 in first release but
> will be added in a future release
> Phase 2
> When the SMX3 components are split out into separate projects, the SMX4
> assembly should be updated to pick them up from these projects rather than
> SMX3 trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.