For the branding question, I don't think we have any doc on that yet.
You can have a look at the following bundle which does what you want:
   https://svn.apache.org/repos/asf/servicemix/smx4/nmr/trunk/branding/

2009/5/6 Moloney, Tim M <[email protected]>:
>
> I'm trying to build from the current trunk (revision 772252) and I get
> several exceptions.  I've attached the output of the build.  I ran the
> build with the following tool versions.
>
>  bash> java -version
>  java version "1.6.0_13"
>  Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
>  Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
>  bash> mvn -v
>  Maven version: 2.0.9
>  Java version: 1.6.0_13
>  OS name: "linux" version: "2.6.27.21-170.2.56.fc10.i686" arch: "i386"
> Family: "unix"
>
> The errrors are the same even after I attempted to build with an empty
> local Maven repository.  Please let me know if I left out any needed
> info.
>
> On a side note, how can I change the branding of Karaf?  I see that it
> uses a properties file to get the information but I don't understand
> where to put this properties file and what to name
> <<karaf-r772252-build-output.txt>> it.
>
> Thanks.
>
>
> Tim Moloney                            The reasonable man adapts himself
> to
> ManTech Real-time Systems Laboratory   the world; the unreasonable one
> persists
> 2015 Cattlemen Road                    in trying to adapt the world to
> himself.
> Sarasota, FL  34232                    Therefore all progress depends on
> the
> (941) 377-6775 x208                    unreasonable man. - George
> Bernard Shaw
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to