From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | Vitalii Tymchyshyn <vit(at)tym(dot)im>, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, Pavel Raiskup <praiskup(at)redhat(dot)com>, Pavel Kajaba <pkajaba(at)redhat(dot)com>, Stephen Nelson <stephen(at)eccostudio(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Step towards being able to build on Linux (Pull request #435) |
Date: | 2016-01-21 22:04:37 |
Message-ID: | CAB=Je-FTF09QQV0_wkvn7pJopyhKbhKCb51JP8Ns2POYAhhzcA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
>So it seems like one solution to osgi is just to copy the sources into the project. These are all interfaces, and a minimal number of files, I think around 4
What's the problem with packaging OSGi interfaces as usual rpms (or
whatever is used for packaging)?
As for me, "copy&pasting <<minimal number of files, I think around
4>>" does not solve legal issues if there are any.
On top of that, exposing OSGi interfaces as part of pgjdbc.jar would
probably void OSGi compliance. The jar would just not load due to
invalid contents.
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2016-01-21 22:40:56 | Re: Step towards being able to build on Linux (Pull request #435) |
Previous Message | Dave Cramer | 2016-01-21 21:22:37 | Re: Step towards being able to build on Linux (Pull request #435) |