Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 464725 - add e4.tools feature to General Purpose tools category
Summary: add e4.tools feature to General Purpose tools category
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 464979
  Show dependency tree
 
Reported: 2015-04-15 13:31 EDT by David Williams CLA
Modified: 2015-04-20 03:56 EDT (History)
1 user (show)

See Also:


Attachments
pic of staging, as of 4/19 7:30 PM (101.05 KB, image/png)
2015-04-19 20:04 EDT, David Williams CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2015-04-15 13:31:50 EDT
And, add it to "ep.b3aggrcon" file. 

Opening cross-project bug just for awareness. But, a ?chunk? of e4 tooling as "graduated" from incubator to the main-line code, for Mars, and while not provided as part of "Platform" or "SDK" would benefit user community to have easier access (discover-ability) to it. I believe it's also being proposed to be added in a couple of EPP packages. 

The point of this bug is just to document that I will be adding it to the the "General Purpose Tools" category ... not aware of any better fit.
Comment 1 David Williams CLA 2015-04-15 13:33:31 EDT
Adding Lars to CC not only because he's the "defacto" owner of the feature ... but also because he claims not to have known about this "cross-project" bugzilla component. :)
Comment 2 Lars Vogel CLA 2015-04-15 13:53:47 EDT
(In reply to David Williams from comment #1)
> Adding Lars to CC not only because he's the "defacto" owner of the feature
> ... but also because he claims not to have known about this "cross-project"
> bugzilla component. :)

Thanks.
Comment 3 David Williams CLA 2015-04-19 20:04:35 EDT
Created attachment 252522 [details]
pic of staging, as of 4/19 7:30 PM

I've added this feature to our ep.b3aggrcon file, and General Purpose tools category. Added last weeks I-build as "warm-up" to staging. 

= = = = = 

And, remember (Lars :) and others, since we build this feature with some EMF components from "previous milestone" (since they are +1 components), but at times mixed with base EMF components for SDK for "next milestone", then: 

A. May not always "install cleaning" based on I-builds, depending what is where at which levels (i.e. this feature may want to down level the base components?), and 

B. By the time the milestone is "nearly done" (say, on +2 day) would be a good time to do "extra testing" on this feature, to make sure all installs cleanly, and works as expected: as that is the time "it all comes together" is Sim. Release repo. That is, what is installed with this feature at that time, will be different than what it was built with. [In the unlikely event that errors are found, we can rebuild, but, I think (hope?) you using basic, public function from EMF that would be unlikely to change from milestone to milestone.   

Thanks,
Comment 4 David Williams CLA 2015-04-19 20:05:11 EDT
Fixed as described in previous comment.
Comment 5 Lars Vogel CLA 2015-04-20 03:56:18 EDT
Thanks David, opened Bug 464979 for an improved description of this category.