I think it is a good idea! But it might be hard to test eventually.
Cheers,
Thomas
Guillaume Nodet wrote:
I'd like to start a discussion on splitting the container and
components release cycles. What do people think about that ?
Should we keep the container and all the components in a
If we go that way, how could we deal with the examples ?
I guess they would either require the use to download the components,
or be available on a separate distros (and thus have their own
release cycle too).
Ideally needs a Maven-like dependency management system for components
so that you
Hey, I've just svn up and I have the following problem when bulding:
[INFO] Surefire report directory:
c:\java\servicemix\clean\deployables\bindingcomponents\servicemix-jms\target\surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException: Unable to
create test class
Fix XSD schema locations for use with plain spring
--
Key: SM-992
URL: https://issues.apache.org/activemq/browse/SM-992
Project: ServiceMix
Issue Type: Task
Reporter: Guillaume
I was mainly refering to the examples that come with the default
distribution of
ServiceMix. The distribution includes the container, some configuration files,
JBI components and demos.
We already have some TCK stuff which is not available publicly due to the need
for an NDA mainly.
But I
[
https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39602
]
Jim ogunjimi commented on SM-960:
-
Dear Jira,
I tried to use the example orcherstration with jsr181 but it is not
