Re: [cross-project-issues-dev] status and outlook for Kepler M1

[David M Williams <david_williams@xxxxxxxxxx>]

>There was one "real" error
found 
>Missing requirement: org.eclipse.jubula.feature.feature.group 1.3.0.201208151047
requires 'org.eclipse.help.ui [3.5.2,4.0.0)' but it could not be found

>help UI has moved to version 4.0 so Jubula will need to adjust version
ranges. (not sure what you use if for, but there were API changes related
to Lucence changes (as previously announced on this list) so not sure if
you can have a >"wide" range, or need to adjust your Java
code. 

Meant to give these bugs, if that helps
you (but, got distracted before I pasted) ... good luck. 

355562         org.eclipse.help
and org.eclipse.help.base should not depend on lucene jar...    
    
350103         [Help]
Remove extension point luceneSearchParticipants        

340563         [Help][Search]
Update Lucene 2.9.1 to the latest version 





From:      
 David M Williams/Raleigh/IBM@IBMUS
To:      
 cross-project-issues-dev@xxxxxxxxxxx,

Date:      
 08/17/2012 01:30 PM
Subject:    
   [cross-project-issues-dev]
status and outlook for Kepler M1
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Its not great. Time to pay attention.
There are still 32 projects not enabled so the aggregation build doesn't
get too far. 

I tried disabling a few features or repositories to see if the aggregator
could get through a build but eventually gave up fearing I'd be at it all
afternoon. 

But, seemed like CDT and Graffiti were two "core" missing ones.

These are the ones I disabled temporarily (in some cases one features,
in others whole repo) 
ptp.b3aggrcon 
webtools.b3aggrcon 
emf-cdo.b3aggrcon 
jubula.b3aggrcon 
linuxtools.b3aggrcon 

There was one "real" error found 
Missing requirement: org.eclipse.jubula.feature.feature.group 1.3.0.201208151047
requires 'org.eclipse.help.ui [3.5.2,4.0.0)' but it could not be found

help UI has moved to version 4.0 so Jubula will need to adjust version
ranges. (not sure what you use if for, but there were API changes related
to Lucence changes (as previously announced on this list) so not sure if
you can have a "wide" range, or need to adjust your Java code.


The following still have not enabled their contribution. (note, I have
removed Jetty contribution, as they have stated they do not plan on participating
in Kepler Sim. Release). 

actf.b3aggrcon 
amp.b3aggrcon 
cdt.b3aggrcon 
dltk.b3aggrcon 
emf-query2.b3aggrcon 
emft-ecoretools.b3aggrcon 
emft-eef.b3aggrcon 
emft-egf.b3aggrcon 
emft-emffacet.b3aggrcon 
epp-mpc.b3aggrcon 
gmp-gmf-tooling.b3aggrcon 
gmp-graphiti.b3aggrcon 
gyrex.b3aggrcon 
jwt.b3aggrcon 
koneki.b3aggrcon 
m2e.b3aggrcon 
m2m-qvtoml.b3aggrcon 
mat.b3aggrcon 
mdt-modisco.b3aggrcon 
mdt-papyrus.b3aggrcon 
mft.b3aggrcon 
mylyn-docs-intent.b3aggrcon 
pdt.b3aggrcon 
recommenders.b3aggrcon 
rtp.b3aggrcon 
scout.b3aggrcon 
soa-bpel.b3aggrcon 
soa-sca.b3aggrcon 
subversive.b3aggrcon 
tcf.b3aggrcon 
tm.b3aggrcon 
virgo.b3aggrcon 

Thanks all, 

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev