Hello all.
I've a quick question on the use of the maven-dependency plugin. Why are you
using a custom installation location when you can actually access the karaf
dependency.
What I've been doing in the past is to directly pull the maven dependency e.g.
via this snippet:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>unpack</id>
<phase>generate-resources</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>org.apache.karaf</groupId>
<artifactId>apache-karaf</artifactId>
<type>tar.gz</type>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
The entire adjustment of the file system towards /opt/... can be handled
afterwards in your target build folder.
Regarding the question on the OS integration. I've done some after install
scripting to start karaf and install the already integrated wrapper.
Nevertheless, it os also required to link all service files to the appropriate
places.
Kind regards,
- Christoph
On Jul 15, 2013, at 7:05 PM, Roedl Lukas wrote:
> Hi!
>
> I'm also working on packaging Karaf for distribution on Debian.
> You can have a look at my current implementation
> athttp://dev.arcsmed.at/homer.core/trac/browser/trunk/distribution/linux
>
> But I have to say that I didn't do much for a good integration with the OS.
> So I'm very interested in the developments going on in that field!
>
> best regards,
>
> Lukas
> ________________________________________
> Von: Ioan Eugen Stan [[email protected]]
> Gesendet: Montag, 15. Juli 2013 17:42
> An: [email protected]
> Betreff: Re: system wide Karaf under Debian
>
> Hello JB,
>
> Thanks.I wanted to know who else is interested in this and to clarify
> some things.
>
> Regards,
