Do you think its worth creating an architype thats creates a project set-up
for embedded to run? Also i had originally specified the default location
of the servicemix.xml as src/main/resources/servicemix.xml?
P
On 8/4/06, Philip Dodds [EMAIL PROTECTED] wrote:
The new goal was something I
Just checked in that new goal for M2 plugin and also an archetype for a
simple embedded project - it is just the framework but I thought it would
get people started at least :)
Also I added a section on the JBI plugin page -
http://www.servicemix.org/site/maven-jbi-plugin.html
P
On 8/4/06,
Not sure for the artifact. There aren't much to do in an archetype, just
reference the
needed components afaik. And for the default location, i would have tought
to look
for it in the current dir, but ... it will be configurable on the plugin, so
it's not
a big deal.
On 8/4/06, Philip Dodds
Thx, will try it now :)
On 8/4/06, Philip Dodds [EMAIL PROTECTED] wrote:
Just checked in that new goal for M2 plugin and also an archetype for a
simple embedded project - it is just the framework but I thought it would
get people started at least :)
Also I added a section on the JBI plugin
The archetype doesn't do much but I wanted to try and keep it so people can
just create the basics - and mainly so I can reference it on the
documentation as a quick way to get a project in the right shape?
I wanted to keep the servicemix.xml in the resources as per the maven
standard directory
NP.
One thing though: is the runtime classpath of the maven project used to load
the servicemix configuration ?
I haven't tested it yet, but I have not seen anything about that in the
code.
If we don't do that, this goal will be nearly unusable.
On 8/4/06, Philip Dodds [EMAIL PROTECTED] wrote:
I'll double check but I think it is :)
P
On 8/4/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
NP.
One thing though: is the runtime classpath of the maven project used to
load
the servicemix configuration ?
I haven't tested it yet, but I have not seen anything about that in the
code.
If we
