Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Moved old bits (up to 3.5.5) to archive

On second thought:

ERROR   [0005] : No suitable provider for component org.eclipse.equinox.concurrent

:osgi.bundle/[1.0.300.v20120522-2049,1.0.300.v20120522-2049] was found in resourceMap file:/home/gravity/.hudson/jobs/Gravity_Update_Site/workspace/releng/com.remainsoftware.gravity.site.everything.feature/gravity.rmap
  ERROR   [0005] : No suitable provider for component 

etc..


Where can o.e.e.concurrent be found? I think I need to check it out and build from source?



On Tue, Jul 24, 2012 at 11:00 PM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
What do you mean with reference? 


On Tue, Jul 24, 2012 at 11:00 PM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:

No, I don't really need it it is just that our builds reference it and broke. It surprises me that no-one else ran into this.


On Tue, Jul 24, 2012 at 7:18 PM, Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx> wrote:
On 07/24/2012 06:42 PM, Wim Jongman wrote:
> Boom, there go our builds:
>
> http://ftp.halifax.rwth-aachen.de/eclipse/rt/ecf/3.5.5/site.p2
>
> I think we should leave a reference to all releases.

Do you need 3.5.5? We could keep current release - 1,2,N on
download.e.o. Keeping all releases is probably too much and I have no
idea how to create a reference (except for a simple readme.txt).

Markus

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev




Back to the top