Bugzilla – Full Text Bug Listing
| Summary: | Drag and Drop broken in Ecore Model Editor - NPE | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | <h1055071> |
| Component: | Edit | Assignee: | Ed Merks <Ed.Merks> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alex.tugarev, brindy, cletavernier, ed, erdal.karaca.de, IngedevTeam.fr, Kenn.Hussey, kutter, milesparker, mlehmannm, nicolas.bros, robert.blust |
| Version: | 2.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
*** Bug 359756 has been marked as a duplicate of this bug. *** We get the same thing - even after regenerating all our code. *** Bug 361542 has been marked as a duplicate of this bug. *** Not to be a pain, but any hints about when a fix w/ nightly build might be available? (I just ask because I can't seem to get my build system to use 2.7.0.) (In reply to comment #4) > Not to be a pain, but any hints about when a fix w/ nightly build might be > available? (I just ask because I can't seem to get my build system to use > 2.7.0.) Yeah, we had the same problem. Luckily someone on our team hadn't updated (me) so I ended up copying my Eclipse install to the rest of the team. However, for the build of our RCP product, we just went through the dependencies and changed the minimum version to 2.7.0 inclusive and maximum to 2.7.1 *exclusive*. This is a real pain though! (In reply to comment #5) > However, for the build of our RCP product, we just went through the > dependencies and changed the minimum version to 2.7.0 inclusive and maximum to > 2.7.1 *exclusive*. Yeah, I tried that, but Buckminster chokes because for some reason it thinks it can't find the older version. There's probably a setting hidden somewhere for that.. <sigh> Did you guys have to change anything on your build / P2 side? (In reply to comment #6) > (In reply to comment #5) > > However, for the build of our RCP product, we just went through the > > dependencies and changed the minimum version to 2.7.0 inclusive and maximum to > > 2.7.1 *exclusive*. > > Yeah, I tried that, but Buckminster chokes because for some reason it thinks it > can't find the older version. There's probably a setting hidden somewhere for > that.. <sigh> Did you guys have to change anything on your build / P2 side? We use Tycho and it magically (thankfully) just worked. The fix is committed for 2.7.1 and 2.8.0. Builds for both will hopefully happen later this week. Marking as resolve. *** Bug 362543 has been marked as a duplicate of this bug. *** Ed, where are these updates hosted? I tried the http://download.eclipse.org/modeling/emf/updates/.. sites, but those are wildly out of data so they must have moved.. Indigo site only has the 0913 build, of course. Miles. I recently asked about the problem in the newsgroup, and Ed Willink pointed me to the place with the dail update sites. You should find the messages. Regards, Philipp (In reply to comment #11) > Ed, where are these updates hosted? I tried the > http://download.eclipse.org/modeling/emf/updates/.. sites, but those are wildly > out of data so they must have moved.. Indigo site only has the 0913 build, of > course. There's the aggregate http://downloads.eclipse.org/modeling/updates and the subsites interim, milestones, and releases. (In reply to comment #13) > http://downloads.eclipse.org/modeling/updates I think you mean.. http://download.eclipse.org/modeling/updates but P2 doesn't like that or http://download.eclipse.org/modeling/updates/milestones either. Ed W.s solution is to grab the update site which should work, but of course it would be better to have this from a P2 site for automated builds. See also bug 364186. I can't remember if there is an automated build on Hudson, or perhaps that is waiting for the git transition, etc.. The fix was in M3 so http://download.eclipse.org/releases/staging should do. Thanks Ed(s). We need the fixed 2.7.1 build, really, unless perhaps 2.8.0 M3 is quite stable. I'm thinking it could be in Indigo SR2 staging, but I'm not sure such a beastie exists. (In reply to comment #16) > We need the fixed 2.7.1 build Try http://download.eclipse.org/modeling/emf/emf/updates/2.7.x (In reply to comment #17) > (In reply to comment #16) > > We need the fixed 2.7.1 build The 2.7.1 release is in the 2.7 site (http://download.eclipse.org/modeling/emf/emf/updates/2.7) and also in the general EMF release site (http://download.eclipse.org/modeling/emf/emf/updates) which is also included in the modeling site (http://www.eclipse.org/modeling/updates). > > Try http://download.eclipse.org/modeling/emf/emf/updates/2.7.x Maintenance builds towards 2.7.2 are found here, as Ed has suggested. (In reply to comment #13) > There's the aggregate > > http://downloads.eclipse.org/modeling/updates > > and the subsites interim, milestones, and releases. Note that the composites need to be updated to pick up interim and milestone builds for more recent EMF releases (i.e., 2.7.2 and 2.8). Will attach a patch to bug 314388 shortly. (In reply to comment #17) > (In reply to comment #16) > > We need the fixed 2.7.1 build > > Try http://download.eclipse.org/modeling/emf/emf/updates/2.7.x Funny, I though you meant as in: "http://download.eclipse.org/modeling/emf/emf/updates/2.7.2", but it is in fact literally "2.7.x". An interesting example of the ambiguity of human conventions vs. code. In any case, that works perfectly, thanks all. A request that when there is a release version available at a permanent site that someone updates this bug with that info. The changes are available in builds. Thanks it work great. Is there a minor release planned before SR2 ? *** Bug 368608 has been marked as a duplicate of this bug. *** |