Mailing-List: contact dev-help@netbeans.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@netbeans.incubator.apache.org
Subject: Re: Integrating with complex third-party software
To: dev@netbeans.incubator.apache.org
References: <E5D28FC9-A630-4C5C-8B95-65793445690B@vieiro.net>
 <1508873401.9216.7.camel@doppel-helix.eu>
From: Antonio <antonio@vieiro.net>
Message-ID: <539e9925-4dea-5f36-8d81-bc381eeb22ff@vieiro.net>
Date: Tue, 24 Oct 2017 22:42:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1508873401.9216.7.camel@doppel-helix.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
archived-at: Tue, 24 Oct 2017 20:43:32 -0000

Hi,

I've been trying to find something similar to Wildfly BOMs [1] in the 
eclipse nexus repository without success. Maybe they don't have them. 
I'd like to see a well defined set of module versions 
(o.eclipse.core.net X.Y.Z, o.eclipse.core.runtime A.B.C, etc.), that are 
tested to work together. I'll keep trying.

I think NetBeans should also provide these BOMs for different releases, 
so you could include the "NetBeans 8.2 Platform BOM", or the "NetBeans 
9.1 Platform BOM" in your project and forget about individual module 
versions. Something to think about in the future.

I'll keep you posted of my findings.

Cheers,
Antonio

[1] https://github.com/wildfly/boms

For wildfly-javaee7-10.0.1
https://github.com/wildfly/boms/blob/wildfly-javaee7-10.0.1.Final/pom.xml

For wildfly-javaee7-9,0.1
https://github.com/wildfly/boms/blob/jboss-javaee-7.0-wildfly-9.0.1.Final/pom.xml


On 24/10/17 21:30, Matthias Bläsing wrote:
> Hey,
> 
> Am Dienstag, den 24.10.2017, 19:35 +0200 schrieb Antonio Vieiro:
>> I’m currently reviewing one of the “o.eclipse.core.*” modules and I
>> can’t find a binary, so I should either upgrade or downgrade it.
>>
>> I was wondering if we should either upgrade or downgrade the binaries
>> of _all_ of the “o.eclipse.core.*” modules at once. In order to avoid
>> subtle bugs that may arise if we choose versions coming from
>> different Eclipse releases.
> 
> there was some talk, that eclipse hosts its artifacts in its own
> repository (Emilian raised that already):
> 
> https://repo.eclipse.org/content/groups/releases/
> 
> They obviously setup a nexus instance for themselves:
> 
> https://repo.eclipse.org/
> 
> The solution could be, that the DownloadBinaries task is modified to
> fetch binaries from multiple maven repositories.
> 
> What do the others think?
> 
> Greetings
> 
> Matthias
>