Re: [cross-project-issues-dev] Xtext M4 ?
On Wed, Dec 14, 2011 at 3:01 PM, Dennis Hübner wrote: > Am 14.12.11 20:52, schrieb Thomas Hallgren: > > On 2011-12-14 20:44, Dennis Hübner wrote: > > > > I think it's also a good idea to point b3 aggregator to projects nightly > > update site after a milestone is released. > > So dependent projects can earlier react to probably breaking changes. > > > Keep in mind though, that many project build nightlys produce version > qualifiers > that starts with 'N' and that this often break the version semantics when > intermixed with other types of builds. > > That's new to me. I thought all project should use > X.Y.Z.vBUILD-QUALIFIER. [1] > Thank for this info Thomas. > > [1] http://wiki.eclipse.org/Version_Numbering > > PDE has this support for the nightlies where the fetchTag is HEAD (instead of the qualifier in the maps), and when using the generic fetchTag the qualifier gets set to N- Interestingly with the switch to git, we've switched to a convention where the qualifier in the map is the v of the last commit to touch a given bundle/project. That same practice could be applied to nightlies since it is invariant with the same build input. In the Eclipse SDK case, that still wouldn't allow easy intermingling of types of builds as the product qualifier *is* changed on every build and in our case would swap between N- and I- PW -- Paul Webster Hi floor. Make me a sammich! - GIR ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
2011/12/14 Dennis Hübner > > Am 14.12.11 20:17, schrieb Adolfo Sanchez Barbudo: > > I actually thought that the "milestones" repository was the ideal > candidate, in this case. > > I don't think that "milestones" is the ideal candidate for downstream > projects. > At least not after the latest RC, which will be rebuild as release in the > most cases. > It's not our case. We build RCs as usual S-builds which are published in the milestones repository. Our releases repository only contains the final Releases, which usually comes from (copyed) the last built RC. So you have to switch to releases update site, to build against the final > version of projects you depends on. > Anyway, if you as e.g +3 project operate against the juno > aggregation/staging repository, > you can be sure, you get the right +2 dependencies for each > milestone/release. > This doesn't sound bad. Essentially, I only want the repository locations which are supposed to be contributed (generally - so far :P -, milestones repositories). Your points looks likea a practical idea to ensure we are building our milestones against the different artifacts which are currently contributed. Regards, Adolfo. > > > In fact, it's not a problem of having different > timing in the releases dates, but the different repositories in which the > different releases are placed Perhaps a simply (temporal) redirection > from the "milestones" composite repository to the new released stuff would > have sufficed in this case It's much easier make the releng of a > project configure the repositories that he/she controls than making the > releng of the downstream projects look into such an issue. > > I think it's also a good idea to point b3 aggregator to projects nightly > update site after a milestone is released. > So dependent projects can earlier react to probably breaking changes. > > > Regards, > Dennis. > > Cheers, > Adolfo. > 2011/12/14 Miles Parker > > I had thought last year that this was what aggregator was for, that is > that we could use the update sites indicated in the aggregator, but I > discovered that I was wrong. Perhaps we should legislate having that be in > sync, or add a separate set for Interim and Nightlies?It sure would be nice > to find out what version of dependencies we should be using without having > to consult typically out of date project web sites. > > On Dec 14, 2011, at 10:53 AM, John Arthorne wrote: > > The general form of this question would be good input for Wayne and his > project page organization. Currently projects declare with a flag that they > are participating in the simultaneous release, but there is no record that > I am aware of indicating which release they will contribute. For projects > whose own schedule matches the cadence of the release train this is fairly > obvious. But for other projects with more frequent releases I don't think > this information is available. To pick a random example, this morning I was > asking what release of Jetty would be in Juno and the answer wasn't so > clear. Maybe the juno "participation" flag should be metadata on a release > rather than just a generic flag on the project? For downstream projects and > consumers I expect this information would be really helpful. > > John > > > > > *Adolfo Sanchez Barbudo > * > Sent by: cross-project-issues-dev-boun...@eclipse.org > > > 12/14/2011 10:20 AM > Please respond to > Cross project issues > > > tocross-project-issues-...@eclipse.org > > cc > Subject > [cross-project-issues-dev] Xtext M4 ? > > > > > Hello Folks > > I'm wondering if Xtext guys are going to create any kind of milestone for > M4. > > Looking at their milestones repository[1] I only see an old 2.1.0M2. > > I don't find any clue in the project plan [2] neither . > > Any reason about why there is no an updated milestones repository would be > appreciated. Take into account that our milestones builds are based on > milestones repositories for those projects we depend on, so keeping the > usual (probably planned) milestones releases are important for us. > > [1] > *http://download.eclipse.org/modeling/tmf/xtext/updates/milestones*<http://download.eclipse.org/modeling/tmf/xtext/updates/milestones> > <http://download.eclipse.org/modeling/tmf/xtext/updates/milestones> > [2] > *http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext > *<http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext> > > <http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xt
Re: [cross-project-issues-dev] Xtext M4 ?
Am 14.12.11 20:52, schrieb Thomas Hallgren: > On 2011-12-14 20:44, Dennis Hübner wrote: > > > > I think it's also a good idea to point b3 aggregator to projects nightly > > update site after a milestone is released. > > So dependent projects can earlier react to probably breaking changes. > > > Keep in mind though, that many project build nightlys produce version > qualifiers > that starts with 'N' and that this often break the version semantics when > intermixed with other types of builds. That's new to me. I thought all project should use X.Y.Z.vBUILD-QUALIFIER. [1] Thank for this info Thomas. [1] http://wiki.eclipse.org/Version_Numbering > > - thomas > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dennis Hübner Softwareentwickler Mobil: 0151 173 96 707 http://www.itemis.de/ itemis AG Am Germaniahafen 1 24143 Kiel Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Wolfgang Neuhaus, Jens Wagener, Dr. Georg Pietrek Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
Yes, I think that would make sense for the given infrastructure. To be clear, what I was suggesting was not to necessarily actually *use* the meta-data for nightly and interim sites but simply to *track* them in addition to the milestone sites so that consumers could know with certainty what evolving target they're supposed to be building against. I've been in a situation where I thought I was building to the current repos for a dependency (my project has a very large number of such), but I'd actually been building against a non-maintained 'interim' site that only included stuff from the Helios release. I didn't figure that out until RC1 when my older dependency no longer worked. A significant advantage of that is that we could eventually build part of the project meta-data for the web sites from the aggregator so that any consumers would be pointed to the blessed version of each build site. It seems that almost every project has multiple old update sites out there and it is often an exercise in googling and trial and error to find the correct up to date site. -Miles (aka 'the universal consumer') On Dec 14, 2011, at 11:44 AM, Dennis Hübner wrote: >> > I think it's also a good idea to point b3 aggregator to projects nightly > update site after a milestone is released. > So dependent projects can earlier react to probably breaking changes. > > Regards, > Dennis. > >> >> Cheers, >> Adolfo. >> 2011/12/14 Miles Parker >> >>> I had thought last year that this was what aggregator was for, that is >>> that we could use the update sites indicated in the aggregator, but I >>> discovered that I was wrong. Perhaps we should legislate having that be in >>> sync, or add a separate set for Interim and Nightlies?It sure would be nice >>> to find out what version of dependencies we should be using without having >>> to consult typically out of date project web sites. >>> >>> On Dec 14, 2011, at 10:53 AM, John Arthorne wrote: >>> >>> The general form of this question would be good input for Wayne and his >>> project page organization. Currently projects declare with a flag that they >>> are participating in the simultaneous release, but there is no record that >>> I am aware of indicating which release they will contribute. For projects >>> whose own schedule matches the cadence of the release train this is fairly >>> obvious. But for other projects with more frequent releases I don't think >>> this information is available. To pick a random example, this morning I was >>> asking what release of Jetty would be in Juno and the answer wasn't so >>> clear. Maybe the juno "participation" flag should be metadata on a release >>> rather than just a generic flag on the project? For downstream projects and >>> consumers I expect this information would be really helpful. >>> >>> John >>> >>> >>> >>> >>> *Adolfo Sanchez Barbudo * >>> Sent by: cross-project-issues-dev-boun...@eclipse.org >>> >>> 12/14/2011 10:20 AM >>> Please respond to >>> Cross project issues >>> >>> To >>> cross-project-issues-dev@eclipse.org >>> cc >>> Subject >>> [cross-project-issues-dev] Xtext M4 ? >>> >>> >>> >>> >>> Hello Folks >>> >>> I'm wondering if Xtext guys are going to create any kind of milestone for >>> M4. >>> >>> Looking at their milestones repository[1] I only see an old 2.1.0M2. >>> >>> I don't find any clue in the project plan [2] neither . >>> >>> Any reason about why there is no an updated milestones repository would be >>> appreciated. Take into account that our milestones builds are based on >>> milestones repositories for those projects we depend on, so keeping the >>> usual (probably planned) milestones releases are important for us. >>> >>> [1] >>> *http://download.eclipse.org/modeling/tmf/xtext/updates/milestones*<http://download.eclipse.org/modeling/tmf/xtext/updates/milestones> >>> [2] * >>> http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext >>> *<http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext> >>> >>> P.S: I've not checked other itemis projects (xpand, mwe), but I guess we >>> will have the same problem with them. >>> >>> Best Regards, >>> Adolfo._
Re: [cross-project-issues-dev] Xtext M4 ?
On 2011-12-14 20:44, Dennis Hübner wrote: I think it's also a good idea to point b3 aggregator to projects nightly update site after a milestone is released. So dependent projects can earlier react to probably breaking changes. Keep in mind though, that many project build nightlys produce version qualifiers that starts with 'N' and that this often break the version semantics when intermixed with other types of builds. - thomas ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
Am 14.12.11 20:17, schrieb Adolfo Sanchez Barbudo: > I actually thought that the "milestones" repository was the ideal > candidate, in this case. I don't think that "milestones" is the ideal candidate for downstream projects. At least not after the latest RC, which will be rebuild as release in the most cases. So you have to switch to releases update site, to build against the final version of projects you depends on. Anyway, if you as e.g +3 project operate against the juno aggregation/staging repository, you can be sure, you get the right +2 dependencies for each milestone/release. > In fact, it's not a problem of having different > timing in the releases dates, but the different repositories in which the > different releases are placed Perhaps a simply (temporal) redirection > from the "milestones" composite repository to the new released stuff would > have sufficed in this case It's much easier make the releng of a > project configure the repositories that he/she controls than making the > releng of the downstream projects look into such an issue. I think it's also a good idea to point b3 aggregator to projects nightly update site after a milestone is released. So dependent projects can earlier react to probably breaking changes. Regards, Dennis. > > Cheers, > Adolfo. > 2011/12/14 Miles Parker > >> I had thought last year that this was what aggregator was for, that is >> that we could use the update sites indicated in the aggregator, but I >> discovered that I was wrong. Perhaps we should legislate having that be in >> sync, or add a separate set for Interim and Nightlies?It sure would be nice >> to find out what version of dependencies we should be using without having >> to consult typically out of date project web sites. >> >> On Dec 14, 2011, at 10:53 AM, John Arthorne wrote: >> >> The general form of this question would be good input for Wayne and his >> project page organization. Currently projects declare with a flag that they >> are participating in the simultaneous release, but there is no record that >> I am aware of indicating which release they will contribute. For projects >> whose own schedule matches the cadence of the release train this is fairly >> obvious. But for other projects with more frequent releases I don't think >> this information is available. To pick a random example, this morning I was >> asking what release of Jetty would be in Juno and the answer wasn't so >> clear. Maybe the juno "participation" flag should be metadata on a release >> rather than just a generic flag on the project? For downstream projects and >> consumers I expect this information would be really helpful. >> >> John >> >> >> >> >> *Adolfo Sanchez Barbudo * >> Sent by: cross-project-issues-dev-boun...@eclipse.org >> >> 12/14/2011 10:20 AM >> Please respond to >> Cross project issues >> >> To >> cross-project-issues-dev@eclipse.org >> cc >> Subject >> [cross-project-issues-dev] Xtext M4 ? >> >> >> >> >> Hello Folks >> >> I'm wondering if Xtext guys are going to create any kind of milestone for >> M4. >> >> Looking at their milestones repository[1] I only see an old 2.1.0M2. >> >> I don't find any clue in the project plan [2] neither . >> >> Any reason about why there is no an updated milestones repository would be >> appreciated. Take into account that our milestones builds are based on >> milestones repositories for those projects we depend on, so keeping the >> usual (probably planned) milestones releases are important for us. >> >> [1] >> *http://download.eclipse.org/modeling/tmf/xtext/updates/milestones*<http://download.eclipse.org/modeling/tmf/xtext/updates/milestones> >> [2] * >> http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext >> *<http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext> >> >> P.S: I've not checked other itemis projects (xpand, mwe), but I guess we >> will have the same problem with them. >> >> Best Regards, >> Adolfo.___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> >> ___ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> &g
Re: [cross-project-issues-dev] Xtext M4 ?
This is as serious deficiency in the portal. There is a huge disconnect between the simultaneous release, releases, reviews, and just about everything else. I'm hoping to address with this with Bug 366466 and Bug 363524. Currently, I use some very fragile logic to form an implicit connection. I look for release(s) in the project metadata that fall on the same date as the simultaneous release. You'll notice that the Eclipse project has two such releases. Note that milestone releases are ignored. Wayne On 12/14/2011 01:53 PM, John Arthorne wrote: The general form of this question would be good input for Wayne and his project page organization. Currently projects declare with a flag that they are participating in the simultaneous release, but there is no record that I am aware of indicating which release they will contribute. For projects whose own schedule matches the cadence of the release train this is fairly obvious. But for other projects with more frequent releases I don't think this information is available. To pick a random example, this morning I was asking what release of Jetty would be in Juno and the answer wasn't so clear. Maybe the juno "participation" flag should be metadata on a release rather than just a generic flag on the project? For downstream projects and consumers I expect this information would be really helpful. John Adolfo Sanchez Barbudo Sent by: cross-project-issues-dev-boun...@eclipse.org 12/14/2011 10:20 AM Please respond to Cross project issues To cross-project-issues-dev@eclipse.org cc Subject [cross-project-issues-dev] Xtext M4 ? Hello Folks I'm wondering if Xtext guys are going to create any kind of milestone for M4. Looking at their milestones repository[1] I only see an old 2.1.0M2. I don't find any clue in the project plan [2] neither . Any reason about why there is no an updated milestones repository would be appreciated. Take into account that our milestones builds are based on milestones repositories for those projects we depend on, so keeping the usual (probably planned) milestones releases are important for us. [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones [2] http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext P.S: I've not checked other itemis projects (xpand, mwe), but I guess we will have the same problem with them. Best Regards, Adolfo.___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
I actually thought that the "milestones" repository was the ideal candidate, in this case. In fact, it's not a problem of having different timing in the releases dates, but the different repositories in which the different releases are placed Perhaps a simply (temporal) redirection from the "milestones" composite repository to the new released stuff would have sufficed in this case It's much easier make the releng of a project configure the repositories that he/she controls than making the releng of the downstream projects look into such an issue. Cheers, Adolfo. 2011/12/14 Miles Parker > > I had thought last year that this was what aggregator was for, that is > that we could use the update sites indicated in the aggregator, but I > discovered that I was wrong. Perhaps we should legislate having that be in > sync, or add a separate set for Interim and Nightlies?It sure would be nice > to find out what version of dependencies we should be using without having > to consult typically out of date project web sites. > > On Dec 14, 2011, at 10:53 AM, John Arthorne wrote: > > The general form of this question would be good input for Wayne and his > project page organization. Currently projects declare with a flag that they > are participating in the simultaneous release, but there is no record that > I am aware of indicating which release they will contribute. For projects > whose own schedule matches the cadence of the release train this is fairly > obvious. But for other projects with more frequent releases I don't think > this information is available. To pick a random example, this morning I was > asking what release of Jetty would be in Juno and the answer wasn't so > clear. Maybe the juno "participation" flag should be metadata on a release > rather than just a generic flag on the project? For downstream projects and > consumers I expect this information would be really helpful. > > John > > > > > *Adolfo Sanchez Barbudo * > Sent by: cross-project-issues-dev-boun...@eclipse.org > > 12/14/2011 10:20 AM > Please respond to > Cross project issues > > To > cross-project-issues-dev@eclipse.org > cc > Subject > [cross-project-issues-dev] Xtext M4 ? > > > > > Hello Folks > > I'm wondering if Xtext guys are going to create any kind of milestone for > M4. > > Looking at their milestones repository[1] I only see an old 2.1.0M2. > > I don't find any clue in the project plan [2] neither . > > Any reason about why there is no an updated milestones repository would be > appreciated. Take into account that our milestones builds are based on > milestones repositories for those projects we depend on, so keeping the > usual (probably planned) milestones releases are important for us. > > [1] > *http://download.eclipse.org/modeling/tmf/xtext/updates/milestones*<http://download.eclipse.org/modeling/tmf/xtext/updates/milestones> > [2] * > http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext > *<http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext> > > P.S: I've not checked other itemis projects (xpand, mwe), but I guess we > will have the same problem with them. > > Best Regards, > Adolfo.___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
I had thought last year that this was what aggregator was for, that is that we could use the update sites indicated in the aggregator, but I discovered that I was wrong. Perhaps we should legislate having that be in sync, or add a separate set for Interim and Nightlies?It sure would be nice to find out what version of dependencies we should be using without having to consult typically out of date project web sites. On Dec 14, 2011, at 10:53 AM, John Arthorne wrote: > The general form of this question would be good input for Wayne and his > project page organization. Currently projects declare with a flag that they > are participating in the simultaneous release, but there is no record that I > am aware of indicating which release they will contribute. For projects whose > own schedule matches the cadence of the release train this is fairly obvious. > But for other projects with more frequent releases I don't think this > information is available. To pick a random example, this morning I was asking > what release of Jetty would be in Juno and the answer wasn't so clear. Maybe > the juno "participation" flag should be metadata on a release rather than > just a generic flag on the project? For downstream projects and consumers I > expect this information would be really helpful. > > John > > > > > Adolfo Sanchez Barbudo > Sent by: cross-project-issues-dev-boun...@eclipse.org > 12/14/2011 10:20 AM > Please respond to > Cross project issues > > To > cross-project-issues-dev@eclipse.org > cc > Subject > [cross-project-issues-dev] Xtext M4 ? > > > > > > Hello Folks > > I'm wondering if Xtext guys are going to create any kind of milestone for M4. > > Looking at their milestones repository[1] I only see an old 2.1.0M2. > > I don't find any clue in the project plan [2] neither . > > Any reason about why there is no an updated milestones repository would be > appreciated. Take into account that our milestones builds are based on > milestones repositories for those projects we depend on, so keeping the usual > (probably planned) milestones releases are important for us. > > [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones > [2] > http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext > > P.S: I've not checked other itemis projects (xpand, mwe), but I guess we will > have the same problem with them. > > Best Regards, > Adolfo.___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
The general form of this question would be good input for Wayne and his project page organization. Currently projects declare with a flag that they are participating in the simultaneous release, but there is no record that I am aware of indicating which release they will contribute. For projects whose own schedule matches the cadence of the release train this is fairly obvious. But for other projects with more frequent releases I don't think this information is available. To pick a random example, this morning I was asking what release of Jetty would be in Juno and the answer wasn't so clear. Maybe the juno "participation" flag should be metadata on a release rather than just a generic flag on the project? For downstream projects and consumers I expect this information would be really helpful. John Adolfo Sanchez Barbudo Sent by: cross-project-issues-dev-boun...@eclipse.org 12/14/2011 10:20 AM Please respond to Cross project issues To cross-project-issues-dev@eclipse.org cc Subject [cross-project-issues-dev] Xtext M4 ? Hello Folks I'm wondering if Xtext guys are going to create any kind of milestone for M4. Looking at their milestones repository[1] I only see an old 2.1.0M2. I don't find any clue in the project plan [2] neither . Any reason about why there is no an updated milestones repository would be appreciated. Take into account that our milestones builds are based on milestones repositories for those projects we depend on, so keeping the usual (probably planned) milestones releases are important for us. [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones [2] http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext P.S: I've not checked other itemis projects (xpand, mwe), but I guess we will have the same problem with them. Best Regards, Adolfo.___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
Hello Dennis, 2011/12/14 Dennis Hübner > Hello Adolfo, > we've released Xtext 2.2.1 which is our Juno M4 contribution. Please use > the releases update site. > I have temporally changed that to produce proper OCL tools contribution... but... To be sure what is in juno aggregator, consider to look in > tmf-xtext.b3aggrcon file (the same for Xpand and MWE). > ... I'd prefer having every project producing their artifacts in the proper repository to avoid unnecessary investigations about where is the content which should feed our target platform. Cheers, Adolfo. > I'm not sure why the project-plan site is not up to date, sorry for that. > :( > > Best regards, > Dennis Huebner. > > Am 14.12.2011 um 16:20 schrieb Adolfo Sanchez Barbudo: > > Hello Folks > > I'm wondering if Xtext guys are going to create any kind of milestone for > M4. > > Looking at their milestones repository[1] I only see an old 2.1.0M2. > > I don't find any clue in the project plan [2] neither . > > Any reason about why there is no an updated milestones repository would be > appreciated. Take into account that our milestones builds are based on > milestones repositories for those projects we depend on, so keeping the > usual (probably planned) milestones releases are important for us. > > [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones > [2] > http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext > > P.S: I've not checked other itemis projects (xpand, mwe), but I guess we > will have the same problem with them. > > Best Regards, > Adolfo. > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Xtext M4 ?
Hello Adolfo, we've released Xtext 2.2.1 which is our Juno M4 contribution. Please use the releases update site. To be sure what is in juno aggregator, consider to look in tmf-xtext.b3aggrcon file (the same for Xpand and MWE). I'm not sure why the project-plan site is not up to date, sorry for that. :( Best regards, Dennis Huebner. Am 14.12.2011 um 16:20 schrieb Adolfo Sanchez Barbudo: > Hello Folks > > I'm wondering if Xtext guys are going to create any kind of milestone for M4. > > Looking at their milestones repository[1] I only see an old 2.1.0M2. > > I don't find any clue in the project plan [2] neither . > > Any reason about why there is no an updated milestones repository would be > appreciated. Take into account that our milestones builds are based on > milestones repositories for those projects we depend on, so keeping the usual > (probably planned) milestones releases are important for us. > > [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones > [2] > http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext > > P.S: I've not checked other itemis projects (xpand, mwe), but I guess we will > have the same problem with them. > > Best Regards, > Adolfo. > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Xtext M4 ?
Hello Folks I'm wondering if Xtext guys are going to create any kind of milestone for M4. Looking at their milestones repository[1] I only see an old 2.1.0M2. I don't find any clue in the project plan [2] neither . Any reason about why there is no an updated milestones repository would be appreciated. Take into account that our milestones builds are based on milestones repositories for those projects we depend on, so keeping the usual (probably planned) milestones releases are important for us. [1] http://download.eclipse.org/modeling/tmf/xtext/updates/milestones [2] http://www.eclipse.org/projects/project-plan.php?projectid=modeling.tmf.xtext P.S: I've not checked other itemis projects (xpand, mwe), but I guess we will have the same problem with them. Best Regards, Adolfo. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
