Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367008 - [releng] Organise Update/Repo categories to improve useability
Summary: [releng] Organise Update/Repo categories to improve useability
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 4.0.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-17 11:16 EST by Ed Willink CLA
Modified: 2013-05-20 11:37 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-12-17 11:16:41 EST
When using M4a, I need to install OCL core, then Acceleo, then OCL tools.

If I have only downloaded the tools ZIP I cannot do this because there is no categorisation to support use of the Core elements.
Comment 1 Adolfo Sanchez-Barbudo Herrera CLA 2011-12-19 08:48:24 EST
Well, 

The idea was actually having to use the core zip, to update the OCL SDK feature . Indeed, If you use public repositories (milestones, nightly, etc) you should be able to that, since they compose the Core and Tools repositories.

On the other hand, since the Core stuff is being included in the Tools p2 repository, I could easily include a categoritzation to make the SDK feature be visible and faciliate to the Tools repository the ability of install/updating every OCL feature at once (including the OCL SDK feature). I don't see any harm of this.

The only inconvenience is that from the public OCL repositories the SDK feature would be available for install/update in both repositories/features categorization (Core and Tools repos). I'm not sure if this could be confusing.

Cheers,
Adolfo.
Comment 2 Ed Willink CLA 2011-12-19 12:03:31 EST
It's already confusing, and some other projects have duplicates too.

I would drop "Eclipse" from category titles so that we would g=have twop top level names "OCL Core" and "OCL Tools (and Core)" with obvious titles below.
Comment 3 Adolfo Sanchez-Barbudo Herrera CLA 2011-12-19 12:44:57 EST
The name of the category is built with some parameters of the build:

the "package.qualifier" (component.name + build.alias or build.id) is used in some bits: the category and zips names, for example. I could create/use a new/different property for the category name, though.

Regards,
Adolfo.
Comment 4 Adolfo Sanchez-Barbudo Herrera CLA 2011-12-23 09:01:44 EST
Current master fixes this issue.

You may check with the last successful core[1] and tests[2] builds.

I've finally did a final change. Since the Core Build, simply builds the CoreSDK feature, I removed the (and Core) from the category name for the Tools repository. You may verify that when the tools job success again.

Resolving as fixed.

Best Regards,
Adolfo.

[1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/
[2] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-branch-tests/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/
Comment 5 Ed Willink CLA 2013-05-20 11:37:26 EDT
CLOSED after a year in the RESOLVED state.