Bug 306133 - Rename and move org.eclipse.stp.sca.osoa to Orbit
Summary: Rename and move org.eclipse.stp.sca.osoa to Orbit
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sca (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 03:20 EDT by Stephane Drapeau CLA
Modified: 2017-03-30 14:20 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephane Drapeau CLA 2010-03-17 03:20:40 EDT 
Here a comment from Wayne Beaton:
> I've noticed that you've packaged the OSOA code into a bundle named
> "org.eclipse.stp.sca.osoa"; I would have expected to see this in a bundle named 
> "org.osoa.sca.annotations" or similar per Orbit convention. After the move, 
> please consider changing the name of this bundle to better align with the 
> convention. Further, please consider moving this bundle to Orbit. I assume that 
> it's generic enough to make sense there; correct me if I'm wrong.

Can we consider to move the plugin to Orbit after Helios?
It makes sense for me.
Comment 1 Vincent Zurczak CLA 2010-03-17 05:37:32 EDT 
Hi,

Maybe I have missed something.
Are the OSOA annotations moving to Orbit? If so, why?

It was planned last year, but we dropped the idea.
Comment 2 Stephane Drapeau CLA 2010-03-17 06:05:02 EDT 
(In reply to comment #1)
> Are the OSOA annotations moving to Orbit? If so, why?

No, the OSOA annotations are not moving to Orbit. 
The question is, do we plan the move or not?
An answer is not required right now. Priority tasks must be done before. We can do this after Helios.

The "move" of which Wayne is talking, is the move of the SCA Tools project from the STP TLP to the SOA TLP.