On Fri, May 2, 2008 at 7:55 AM, Tom Purcell
<[EMAIL PROTECTED]> wrote:
>
> Hello
>
> I've been trying to get SMX into an internal remote Maven repository. I have
> two questions. The first is what needs to be there in order to allow
> developers to build JBI components? The second is what is the easiest way to
> get those dependencies into the repositroy.
>
> It seems like there is a lot that needs to be there in order to have access
> to all the components so individual deploy-file commands would be tedious
> and error prone. I have actually solved my immediate problem by running the
> SMX build on the machine that hosts the repository but I know that will not
> always be possible and it seems like a sledge hammer type approach.
>
> Is there a better way? I'm thinking something like: mvn -PinternalRepo
> install
Here are a couple of options I've used before:
1) Build SMX without a local Maven repository. Upon successful build,
copy everything in the local Maven repo to your own internal remote
Maven repo.
2) Build SMX using the maven-dependency-plugin's go-offline goal and
it's outputFile property. This will put all files needed to build the
project into a directory of your choosing. The only exception to this
are the Maven plugins needed by SMX because the SMX root POM does not
specify a dependencyManagement element yet.
There are other ways, but these are the two I've used the most.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
