Community
Participate
Working Groups
Create an update site for COSMOS plugins.
Mark, Do we want to have update manager for v1.0?
Hubert, I'm glad you set this to i10 target milestone. I see this as very important for both the SML tooling and the data manager tooling (bug 208274).
*** Bug 216653 has been marked as a duplicate of this bug. ***
I forgot to also mention the WSDM tooling is another great candidate for an update manager.
*** Bug 218518 has been marked as a duplicate of this bug. ***
Copying Ruth's comment from one of the duplicate bugs here: "This bugzilla should be used to cover the work under item 'Involve the build team in helping with feature definition to enable an UpdateManager install.' The talk page on COSMOS that the development team has used for the discussion so far is located here: http://wiki.eclipse.org/Build_Packaging_for_COSMOS"
Assigning to Leonard as per Saurabh's/Jack's request.
I understand that Leonard has put together the update site. Saurabh, when is the target for deploying this so that people could install using the update manager? Does the site include all SDK packages, and will it include the docs as well?
Update site is going to include these features. org.eclipse.cosmos.rm org.eclipse.cosmos.rm.sdk org.eclipse.cosmos.rm.sml.mdr org.eclipse.cosmos.dc org.eclipse.cosmos.dc.sdk org.eclipse.cosmos.dc.stat.datamgr org.eclipse.cosmos.dc.framework org.eclipse.cosmos.dc.logging.datamgr org.eclipse.cosmos.dc.example.mdr org.eclipse.cosmos.me.management org.eclipse.cosmos.dc.dependencies org.eclipse.cosmos.me.dmtoolkit I asked Leonard to review the update site from one of the committer from CA.
Is this close to going live on our web site?
David, this was discussed on this mornings RE call. As far as is know, Len has coded all that is required, but has been unable to deploy this, as he is not yet a committer. Len will work through either JT, or Bill to get this in place. Len, update the issue if there is a new obstacle, or if there is a piece of information required that I've forgotten to mention.
I have recreated the site with all of the features and plugins that I could get to compile from yesterday's sources. These are the features included org.eclipse.cosmos.rm org.eclipse.cosmos.rm.sdk org.eclipse.cosmos.dc org.eclipse.cosmos.dc.sdk org.eclipse.cosmos.me.management org.eclipse.cosmos.dc.framework (some compile errors) These are the features that I could not get to compile and I omitted org.eclipse.cosmos.rm.sml.mdr org.eclipse.cosmos.dc.stat.datamgr org.eclipse.cosmos.dc.logging.datamgr org.eclipse.cosmos.dc.example.mdr org.eclipse.cosmos.dc.dependencies org.eclipse.cosmos.me.dmtoolkit The uncompiled reatures probably just require dependencies but developers should clearly state what is required for a successful build. I am not able to deploy it on the eclipse site as I am not a committer and even if I got a committer to do it, I do not know where to put it. I will try to make a zip file of this site available on our ftp site so that it can be tested locally or remotely.
The update site zip file is now available at: ftp://ftp.ca.com/outgoing/0000972/16471242-01/cosmosupdate.zip Please download and extract. You can then use it locally or deploy it to a remote web site. Then Use Help->Software Updates->Find and Install... Select "Search for new features to install" and click Next. Setup a remote or local site pointing to wherever you deployed it, select it and then click Finish. The features available will then be seen.
A COSMOS update site can now be generated using the script updatesite.cosmos.sh located in the org.eclipse.cosmos.releng.builder/bash directory. It is called as follows USAGE: ./updatesite.cosmos.sh <output directory> <driver directory> Where <output directory> is the location of the update site where the updates folder will be generated and <driver directory> is the location of sdk zip files from the build. The script will generate a site which contains all of the features in the file update-site-features.lst. This file is currently in CVS in the org.eclipse.cosmos.releng.builder/bash directory. Any alterations to the list can be made in this file and the script will generate the site accordingly, as long as the features and plugins are in the sdk zip files. This is an example of how you could generate a site from a recent build and use the update site. Obtain the script from CVS and copy to a work folder on build.eclipse.org. Then do the following. mkdir mysite ./updatesite.cosmos.sh mysite /shared/technology/cosmos/downloads/COSMOS/1.0.0/COSMOS-1.0.0-200806011210/ Wait for site to be generated then copy the updates folder created in the folder mysite, from there to a folder on a web server. Start Eclipse, and use Help->Software Update->Find and Install.. Click Search for new features to install and Next Create a new remote site and point it to the location of the updates folder where you published it on your web server previously. Click Finish, and the list of features will be displayed. select the required features and Next Agree to the license terms, click Next then Finish. The selected features and associated plugins will be installed. The script may be integrated into the build process when it is clear what is required.
Nice work, Leonard! I had thought this would be marked fixed when the update site is available and referenced on our web site. I know your work is done, Leonard, but should we create a separate defect to track the work of integrating your script with the build and updating the web site to tell consumers of the update site URL? Or should we reopen and reassign this defect for that purpose?
Guess I should not have marked this as resolved until it was verified, so I changed the resolution to WORKSFORME. Not sure if this is right either but seems the most appropriate status at the moment. Will create a separate bug to track the integration of the script into the build. Also tried creating a sample site at somewhere like http://builds.eclipse.org/technology/cosmos/downloads/updates, so that developers could access it from Eclipse, and test that the constructed site actually contains the correct parts I but did not have the permissions to write to that area.
Actually RESOLVED-FIXED is the correct status if there will be a separate ER or defect for putting it in our build and on our web site. Once the fix is verified by someone, then it will be moved to VERIFIED status.
Leonard, Can you please provide instructions for me to verify this enhancement? Please provide instructions for using the update site from the COSMOS website. Also, the feature.xml files for COSMOS features will need to include the declaration of the COSMOS update site. This is for discovering newer versions. You can look at projects in ganymede as examples. For example: <url> <update label="%EMFUpdateSiteName" url="http://download.eclipse.org/modeling/emf/updates/"/> <discovery label="%EMFUpdateSiteName" url="http://download.eclipse.org/modeling/emf/updates/"/> <discovery label="%EMFTUpdateSiteName" url="http://download.eclipse.org/modeling/emft/updates/"/> </url>
Unfortunately I do not yet have a place where I can put a generated site so that it can be accessed by everyone. So the only alternative is to generate the site using the script yourself and use Eclipse to test and install from a local site. If you look at my comment 15 on this bug, it provides instructions and an example on how to use the script to generate the update site. You can use these to verify that the script generates the site correctly.
The site isn't working for me. Here's what I did in Eclipse 3.4 GA: 1. Help > Software Updates... 2. Available Software 3. Add Site... 4. Pasted in http://download.eclipse.org/technology/cosmos/update-site 5. Expanded the tree for the site and noticed the 4 subproject categories (which I'm not sure that we want to organize in this way, since the user doesn't know our subprojects). Noticed "resource modeling" incorrectly has two "l"s. 6. Tried to expand the tree for any of the subprojects, but nothing shows up. 7. Deselected the two checkboxes below the tree view and attempted again to expand the subproject trees. Still nothing shows up.
David, You probably already have some or all of the plugins and features installed in your Eclipse environment. Click the installed software tab to check. If so when you browse the update site again, they do not show up unless you click the "Include items that have already been installed" check box. Then you can try to reinstall, but this does not seem to work and it tells you that they are already installed and its not going to install again. If you remove all the COSMOS plugins and try the process again it should work. To remove them: 1) Go to Help->Software Updates... and click the Install Software tab.. 2) Select all entries starting with COSMOS 3) Click the Uninstall button 4) Restart Eclipse as advised The version of Eclipse I am using is 3.4.0 build Id: I200080617-2000, which is the GA release. All earlier versions have a different GUI for installs from update sites and my instructions earlier in this thread are no longer valid for this GA version. As for the subcategories in the site, please expand on how you would like the site organized. Specifically what categories, if any, that you require. I have no guidelines here, so once we have agreed on a new format, I can change the site generation script accordingly. Thanks
(In reply to comment #22) > David, > > You probably already have some or all of the plugins and features installed in > your Eclipse environment. Click the installed software tab to check. If so when > you browse the update site again, they do not show up unless you click the > "Include items that have already been installed" check box. Then you can try to > reinstall, but this does not seem to work and it tells you that they are > already installed and its not going to install again. When I check that check box you mentioned, I still don't see any child items of the categories. > If you remove all the COSMOS plugins and try the process again it should work. > > To remove them: > > 1) Go to Help->Software Updates... and click the Install Software tab.. > 2) Select all entries starting with COSMOS > 3) Click the Uninstall button > 4) Restart Eclipse as advised > > The version of Eclipse I am using is 3.4.0 build Id: I200080617-2000, which is > the GA release. All earlier versions have a different GUI for installs from > update sites and my instructions earlier in this thread are no longer valid for > this GA version. I have the GA version also. > As for the subcategories in the site, please expand on how you would like the > site organized. Specifically what categories, if any, that you require. I have > no guidelines here, so once we have agreed on a new format, I can change the > site generation script accordingly. Since there is only one item per category, perhaps we don't even need categories?
I am unable to uninstall cosmos features using the Software Updates window. When I select each of the COSMOS features, the Uninstall button is grayed out. Perhaps this is because they were not originally installed using update manager, or should that matter?
I have only ever installed the COSMOS features via the update manager and have started with a clean environment since the GA release. Not knowing the exact install/uninstall mechanism behind the scenes, I would guess that software which is not installed via the update manager cannot be uninstalled that way. If you select any other non Cosmos package that is installed via the traditional copy into the eclipse folder method, and then try to uninstall it using the update manager then it does not allow you to do it so your assumption is probably correct. This behavior sounds reasonable to me; as a comparison, if you just copy an exe to a folder on your c: drive you cannot use add/remove programs to get rid of it.
Updated script to change layout of the update site to have only two categories: 1) SML validator and SML-IF Editor 2) COSMOS SDK
(In reply to comment #26) > Updated script to change layout of the update site to have only two categories: > > 1) SML validator and SML-IF Editor > 2) COSMOS SDK > Thanks, Leonard. Can we change #1 to instead be simply "SML Tooling"? There is more there than just the validator and editor, and SML Tooling would keep it simple.
Category 1 has now been changed to SML Tooling
