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

Bug 436399

Summary:	Consider building "tools" and putting in (only) Eclipse repo
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert
Version:	4.4
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description David Williams

2014-06-02 14:44:34 EDT

I'm thinking of tools such as ASTVew (I got this idea from bug 436301), 

pessimistic file system provider, 

?SWT Leak? detector ... 

and others? 

I'm just thinking might be more easily available if in "common repo" and might encourage others to use/test with them more often? 

To emphasize their "tool, not to be extended" nature, might want to not "export packages" as we normally would? (Naturally, people could fork them, if they wanted to ... but, we shouldn't have to worry about "API" or anything. 

We currently have two categories that might be appropriate (or modified): 

  Eclipse Tests, Examples, and Extras	
  Releng Tools	

Also, they would not necessarily have to be part of "main build" ... but have their own build jobs, perhaps ran less often, and through the magic of composites, even put in their own, "sub repository" of main site.

Comment 1 Dani Megert

2014-06-02 15:12:38 EDT

The people who know JDT tools, SWT snippets, leak tools, etc. have a completely different knowledge of the tools/component. Removing the usual commit rights by putting them into a single repo and open a zoo is wrong.

If you want to build them out of different existing repos, then that's fine and this bug can be reopened.

Comment 2 David Williams

2014-06-02 19:10:23 EDT

(In reply to Dani Megert from comment #1)
> The people who know JDT tools, SWT snippets, leak tools, etc. have a
> completely different knowledge of the tools/component. Removing the usual
> commit rights by putting them into a single repo and open a zoo is wrong.
> 
> If you want to build them out of different existing repos, then that's fine
> and this bug can be reopened.

Well, a different Git repo (per component) is not a bad idea ... but, I guess I was not very clear. I was talking entirely about the p2 repository we provide. 

I you think "no one else is interested" ... that's fine, and you can close as won't fix again. But, I know in the past, when working on WTP or other projects, there was always "an hour or two" of just "tracking down" the tools and documentation  -- and that's by people fairly knowledgeable with Eclipse. Making it easier for others to find (and use) these tools was my only intent. Nothing about committership or Git repos.

Comment 3 Dani Megert

2014-06-03 03:35:37 EDT

(In reply to David Williams from comment #2)
> I was talking entirely about the p2 repository we provide. 

Ah yes, that makes perfect sense. I guess JDT could then stop building their tools manually and refer to that p2 repo, right?

Comment 4 David Williams

2014-06-03 06:27:59 EDT

(In reply to Dani Megert from comment #3)
> (In reply to David Williams from comment #2)
> > I was talking entirely about the p2 repository we provide. 
> 
> Ah yes, that makes perfect sense. I guess JDT could then stop building their
> tools manually and refer to that p2 repo, right?

Correct.

Comment 5 Lars Vogel

2019-11-27 07:29:17 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.