On Wed, Sep 11, 2013 at 9:19 AM, Minto van der Sluis <[email protected]> wrote:
> See below, > > Regards, > > Minto > > Op 10-9-2013 22:21, Reto Bachmann-Gmür schreef: > > On Mon, Sep 9, 2013 at 1:49 PM, Reto Bachmann-Gmür <[email protected]>wrote: > >> I suggest to create svn folders: >> >> - provisioning/sling >> - provisioning/karaf >> >> with partialbundlelists respective features. Ideally we could then >> later get the karaf-maven-plugin to produce partial bundlelists too or >> unify the things in another way. But given the usage of clerezza features >> both in a sling-launcher as well as in a karaf environment I think it makes >> sense to provide both. >> > > Started creating a partialbundlelist I found it very tedious to type > dependencies without the support of the IDE so I decided to go straight for > the better approach and tweak the karaf-maven-plugin to gnerated the > partail bundlelists. > > In /trunk/provisioning/tools/karaf-maven-plugin/ there is now a version > of the plugin that has the addional createSlingPartialBundleList > configuration param. > > It can be used like this (modified version from what the > karaf-feature-archetype created): > > <build> > <pluginManagement> > <plugins> > <plugin> > > <groupId>org.apache.clerezza.provisionig.tooling</groupId> > <artifactId>karaf-maven-plugin</artifactId> > <version>3.0.0.RC1</version> > <extensions>true</extensions> > </plugin> > </plugins> > </pluginManagement> > <plugins> > <plugin> > <groupId>org.apache.clerezza.provisionig.tooling</groupId> > <artifactId>karaf-maven-plugin</artifactId> > <configuration> > <startLevel>50</startLevel> > <aggregateFeatures>true</aggregateFeatures> > <resolver>(obr)</resolver> > <checkDependencyChange>true</checkDependencyChange> > <failOnDependencyChange>false</failOnDependencyChange> > <logDependencyChanges>true</logDependencyChanges> > > <overwriteChangedDependencies>true</overwriteChangedDependencies> > > <includeTransitiveDependency>false</includeTransitiveDependency> > > <createSlingPartialBundleList>true</createSlingPartialBundleList> > </configuration> > </plugin> > </plugins> > </build> > > I checked out the sling-launchpad side of things and I hope (and think > that) I haven't broken the karaf side. > > Are you sure a change like this will be accepted by the karaf community? > When looking from a puristic perspective I can image them not being > interested in sling based artifacts. > I can't be sure of course. I think denying it would have less to do with purism tahn with locking up. If not we can keep it where it is. The sling plugin also produces both formats but I prefer the karaf plugin. > > > Tomorrow I'll start creating some features in /trunk/provisioning > (thinking at rdf-core, rdf-jena, rdf-scala, shell). > > @Minto do you happen to have already such feature generating poms that > could be used to try out the tweaked plugin version? > > I do have a pom but it does not generate a features.xml. My features.xml > for Clerezza was had crafted. Another note is that I am using karaf 2.3.2 > for which the maven features plugin was still a separate plugin (not part > of karaf-maven-plugin). > Ok. Reto
