Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364752 - [LTTng] Comply with the Linux Tools recommended project structure
Summary: [LTTng] Comply with the Linux Tools recommended project structure
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francois Chouinard CLA
QA Contact: Francois Chouinard CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 15:11 EST by Francois Chouinard CLA
Modified: 2022-01-13 14:53 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Chouinard CLA 2011-11-24 15:11:06 EST
We plan to properly align to Alex's recommended Linux Tools project structure for the upcoming 1.0 release. We did a half-hearted job at it at the last "ultimatum" :-) mainly because we had many internal branches ongoing, coupled with a tight local release schedule, and it was deemed too risky to go full-blown then.

But, as we are preparing for 1.0, now would be good time to bite the bullet and become fully compliant with the guidelines.

In a nutshell, the various plug-in IDs are already correct but the package and directory structures do not match exactly. The work that has to be done is the following:
- Refactor (rename) the packages org.eclipse.linuxtools.{lttng{,.tests},tmf{,.tests}} to the org.eclipse.linuxtools.{lttng.core{,.tests},tmf.core{,.tests}}
- Do the corresponding "git mv" so the repo directories match the new package names
- Fix the pom.xml:s
- Make sure nothing is broken

All this is fairly trivial but the downsides are that [1] you will likely have to perform a new checkouts to properly refresh your workspace(s), and [2] your local branches might not appreciate. The "git mv":s are causing the main annoyances but we would really like the directory structure to match the package naming.

Note that this applies to the master/HEAD branch only. The existing stable-0.x branches will keep the legacy structure.
Comment 1 Francois Chouinard CLA 2011-11-25 11:19:31 EST
Also removed the *.tmf.doc plugin since it is badly out of date and downright misleading. If we are to ever publish documentation again, it should in a design wiki.
Comment 2 Francois Chouinard CLA 2011-11-28 15:35:46 EST
Updated structure committed. Maven builds OK here.

commit: 0829a041f780d7d2cd8c0711bc6fe33b97f5157d
Comment 3 Francois Chouinard CLA 2012-03-26 14:01:09 EDT
Delivered in 0.10.0