Community
Participate
Working Groups
Based on our discussions during various PMC calls, we want to create (a) composite site(s) for all Modeling projects rather than having aggregate sites for the various container projects. This is desirable since we're already using "Eclipse Modeling Project" and an associated branding icon for our projects; it only makes sense to use common update and discovery sites as well. The proposal is to host composite content and artifacts XML files in CVS which would be accessible at http://www.eclipse.org/modeling/updates. Projects would contribute to the site by including references to their respective (operating) project-specific sites for each release. Similar sites for milestone and interim builds would be be at http://www.eclipse.org/modeling/updates/milestones and http://www.eclipse.org/modeling/updates/interim, respectively. In order to adopt the new composite site in time for Helios, each project would need to a) add a reference to their (project-specific) site and b) change the update and discovery site references in their features to point to the new URL.
Created attachment 170004 [details] initial sites
This should be fixed in RC2 and beyond.
Oops, wrong bug. :-(
With Ed's help there is now an initial site in place. In order for other projects to include their sites, the project leads will need to provide Ed with their site URL(s). Of course, they will also need to change the update and discovery URLs in their features to reference the new site. We are just about to commit the changes to do this for EMF and XSD...
Created attachment 170261 [details] UML2 site Ed, here is a patch that adds the site for UML2 (assuming we'll actually be able to build and release it...).
I've committed the changes.
Ed, the compare update-site is http://download.eclipse.org/modeling/emf/updates/releases/ (and milestones + interim) for helios but it's not a compare specific one. Is that a problem ? Kenn : what is the difference between the discovery and update field ? should we point to the same update-site being the http://www.eclipse.org/modeling/updates one ?
(In reply to comment #7) > Ed, the compare update-site is > http://download.eclipse.org/modeling/emf/updates/releases/ (and milestones + > interim) for helios but it's not a compare specific one. Is that a problem ? > This is similar to the MDT update site being used for UML2. It should not be a problem. > Kenn : what is the difference between the discovery and update field ? should > we point to the same update-site being the > http://www.eclipse.org/modeling/updates one ? It's never been clear to me what the difference is, but just use the same URL for both. Ideally, when all Modeling projects are installed, there would only be one additional software site introduced - the new composite one.
The Acceleo update site is http://download.eclipse.org/modeling/m2t/updates/releases/ , which isn't specific to Acceleo either.
The M2T-JET uses the same update site as Acceleo. It appears, however, the Xpand is using a separate site for Helios. I haven't figured out the Xpand locations yet. Also, I just give the 'milestones' composite site a try with RC3 - seems to work fine. But, the 'interim' composite site reports a cryptic error from P2. Here's the error log entry: eclipse.buildId=I20100527-1700 java.fullversion=J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled) J9VM - 20081105_025433_lHdSMr JIT - r9_20081031_1330 GC - 20081027_AB BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA Command-line arguments: -os win32 -ws win32 -arch x86 Error Tue Jun 01 11:34:39 EDT 2010 Unable to read repository at http://www.eclipse.org/modeling/updates/interim/compositeContent.xml. org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://www.eclipse.org/modeling/updates/interim/compositeContent.xml. at org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:357) at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:205) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.getLocalFile(CompositeMetadataRepositoryFactory.java:74) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:99) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:747) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:652) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.p2.ui.ProvisioningUI.loadMetadataRepository(ProvisioningUI.java:388) at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:120) at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getRepository(MetadataRepositoryElement.java:109) at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:103) at org.eclipse.equinox.internal.p2.ui.QueryProvider.getQueryDescriptor(QueryProvider.java:54) at org.eclipse.equinox.internal.p2.ui.model.QueriedElement.fetchChildren(QueriedElement.java:102) at org.eclipse.equinox.internal.p2.ui.model.MetadataRepositoryElement.fetchChildren(MetadataRepositoryElement.java:72) at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:34) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.util.NoSuchElementException at java.util.TreeMap.firstKey(TreeMap.java:4251) at java.util.TreeMap$NavigableSubMap.values(TreeMap.java:3042) at org.eclipse.equinox.internal.p2.repository.ProgressStatistics.getRecentSpeed(ProgressStatistics.java:101) at org.eclipse.equinox.internal.p2.repository.ProgressStatistics.report(ProgressStatistics.java:126) at org.eclipse.equinox.internal.p2.repository.FileReader.handleTransferEvent(FileReader.java:157) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.fireReceiveStartEvent(AbstractRetrieveFileTransfer.java:659) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:735) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:877) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:564) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:98) at org.eclipse.equinox.internal.p2.repository.FileReader.sendRetrieveRequest(FileReader.java:342) at org.eclipse.equinox.internal.p2.repository.FileReader.readInto(FileReader.java:288) at org.eclipse.equinox.internal.p2.repository.RepositoryTransport.download(RepositoryTransport.java:71) at org.eclipse.equinox.internal.p2.repository.RepositoryTransport.download(RepositoryTransport.java:127) at org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:337) ... 18 more
Created attachment 170668 [details] Ecore Tools Site This adds the sites for Ecore Tools.
FYI. The stack trace in comment 10 appears to be related to the IBM JVM and/or the client firewall on my machine. Everything works fine with the Sun 1.6 JVM.
(In reply to comment #12) > FYI. The stack trace in comment 10 appears to be related to the IBM JVM and/or > the client firewall on my machine. Everything works fine with the Sun 1.6 JVM. There are known issues with running p2 with the IBM JVM. Which version did you try?
Noticed a typo in the Interim site name: Eclipse Modeling Project Iterim Site Should be Eclipse Modeling Project Interim Site As for the IBM JVM version: J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 I've switch to a Sun JVM for the time being.
I fixed the typo Paul noticed.
These are the sites for Teneo: http://download.eclipse.org/modeling/emf/teneo/updates/1.2.0/interim/ http://download.eclipse.org/modeling/emf/teneo/updates/1.2.0/milestones/ http://download.eclipse.org/modeling/emf/teneo/updates/1.2.0/releases/ The releases site is not there yet as I direct everyone to use a nightly build. But when Helios releases I will create one. Should I create a patch, or commit this myself? I have made the changes to the update/discovery sites in the feature.xml of Teneo. This will be/is in the RC3 build. gr. Martin
To make sure : we need to ad both 'update site' and 'discovery site' to our feature.xml files. Should we use a "standard" label for these sites? And "discovery" doesn't appear on the overview of the feature.xml in the feature editor. Do we manually add it in the xml? If I understood correctly, this would give something like this in our feature.xml. If I am wrong, please tell it soon :p. <url> <discovery label="Eclipse Modeling" url="http://www.eclipse.org/modeling/updates"/> <update label="Eclipse Modeling" url="http://www.eclipse.org/modeling/updates"/> </url>
(In reply to comment #17) > To make sure : we need to ad both 'update site' and 'discovery site' to our > feature.xml files. Should we use a "standard" label for these sites? And > "discovery" doesn't appear on the overview of the feature.xml in the feature > editor. Do we manually add it in the xml? > > If I understood correctly, this would give something like this in our > feature.xml. If I am wrong, please tell it soon :p. > > <url> > <discovery label="Eclipse Modeling" > url="http://www.eclipse.org/modeling/updates"/> > <update label="Eclipse Modeling" > url="http://www.eclipse.org/modeling/updates"/> > </url> Yes, we should use the same label. In EMF, XSD, and Ecore Tools we used "Eclipse Modeling Project Updates". Here's what we have in our feature manifests: <url> <update label="%ModelingUpdateSiteName" url="http://www.eclipse.org/modeling/updates/"/> <discovery label="%ModelingUpdateSiteName" url="http://www.eclipse.org/modeling/updates/"/> </url>
Let's go with "Eclipse Modeling Project Updates" then, thanks for the update :).
(In reply to comment #16) > The releases site is not there yet as I direct everyone to use a nightly build. > But when Helios releases I will create one. You could create an empty (composite) site for releases; that's what we've done for EMF, XSD, and Ecore Tools... > Should I create a patch, or commit this myself? No, as far as we can tell only Ed has the necessary write permission. I'll create a patch with all of the outstanding changes and attach it ASAP. > > I have made the changes to the update/discovery sites in the feature.xml of > Teneo. This will be/is in the RC3 build. Great, thanks!
Created attachment 170858 [details] Changes for EMF Compare, EMF Teneo, M2T (Acceleo and JET) Here's a patch for the outstanding sites.
I've committed the latest patch.
Created attachment 170920 [details] Proposed changes for CDO and Net4j features Please have a look at the changes I've made and let me know if they're okay. And ping me when it's time to commit them!
hi, i would like to participate for the EEF project, but i am a little bit lost :) looking to your patches, do i need to provide update site that contains only 0.8.X versions or a more generally one ( with futures 0.9 version ? ) ie http://download.eclipse.org/modeling/emft/eef/updates/interim/ ( all interim versions ) or http://download.eclipse.org/modeling/emft/eef/updates/0.8.interim/ ( just 0.8 versions ) ? thanks
I'm also not an expert in this round but my understanding was that we update our features to point to the modeling update site and Kenn or Ed update the definition of the aggregate repo. I suspect this must be coordinated in some way.
(In reply to comment #23) > Created an attachment (id=170920) [details] > Proposed changes for CDO and Net4j features > > Please have a look at the changes I've made and let me know if they're okay. > And ping me when it's time to commit them! At a glance, these changes look fine. If you are using Buckminster (which you are), take care not to specify the common Modeling composite (or any site, for that matter) as the update site for your build feature, or it will try to use it as a mirror by default. For EMF builds, we have removed all site URLs from our build feature and are using a template when we "promote" our build to insert the appropriate mirror site URL.
(In reply to comment #24) > hi, > > i would like to participate for the EEF project, but i am a little bit lost :) > > looking to your patches, do i need to provide update site that contains only > 0.8.X versions or a more generally one ( with futures 0.9 version ? ) ie > > http://download.eclipse.org/modeling/emft/eef/updates/interim/ ( all interim > versions ) > > or > > http://download.eclipse.org/modeling/emft/eef/updates/0.8.interim/ ( just 0.8 > versions ) ? > > thanks Longer term, we want to get rid of the container project aggregate sites (such as the ones for EMF, MDT, M2T, etc.) and move towards a project-specific site (or sites) for each release. We have done this for EMF, XSD, and Ecore Tools to set the trend. In the meantime, if your project is still publishing its builds as part of an aggregate site, we can include the URL for that aggregate. Note that, for projects that are already using a project-specific site for this release, we'll need to include the release URL in the legacy aggregate site so that clients which already have features installed will discover the new release when checking for updates.
(In reply to comment #25) > I'm also not an expert in this round but my understanding was that we update > our features to point to the modeling update site and Kenn or Ed update the > definition of the aggregate repo. I suspect this must be coordinated in some > way. Eike, you can make the changes in your features any time (before next week's final RC4 build, of course). Please tell us the URL(s) of your site(s) and I'll create a patch which Ed will then commit.
(In reply to comment #27) > (In reply to comment #24) > > hi, > > > > i would like to participate for the EEF project, but i am a little bit lost :) > > > > looking to your patches, do i need to provide update site that contains only > > 0.8.X versions or a more generally one ( with futures 0.9 version ? ) ie > > > > http://download.eclipse.org/modeling/emft/eef/updates/interim/ ( all interim > > versions ) > > > > or > > > > http://download.eclipse.org/modeling/emft/eef/updates/0.8.interim/ ( just 0.8 > > versions ) ? > > > > thanks > > Longer term, we want to get rid of the container project aggregate sites (such > as the ones for EMF, MDT, M2T, etc.) and move towards a project-specific site > (or sites) for each release. We have done this for EMF, XSD, and Ecore Tools to > set the trend. In the meantime, if your project is still publishing its builds > as part of an aggregate site, we can include the URL for that aggregate. no, my project is not part of EMFT aggragate. It has its own sites. > > Note that, for projects that are already using a project-specific site for this > release, we'll need to include the release URL in the legacy aggregate site so > that clients which already have features installed will discover the new > release when checking for updates. ok, so please add the three EEF sites : ( at least the release, but for now it is empty :) ) http://download.eclipse.org/modeling/emft/eef/updates/interim/ http://download.eclipse.org/modeling/emft/eef/updates/milestones/ http://download.eclipse.org/modeling/emft/eef/updates/releases/
We do not have interim builds for Xtext, Xpand and MWE but we have update sites for nightly builds. I know that this is uncommon at Eclipse but we like to be able to test nightlies that way. I'ld like to suggest to have another aggregate site for nightly builds. Are there any other projects having nightly update sites or are interested to introduce them?
(In reply to comment #30) > We do not have interim builds for Xtext, Xpand and MWE but we have update sites > for nightly builds. > I know that this is uncommon at Eclipse but we like to be able to test > nightlies that way. > I'ld like to suggest to have another aggregate site for nightly builds. > > Are there any other projects having nightly update sites or are interested to > introduce them? We have nightly for EEF, but i don't think this is a good idea to aggregate them. nightly can be totally broken, and might be accessible to small groups of people ( dev team ). in contrary, EEF has integration builds that are deployed periodically that can be used widely...
(In reply to comment #31) > (In reply to comment #30) > > We do not have interim builds for Xtext, Xpand and MWE but we have update sites > > for nightly builds. > > I know that this is uncommon at Eclipse but we like to be able to test > > nightlies that way. > > I'ld like to suggest to have another aggregate site for nightly builds. > > > > Are there any other projects having nightly update sites or are interested to > > introduce them? > > We have nightly for EEF, but i don't think this is a good idea to aggregate > them. nightly can be totally broken, and might be accessible to small groups > of people ( dev team ). in contrary, EEF has integration builds that are > deployed periodically that can be used widely... You are probably right. In our case it is good to have the three sites aggregated, since we often have parallel changes (they all depend on each other...). Last year we also developed against the head of EMF. We changed to MinimalEObject as soon as it was committed. Depending on the last milestone might be a better strategy in many cases, but sometimes it slows you down. However, I think this needs to be solved individually. I.e. I agree with not having an aggregated nightly site. :-)
Created attachment 171100 [details] EEF site
Created attachment 171398 [details] EMFT MWE, M2T Xpand and TMF Xtext Mwe, Xpand, Xtext contribution.
(In reply to comment #34) > Created an attachment (id=171398) [details] > EMFT MWE, M2T Xpand and TMF Xtext > > Mwe, Xpand, Xtext contribution. Dennis, are there a /releases subfolders that could be referenced instead for the release sites?
(In reply to comment #35) > (In reply to comment #34) > > Created an attachment (id=171398) [details] [details] > > EMFT MWE, M2T Xpand and TMF Xtext > > > > Mwe, Xpand, Xtext contribution. > > Dennis, are there a /releases subfolders that could be referenced instead for > the release sites? Yes, but we prefer to use updates as the root entry, to have more control about what is contributed to modeling update site. It's exactly the same as for modeling/updates. There is a composite u- site which currently points to old 0.7.2 release in updates/release folder. For Helios I will move this old release to a separate folder becuase Athena overwrites existing content. After promotion I will setup our updates/ composite update site to use the "old" 0.7.2 and the new Helios releases update sites.
Kenn, please change the repository URL for CDO to http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/ Not the one we talked about yesterday!
Kenn, I just noticed that my patch is not applied yet. Is there still something to do? Regards, Dennis.
(In reply to comment #38) > Kenn, > I just noticed that my patch is not applied yet. > Is there still something to do? > > Regards, > Dennis. Sorry for the delay, Dennis. Unfortunately, Ed is the only one with the necessary commit privileges, and he's currently traveling. In the meantime, I'll create a consolidated patch for the outstanding changes...
Created attachment 171980 [details] Changes for EMF CDO, EMFT MWE, M2T Xpand, and TMF Xtext Ed, please commit the changes in this consolidated patch.
(In reply to comment #39) > Sorry for the delay, Dennis. No problem! :) > Unfortunately, Ed is the only one with the > necessary commit privileges, hmm... that's not good. Normally, anyone with group membership ('modeling-home') may commit, right?
(In reply to comment #41) > (In reply to comment #39) > > Sorry for the delay, Dennis. > No problem! :) > > Unfortunately, Ed is the only one with the > > necessary commit privileges, > hmm... that's not good. > Normally, anyone with group membership ('modeling-home') may commit, right? Yes, but Modeling committers are not automatically in that group. :(
The patch from comment #40 is committed to CVS.
For MoDisco, the update sites are: release (composite): http://download.eclipse.org/modeling/mdt/modisco/updates/release/ milestones (will be composite): http://download.eclipse.org/modeling/mdt/modisco/updates/milestones/ For the discovery/update URLs in the features, http://www.eclipse.org/modeling/updates is on the web server. Shouldn't it be http://download.eclipse.org/modeling/updates instead?
(In reply to comment #44) > For MoDisco, the update sites are: > > release (composite): > http://download.eclipse.org/modeling/mdt/modisco/updates/release/ > > milestones (will be composite): > http://download.eclipse.org/modeling/mdt/modisco/updates/milestones/ Thanks, I'll attach a patch for Ed shortly. > For the discovery/update URLs in the features, > http://www.eclipse.org/modeling/updates is on the web server. Shouldn't it be > http://download.eclipse.org/modeling/updates instead? Not necessarily. We're using a location on the web server so that we can more easily sync it with CVS; what really matters is where the composed repositories are located - they should be on the download server so that they can be mirrored, archived, etc..
Created attachment 176826 [details] Changes for MDT MoDisco
The patch in commment https://bugs.eclipse.org/bugs/show_bug.cgi?id=314388#c46 is committed.
Adolfo: MoDisco's contribution shows us exactly what we should be doing on MDT/OCL.
Hello Folks, Bug 334378 resolution has fixed every MDT/OCL feature so that now it refers to the requested URL. I've been recently working with the organization of our repositories. There has been some discussion in the mdt-ocl.dev about this organization and possible URLS... The final URL of our repositories are the following - http://download.eclipse.org/modeling/mdt/ocl/updates/releases a composite repository which will expose every MDT/OCL Release (starting from the Helios one: MDT/OCL 3.0.0). - http://download.eclipse.org/modeling/mdt/ocl/updates/milestones a composite repository which contains our three last stable build (including RCs). This repository is thought to be used during the milestones by any party interested in our main development stream (downstream projects, modeling composite repository, the simultaneous release aggregator, etc) - http://download.eclipse.org/modeling/mdt/ocl/updates/interim a repository which contains our last successful integration build. This repository is thought to be used between milestones by any party interested in our main development stream. Some other questions: - These URLs are project-specific. The previous releng decided not to aggregate the releases repository to the MDT releases repository one. Do we need to do this now (for Helios SR2 and/or Indigo) ?. - In the mailing list discussion, I talked about the possibility of using (actually I'm currently using it) a http://download.eclipse.org/modeling/mdt/ocl/updates/maintenance repository which contained our last successful maintenance build (this could also contain our SR RC artifacts). This repository were thought to be used by any party interested in our maintenance stream (downstream projects, an hypothetical modeling composite maintenance repository, the service release aggregator, etc) ... Does this make sense to anybody ? Cheers, Adolfo.
Created attachment 187270 [details] Changes for MDT OCL To make things easier, the attachment provides the patch to make the EMP repositories compose the correpsondent MDT/OCL repositories. Best Regards, Adolfo.
The OCL changes have been committed to CVS.
The Helios build has been failing because it cannot load the composite modeling repository. :( I think the problem may have to do with the fact that the child sizes in the metadata are not correct. I'll attach a patch to fix them.
Created attachment 187522 [details] child size corrections
The changes are committed to CVS.
I just realized that our composite repo is the only one that uses www.e.o rather than download.e.o and I wonder if that's intentional? Does it affect mirroring in some way?
(In reply to comment #55) > I just realized that our composite repo is the only one that uses www.e.o > rather than download.e.o and I wonder if that's intentional? Does it affect > mirroring in some way? AFAIK, the composite itself does not need to be mirrored; only the contents (referenced repositories) do, and they are since they are located on download.eclipse.org.
the uml2 tools project also has new update sites now I created a patch to add these new sites to the modeling update site (see attachment)
Created attachment 192256 [details] Patch to add UML2 Tools update sites ...and here's the patch
I committed the changes, plus incremented the size. It's important to fix child sizes, so please consider that for future additions.
Created attachment 198416 [details] patch for emf and xsd 2.7 Here's a patch that adds references to the release repository for EMF and XSD 2.7.0.
Reopening to add sites for EMF and XSD 2.7.0.
Hi Kenn, We've got a new layout of our repositories: http://download.eclipse.org/modeling/emf/cdo/updates/downloads.php Would you agree that it makes sense to include these two instead of the former one(s)? http://download.eclipse.org/modeling/emf/cdo/updates/releases http://download.eclipse.org/modeling/emf/cdo/updates/maintenance/stable
(In reply to comment #63) > Would you agree that it makes sense to include these two instead of the former > one(s)? > > http://download.eclipse.org/modeling/emf/cdo/updates/releases > http://download.eclipse.org/modeling/emf/cdo/updates/maintenance/stable And if so, could you please change the CDO child locations accordingly?
(In reply to comment #64) > (In reply to comment #63) > > Would you agree that it makes sense to include these two instead of the former > > one(s)? > > > > http://download.eclipse.org/modeling/emf/cdo/updates/releases > > http://download.eclipse.org/modeling/emf/cdo/updates/maintenance/stable > > And if so, could you please change the CDO child locations accordingly? I think you're the better judge of which repositories you want to publish for your project. If you provide a patch, Ed can apply and commit the changes (I don't have the necessary permissions).
(In reply to comment #65) > If you provide a patch, Ed can apply and commit the changes I don't even know what to create a patch against. AFAIK these p2 composite repositories are simple xml files with one line per child, similar to: <child location=".."/> Ed just has to change my line and evtl. add a second one. Note that the "official" way to manage composites is to use p2 API or the p2 Ant tasks. I don't know how you guys maintain this Modeling composite.
Created attachment 207256 [details] updates for EMF (Core), MDT XSD, and MDT UML2 The composites need to be updated to pick up interim and milestone builds for more recent EMF/XSD (i.e., 2.7.2 and 2.8) and UML2 (i.e., 4.0) releases.
The latest patch has been committed.
Hi guys, Just a note about this bug and some builds using buckminster. I discovered that buckminster is incorrectly using the sites to visit or discovery URL in the p2 metadata for "p2.mirrorsURL". resulting is a LOT of errors trying to mirror or just install artifacts from a command line. using tycho resolved the problem. see https://bugs.eclipse.org/bugs/show_bug.cgi?id=374471 for ref.
(In reply to comment #69) > Hi guys, > > Just a note about this bug and some builds using buckminster. > > I discovered that buckminster is incorrectly using the sites to visit or > discovery URL in the p2 metadata for "p2.mirrorsURL". It's a well known buckminster feature, not a bug. The "site" feature is just a container for features to build and not a real feature which can/should be installed with p2. > resulting is a LOT of > errors trying to mirror or just install artifacts from a command line. > using tycho resolved the problem. And how many new problems you got after switching to Tycho? :) > see https://bugs.eclipse.org/bugs/show_bug.cgi?id=374471 for ref.
So I assume there's no action needed to resolve anything...
Changes (for which a patch will be attached shortly) are needed to pick up the new repositories for UML2 4.0.
Created attachment 217318 [details] changes needed for uml2 4.0
Created attachment 217333 [details] CDO changes Please apply the attached changes for CDO.
From Bug 382092: P2 cannot find http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/ http://download.eclipse.org/modeling/emf/teneo/updates/1.2.0/releases/ http://download.eclipse.org/modeling/mdt/uml2tools/updates/releases/ CDO and Teneo appear to have moved to the 'standard' composite repository names. UML2Tools only has a 'standard' interim repository.
Created attachment 217354 [details] CDO Changes I made a new patch that: 1) Remove the old CDO contributions that I overlooked in two files (Thx Ed!) 2) Fix the children counts in all files (was already wrong in two of them) 3) Adds a .cvsignore for the .project file (hope that's ok)
I committed the combined changes from Kenn and Eike, but I need Martin's attention to what needs to be changed for Teneo.
Dennis, I'm sure I need to add something for the 2.8 EMF release, but I'm not sure what.
(In reply to comment #78) > Dennis, > > I'm sure I need to add something for the 2.8 EMF release, but I'm not sure > what. All the sites we have are already in, except of 2.8 I think, but it's still empty. You can add it anyway: http://download.eclipse.org/modeling/emf/emf/updates/2.8 I'm not sure why we have to maintain them in this bug. What about the composite site foreach modeling site, like I did it for Xtext? I can create and maintain following sites: http://www.eclipse.org/modeling/emf/emf/releases http://www.eclipse.org/modeling/emf/emf/milestones http://www.eclipse.org/modeling/emf/emf/integration Then you reference this sites in modeling composite repositories, so we don't have to change them each release.
> > I'm not sure why we have to maintain them in this bug. What about the composite > site foreach modeling site, like I did it for Xtext? > I can create and maintain following sites: > http://www.eclipse.org/modeling/emf/emf/releases > http://www.eclipse.org/modeling/emf/emf/milestones > http://www.eclipse.org/modeling/emf/emf/integration > +1. Having every modeling project releng maintaining their own releases, milestones and integration repositories would produce an always updated modeling composite repository. MDT/OCL project is currently using the configuration described by Dennis. Regards, Adolfo.
Dennis, It would be really nice to have the composite you suggest! Let me know when it's done and I'll change these to reference them.
(In reply to comment #81) > Dennis, > > It would be really nice to have the composite you suggest! > > Let me know when it's done and I'll change these to reference them. Here they are: https://bugs.eclipse.org/bugs/show_bug.cgi?id=383208 On 27. June I will add the 2.8 contribution.
Closing after almost 8 years of inactivity.
