Community
Participate
Working Groups
The secondary Dali dependencies (EMF Transaction and Validation) need to be updated to their Indigo versions (1.5.0). This should be done to align with what will be installed from the Indigo repository when the JPA Diagram Editor is selected. Graphiti 0.8 requires versions 1.4 or higher of these dependencies, so 1.5 is a valid and preferred option.
David...let me know how you want to precede with this. Tran can make the changes, but wasn't sure if you wanted to do a build for this, or edit the website. I assume build, but thought I would ask. PMC approval would be requested for any change.
Yeah, I think we should rebuild ... since it has been a long time ... potentially larger differences. There's a build running that has all the other updates for prereqs I mentioned at PMC meeting (e.g. to Eclipse RC3) so I'd like that to finish normally ... 2 or 3 hours left ... but, after that, it'd be good to do a re-build with these udpates too. Once Tran checks in the changes (and, when the wtp 3.3 I build is no longer running) Tran will have to "manually" start the build ... as its purposely not triggered by releng changes.
PMC notification for this non-code change. Tran will post a patch when it is ready and restart the build to incorporate the changes.
I'm in favor of including this in a build. But, have you check the code against the new versions, in a PDE runtime target? Make sure JPA Diagram editor compiles? No versioning issues? Always a good question :) but, I'm also asking to figure out how to time the update and new build. Even though current build has been running for 7 hours, it is still on the "compile dali sdk" step ... in other words, even if it suddenly started going normal speed, it'd have around 4 hours left. So, if you are confident in the changes, I'd recommend we update the pre-req, and restart the build. Let me know if you'd like to do that ... otherwise, I'll let the current one limp along a little longer. We might have to kill it anyway ... with all the infrastructure problems and people hogging the signing queue :) not sure I'm trusting a build that takes so much longer than usual.
(In reply to comment #4) > I'm in favor of including this in a build. But, have you check the code against > the new versions, in a PDE runtime target? Make sure JPA Diagram editor > compiles? No versioning issues? Yep...everything looks good. Actually, I was surprised to find that the only difference between the 1.4 and 1.5 version is the features themselves. The plugins inside are the same exact versions. > > Always a good question :) but, I'm also asking to figure out how to time the > update and new build. Even though current build has been running for 7 hours, > it is still on the "compile dali sdk" step ... in other words, even if it > suddenly started going normal speed, it'd have around 4 hours left. Yikes...now that is slow. > > So, if you are confident in the changes, I'd recommend we update the pre-req, > and restart the build. Let me know if you'd like to do that ... otherwise, I'll > let the current one limp along a little longer. We might have to kill it anyway > ... with all the infrastructure problems and people hogging the signing queue > :) not sure I'm trusting a build that takes so much longer than usual. Yep...I think we could probably restart, but I'll wait for Tran to vouch for his changes. : )
Created attachment 197182 [details] Proposed patch David, I have tested manually the runtime zip URL and I feel confident about the changes. Please restart the build if it is appropriate.
> Please restart the build if it is appropriate. Ok, I will restart ... I noticed, though, that the compile part of build is (almost) over, so I'll let that part finish, but then cancel and restart, rather than wait for unit tests to run. thanks,
Looks like the build is still really slow. I think that compilation is not through yet!
I think this was resolved in RC4.
