And it was not documented because I never had the time to test it (and document it.) I only wrote it :-(
Kind regards,
Peter Kriens
> On 23 Nov 2016, at 22:48, Raymond Auge <raymond.a...@liferay.com> wrote:
>
> I never said it was documented! ;)
>
> https://github.com/bndtools/bnd/blob/master/biz.aQute.resolve/src/biz/aQute/resolve/BndrunResolveContext.java#L167
>
> <https://github.com/bndtools/bnd/blob/master/biz.aQute.resolve/src/biz/aQute/resolve/BndrunResolveContext.java#L167>
>
> On Wed, Nov 23, 2016 at 4:45 PM, Milen Dyankov <milendyan...@gmail.com
> <mailto:milendyan...@gmail.com>> wrote:
> not according to http://bnd.bndtools.org/chapters/825-instructions-ref.html
> <http://bnd.bndtools.org/chapters/825-instructions-ref.html> :)
>
>
> On Wed, Nov 23, 2016 at 10:42 PM, Raymond Auge <raymond.a...@liferay.com
> <mailto:raymond.a...@liferay.com>> wrote:
> -distro: is an existing bnd instruction implemented by Peter.
>
> - Ray
>
> On Wed, Nov 23, 2016 at 4:22 PM, Milen Dyankov <milendyan...@gmail.com
> <mailto:milendyan...@gmail.com>> wrote:
> I didn't want to highjack the "Component being activated twice?" thread so
> decided to start a new one.
>
> Regarding the "-distro" instruction - I don't seam to find any info about it.
> I assume this was simply an idea Ray proposed and not something that exist
> and need to be improved? Please correct me if I'm wrong and point me to some
> documentation.
>
> From the previous discussion I get the impression the really missing piece in
> bnd / repos / resolver is the concept of dependency scope "provided" that we
> know from Maven. If I understood Ray's intention correctly this is what he
> generally wants to have with "-distro" except it's on repository level
> instead of bundle level. I'm just curios if it wouldn't make more sense to
> have both. That is so in addition to what Ray proposes one could say for
> example:
>
> --runprovided: <blach>
>
> which would mean use those to resolve build time but do not
> package/deploy/include them in anything that would go in runtime.
>
> Best,
> Milen
>
>
> --
> http://about.me/milen <http://about.me/milen>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
>
> --
> Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
> Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance)
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
>
> --
> http://about.me/milen <http://about.me/milen>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
>
> --
> Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
> Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance)
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
