Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 459574

Summary:	Migrate Build to use the CBI
Product:	[Tools] andmore	Reporter:	David Carver <d_a_carver>
Component:	releng	Assignee:	Kaloyan Raev <kaloyan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	kaloyan
Version:	unspecified
Target Milestone:	0.5-RC1
Hardware:	PC
OS:	Mac OS X
See Also:	https://github.com/eclipse/andmore/pull/104
Whiteboard:
Bug Depends on:	458597, 483513
Bug Blocks:

Description David Carver

2015-02-10 11:23:08 EST

Currently we are using a Tycho and Maven, but it isn't using the CBI so we aren't currently setup for handling release artifacts and signing the components.  To make this easier, we should really leverage the common build infrastructure at eclipse.

https://wiki.eclipse.org/CBI

This needs to happen before we release a 0.5-M1

Comment 1 David Carver

2015-03-15 22:21:43 EDT

Do not need to be able to do an M1 release.

Comment 2 Eclipse Genie

2015-12-03 09:48:12 EST

GitHub Pull Request 104 created by [kaloyan-raev]
https://github.com/eclipse/andmore/pull/104

Comment 3 Kaloyan Raev

2015-12-15 06:27:24 EST

I did some progress in this direction. We have a Nexus repository where we publish the snapshot builds [1].

We need to wait for version 1.1.3 of the eclipse-jarsigner-plugin to sign the Andmore plugins. See the discussion in the cbi-dev list [2].

[1] https://repo.eclipse.org/content/repositories/andmore-snapshots
[2] https://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01560.html

Comment 4 Kaloyan Raev

2016-05-18 06:23:47 EDT

The new Eclipse JarSigner won't be deployed in the Eclipse infrastructure for Neon. Therefore, we will just sign the Andmore bundles as usual and the installation won't work for Indigo and older versions.