|Re: Why is "Non Java Projects" chp 18 so thin? [message #809569 is a reply to message #809436]
||Tue, 28 February 2012 21:15
| Henrik Lindberg
Registered: July 2009
On 2012-28-02 22:58, Dick Bridges wrote:|
> ICYC, I'm setting up Buckminster for a non-Java OSGi project.
> Specifically, something very similar to "nOSGi: a posix-compliant native
> OSGi framework" (link removed. Search for 'nOSGi').
> Query: Does the empty chapter 18 ("Non Java Projects") indicate there is
> more to come or that we should simply extend Buckminster to read the
> 'native' bundle manifests and there is no real need for a separate chapter?
> Can someone point me in the right direction?
> Regards, Dick
The idea was to show with examples how this would be done using some
sort of best/common practices. It turned out to be a major effort as we
at the time did not have any builds that were non-java.
Would love to include examples, but simply do not have the time to
Hope that explains why the chapter is thin.
Powered by FUDForum
. Page generated in 0.01633 seconds