Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 376696 - Migrate RAP Tooling to a separate Git repository?
Summary: Migrate RAP Tooling to a separate Git repository?
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5 RC1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 331780
  Show dependency tree
 
Reported: 2012-04-13 04:36 EDT by Ralf Sternberg CLA
Modified: 2012-05-15 16:21 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Sternberg CLA 2012-04-13 04:36:48 EDT
Since the RAP Tooling is completely separated from the RAP Runtime, i.e. there are no dependencies between runtime and tooling, it could make sense to create a separate Git repository for the tooling.
(+) The repositories will be smaller, cloning is faster.
(-) We need to split up the releng project into a runtime and a tooling part.

Thoughts?
Comment 1 Markus Knauer CLA 2012-04-13 08:45:07 EDT
Personally I would split these repositories during the CVS-Git migration, even if they are very small (my first very dump test shows that the overall Git part of the RAP repository is about 100 MBytes). Managing multiple Git repositories is easy, but splitting a single Git repository in multiple parts at a later time is not so easy.
Comment 2 Austin Riddle CLA 2012-04-13 09:41:52 EDT
(In reply to comment #1)
> ...but splitting a single Git repository in multiple parts at a later
> time is not so easy.

I agree, it also makes more sense to me to put the tooling in a separate repository since in my view most consumers of the RAP codebase are not doing anything with the tooling.
Comment 3 Rüdiger Herrmann CLA 2012-04-14 05:46:22 EDT
+1 for having a separate tooling repository.
As Austin already mentioned, most RAP users aren't interested in the tooling parts. Also from a RAP committer/contributor POV these are entirely separate too (i.e. you wouldn't have them in the same workspace, they have different taget platforms, etc.) They could even be separate Eclipse projects (much like PDE vs. Platform/UI).
Correct me if I'm wrong, but splitting the releng doesn't seem to be a disproportional effort.
Comment 4 Ralf Sternberg CLA 2012-05-10 08:27:46 EDT
Inspired by this tweet [1] I'd propose to name the repository "o.e.rap.tools" instead of "o.e.rap.tooling" and to rename the tooling feature to tools as well in 2.0. Even though the term "tooling" is commonly used in the Eclipse community, it's jargon and I think
"tools" is a more suitable name for the component. Comments?

[1] https://twitter.com/#!/waynebeaton/status/199531054070120448
Comment 5 Markus Knauer CLA 2012-05-10 08:31:28 EDT
(In reply to comment #4)
> "tools" is a more suitable name for the component. Comments?

I never gave this a thought but now that the discussion pops up I can only agree. To me 'tools' sounds much better than 'tooling'. From my point of view it is a +1 to use 'tools' and it is not (yet) too late to change this.
Comment 6 Rüdiger Herrmann CLA 2012-05-10 09:09:30 EDT
(In reply to comment #4)
> [ ... ]
> "tools" is a more suitable name for the component. Comments?
+1 for 'tools', short and nice
Comment 7 Ralf Sternberg CLA 2012-05-15 16:21:53 EDT
The RAP Tools have been successfully migrated to git. The old CVS is now read-only.

Read-only URL: git://git.eclipse.org/gitroot/rap/org.eclipse.rap.tools.git
Committer URL: ssh://COMMITTER_ID@git.eclipse.org/gitroot/rap/org.eclipse.rap.tools.git
Web frontend: http://git.eclipse.org/c/rap/org.eclipse.rap.tools.git/