Hi
One of the side effects of moving from 1.x to 2.x is that the build
system has been reorganised to make Servicemix more modular (or
something). This also seems to mean that having a servicemix-2.x
project in Eclipse based on the top level directory of the bundle
doesn't work anymore. When I run "maven eclipse" the .project
and .classpath files in jbi, base, core, jaxws, xfire, components and
assembly are updated, but not the ones in the servicemix base
directory itself.
Given the way that Eclipse works, this means that I will need to
create projects for all of these components separately. Was this
intended, or just an unforeseen outcome? I could create a workspace
based on the servicemix-2.0.1 directory, and so create all of the
project internally and update their dependencies, but this is less
straightforward than the way in which 1.x was structured, and would
mean that my own projects would have to appear in the same workspace.
I'll go with the flow, if I can see where the flow is going :-)
Many thanks
Nathan
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering -
+34-638-083-675, +34-91-201-2139 - AIM NathanCisco - [EMAIL PROTECTED]
