Hi Jean-Baptiste, thank's for your response.
I'll give it a try with the maven-metadata-local.xml since calling a REST Service (I assume you shortened the long term by RS) might become difficult from the RPM process on an environment where JAVA_HOME might not be standardized set across all environments. Many greets and kind regards, Christoph On 19.04.2012, at 16:04, Jean-Baptiste Onofré wrote: > Hi Christoph, > > The "efficient" way is to mimic the maven-deploy-plugin. > > The maven-deploy-plugin (in deploy or deploy-file goals) create all the maven > metadata (pom.properties, maven-metadata.xml, etc) that Archiva use. > > On karaf-maven-plugin (trunk), I implemented the generation of > maven-metadata-local.xml. > > Archiva provide a RS interface to upload artifact and generate the metadata > on the fly (using the RS provided info). > > Regards > JB > > On 04/19/2012 03:37 PM, Christoph Emmersberger wrote: >> Dear all, >> >> I'm looking currently for a convenient way of using the >> features-maven-plugin to create an offline repo and deploy it as an RPM. >> >> What I've already achieved is the creation of the RPM package and the >> inclusion of the created bundels (see also my feature-repo target folder) >> >> [cemmersb@localhost repo-snapshot]$ tree >> . >> |-- commons-io >> | `-- commons-io >> | |-- 1.4 >> | | |-- commons-io-1.4.jar >> | | |-- commons-io-1.4.jar.md5 >> | | |-- commons-io-1.4.jar.sha1 >> | | |-- maven-metadata.xml >> | | |-- maven-metadata.xml.md5 >> | | `-- maven-metadata.xml.sha1 >> | |-- maven-metadata.xml >> | |-- maven-metadata.xml.md5 >> | `-- maven-metadata.xml.sha1 >> `-- org >> `-- apache >> |-- karaf >> | `-- assemblies >> | `-- features >> | |-- enterprise >> | | `-- 2.2.2 >> | | `-- enterprise-2.2.2-features.xml >> | `-- standard >> | `-- 2.2.2 >> | `-- standard-2.2.2-features.xml >> `-- servicemix >> `-- bundles >> `-- org.apache.servicemix.bundles.ehcache >> |-- 2.5.0_1 >> | |-- maven-metadata.xml >> | |-- maven-metadata.xml.md5 >> | |-- maven-metadata.xml.sha1 >> | |-- org.apache.servicemix.bundles.ehcache-2.5.0_1.jar >> | |-- org.apache.servicemix.bundles.ehcache-2.5.0_1.jar.md5 >> | `-- org.apache.servicemix.bundles.ehcache-2.5.0_1.jar.sha1 >> |-- maven-metadata.xml >> |-- maven-metadata.xml.md5 >> `-- maven-metadata.xml.sha1 >> >> My RPM does basically nothing else than copying the repo into the >> Archiva repository data folder that I chose for that operation. >> Generally the processing works well whey Karaf adds Archiva as a >> repository, features and bundles can be installed that way. The only >> missing point for me is, that Archiva complains about incomplete >> metadata, which is correct since there is no pom file included to the >> feature-repo. >> >> Archiva screen output: >> >> <dependency> >> <groupId></groupId> >> <artifactId></artifactId> >> <version>2.0-rc3-SNAPSHOT</version> >> <type></type> >> </dependency> >> >> Artifact metadata is incomplete. >> >> Does anyone of you know about a convenient way, to include the pom files >> as well? >> >> Many thanks and kind regards, >> >> Christoph > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
