Hi,
There's no need to modify any dependencies, all should be ok. Sorry for
the misunderstanding.
The main problem is that many libraries cannot be found in Maven
central. I thought we could use the latest binaries that are indeed in
Maven central, but after some experiments that's going to be a hard task
(*).
So I'm afraid we'll have to use repos at eclipse nexus. I'll concentrate
on that in the coming days. Will keep you posted.
Cheers,
Antonio
(*) netbinox, for instance, will have to be modified to adopt any higher
version of org.eclipse.osgi. APIs have changed a lot.
On 29/10/17 20:24, Matthias Bläsing wrote:
Hey Antonio,
Am Sonntag, den 29.10.2017, 10:48 +0100 schrieb Antonio:
Currently NetBeans modules define themselves the exact version of
third-party binaries, for instance:
netbinox depends on org.eclipse.osgi_3.9.1.v20140110-1610
and
o.eclipse.core.runtime depends on org.eclipse.core.runtime-3.7.0
Would it be a good idea to specify the exact versions of these in a
separate, centralized, release-specific version file?
I would not try to reinvent the wheel right now. What I would try:
- create a libs.eclipseruntime
- let that hold the binaries
- modify o.eclipse.core.runtime to depended on that
- modify nebinox to depend on that
or let netbinox depend on o.eclipse.core.runtime.
Greetings
Matthias
