I have just checked in a fix to the root pom to exclude this dependency
from xfire-all.
On 8/1/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
As a workaround, you can copy the jar from
http://repo.mergere.com/maven2/stax/stax-api/1.0/stax-api-1.0.jar
to
~/.m2/java/xml/jsr173/1.0
I will l
will do :)
P
On 8/1/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
As a workaround, you can copy the jar from
http://repo.mergere.com/maven2/stax/stax-api/1.0/stax-api-1.0.jar
to
~/.m2/java/xml/jsr173/1.0
I will look at the problem now.
On 8/1/06, Philip Dodds <[EMAIL PROTECTED]> wrote
As a workaround, you can copy the jar from
http://repo.mergere.com/maven2/stax/stax-api/1.0/stax-api-1.0.jar
to
~/.m2/java/xml/jsr173/1.0
I will look at the problem now.
On 8/1/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
Great! Did you have any luck on the jsr171 dependency?
P
On 8/1/06
Great! Did you have any luck on the jsr171 dependency?
P
On 8/1/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I have just added some profiles to the build system.
They can be activated using
mvn -Dprofile=name
where name can be
container => servicemix-services, servicemix-jbi, service
I have just added some profiles to the build system.
They can be activated using
mvn -Dprofile=name
where name can be
container => servicemix-services, servicemix-jbi, servicemix-core
tooling => tooling
components => beanflow, components, common, soap, bpe, ...
assembly => samples,
