I ended up having:
→ mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building osgi.enroute.examples.eval.bndrun 1.0.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[WARNING] The POM for
biz.aQute.bnd:bnd-export-maven-plugin:jar:3.4.0-SNAPSHOT is missing, no
dependency information available
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.109 s
[INFO] Finished at: 2016-10-12T00:26:21+02:00
[INFO] Final Memory: 7M/309M
[INFO]
------------------------------------------------------------------------
[ERROR] Plugin biz.aQute.bnd:bnd-export-maven-plugin:3.4.0-SNAPSHOT or one
of its dependencies could not be resolved: Could not find artifact
biz.aQute.bnd:bnd-export-maven-plugin:jar:3.4.0-SNAPSHOT -> [Help 1]
[ERROR]
after creating the bndrun sub-project. This is with maven 3.3.9. I had to
add
<pluginRepositories>
<pluginRepository>
<id>bnd-snapshots</id>
<url>
https://bndtools.ci.cloudbees.com/job/bnd.master/lastSuccessfulBuild/artifact/dist/bundles/
</url>
<layout>default</layout>
</pluginRepository>
</pluginRepositories>
to my parent POM to make it work.
Regards,
Milen
On Tue, Oct 11, 2016 at 4:23 PM, BJ Hargrave <hargr...@us.ibm.com> wrote:
> > Btw. I wonder if we could use a command line option for maven to auto
> update the runbundles. So you could describe to first run the build with
> mvn install. It fails and then run again with the option to replace the
> runbundles. That would be a lot simpler than copy pasting them.
>
> We just added support like this to the gradle plugin. It has resolve.XXX
> tasks which run the resolver for the XXX.bndrun file and then replaces the
> -runbundles statement in that bndrun file.
>
> https://github.com/bndtools/bnd/blob/master/biz.aQute.bnd.
> gradle/src/aQute/bnd/gradle/BndPlugin.groovy#L451-L497
>
> --
>
> BJ Hargrave
> Senior Technical Staff Member, IBM // office: +1 386 848 1781
> OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
> hargr...@us.ibm.com
>
>
>
> ----- Original message -----
> From: Christian Schneider <ch...@die-schneider.net>
> Sent by: osgi-dev-boun...@mail.osgi.org
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Cc:
> Subject: Re: [osgi-dev] OSGi enRoute Maven Testers wanted ...
> Date: Fri, Oct 7, 2016 2:20 PM
>
> Hi Peter,
>
> do you also provide the full source code of the finished project?
> I read most of the instructions and generally they look good but I think I
> personally would never try to recreate the whole project by hand by
> following the steps.
> I think most people would simply checkout the finished example and try and
> experiment with it while reading the sections of the tutorial.
>
> I also think the instructions for creating and adding the runbundles
> manually are quite tedious. I would rather leave the option to auto resolve
> on for the start and explain in a special section what the risks are and
> how to avoid these by "approving" the resolve manually like you describe
> now.
>
> Btw. I wonder if we could use a command line option for maven to auto
> update the runbundles. So you could describe to first run the build with
> mvn install. It fails and then run again with the option to replace the
> runbundles. That would be a lot simpler than copy pasting them.
>
> Christian
>
> On 06.10.2016 15:51, Peter Kriens wrote:
>
> I’ve created a tutorial for OSGi enRoute with Maven and vi. I am in need
> of some people that are willing to review this tutorial.
>
> The tutorial is at http://enroute.osgi.org/tutorial_eval/050-start.html
>
> You can find the Github source code at: https://github.com/osgi/
> osgi.enroute.site/tree/gh-pages/_tutorial_eval
>
> Please provide tool requests and issues or just mail me personally at
> peter.kri...@aqute.biz <peter.kri...@aqute.biz>.
>
> Any help would be HIGHLY appreciated. Kind regards,
>
> Peter Kriens
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
--
http://about.me/milen
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
