Bugzilla – Full Text Bug Listing
| Summary: | Retire obsolete e4 bug components | ||
|---|---|---|---|
| Product: | Community | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | Bugzilla | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bsd, danail.branekov, dimitar.georgiev, eduard.bartsch, john.arthorne, Lars.Vogel, pwebster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Lars Vogel
I think e4-Resources still has some work that hasn't graduated (the Semantic File System). e4-Search had a new search implementation, though I'm not sure what the status is. It would be good to retire e4/UI and instead add an e4/Tools! @Eduard: are you still using e4 / Resources or has everything been migrated? @Dimitar - Is e4 / search still actively used? (In reply to comment #3) > @Dimitar - Is e4 / search still actively used? Sorry for the late reply, I was on an unplanned leave. Search is very actively used in already shipped SAP products and ones we build now. There have been some new use cases identified recently so i would expect commits in the near future. In addition Red Hat had expressed interest to use it in their stack and we had collaboration there - not sure how it winded up, I will check. In my view the original vision of graduating Search Console to the standard eclipse search is out of the question, at least at this point. So far we were unable to arrive at a common vision with Platform team on what the UI should look like. We also had rough time with making the product buildable by platform build. But maybe this is not a problem now as it is being invested in CBI. Getting Search Console in Eclipse SDK was the primary theme/epic on our plate. That turning out unfeasible is the reason you see no commits in git, and no traffic on the mailing list. Having said that, it is possible that there is a better way/place to evolve Search than e4. In any case my personal desire is for Search to remain an Eclipse project, in whatever form is needed/best. I am adding Danail to the bug. I would like to have a word with the people at SAP and see what their vision is. I will update you shortly on how that went. (In reply to comment #2) > @Eduard: are you still using e4 / Resources or has everything been migrated? I am still using e4 Resources project. SAP is now shipping a product that uses Semantic Resources component. Sorry, I have missed the mail on the e4 mailing list. Would it be possible to move the e4 resources to git and containue? @Dimitar you could move the e4 componets to its own project. I think Wayne Beaton would be the right contact. @Eduard I think Paul may be able to answer if e4 resource could be moved to Git. (In reply to comment #4) > In my view the original vision of graduating Search Console to the standard > eclipse search is out of the question, at least at this point. So far we > were unable to arrive at a common vision with Platform team on what the UI > should look like. We also had rough time with making the product buildable > by platform build. But maybe this is not a problem now as it is being > invested in CBI. I have updated what's in org.eclipse.e4.search to build with CBI based pom.xml, and we're still building it as part of 0.13. I think there's a fix to the org.eclipse.e4.releng eclipse-parent/pom.xml we use to not include the pom.xml files when calculating the bundle qualifier. PW (In reply to comment #5) > > Would it be possible to move the e4 resources to git and containue? Eduard, could you please open a bug against E4/UI, CC pwebster@ca.ibm.com, and list the CVS projects/modules that you would like in the e4 resources git repo? I'll try and make that happen soon. PW (In reply to comment #9) > > Eduard, could you please open a bug against E4/UI, CC > pwebster@ca.ibm.com, and list the CVS projects/modules that you would like > in the e4 resources git repo? I'll try and make that happen soon. I have moved the existing bug 377791 to E4/UI. So it sounds as if we could remove the following components: e4 / Runtime e4 / SWT e4 / TM Any objections? (In reply to comment #11) Ok I will archive those components tomorrow(Dec 13th 2012). -M. Done. These components have been archvied to z_archived/E4 . -M. |