| Summary: | New M6 NPE running Acceleo standalone | ||
|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | laurent.goubet, nicolas.bros |
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Ed Willink
The "isInDynamicBundle" code is something that has been included -very- late in the M6 cycle so that we had the whole necessary API to handle dynamic metamodels; and we've all the trouble we've faced with the M6 build, I admit I haven't taken enough time to test this version. This one is indeed the very same bug as bug 336119, a regression with the standalone mode (AcceleoWorkspaceUtil should never be called from standalone :s). I just raised bug 340127 in order to try and prevent these regressions in the future. As for this bug, it is fixed on HEAD. A nightly should be available soon. I think M6 has enough fatal bugs on standalone and on dynamic models to merit an M6a. One of the bugs we introduced (bug 340094) cannot be fixed soon enough to be part of an M6x milestone, we'll have it fixed asap, but it will be part of an integration build next week at best. (In reply to comment #1) > As for this bug, it is fixed on HEAD. A nightly should be available soon. Where? The Acceleo download page doesn't show N-builds. The Hudson Job shows no build artefacts since M6. I was expecting to have part of the fix for bug #340094 before launching the nightly ... and forgot to launch it altogether at the end of the day ... The nightly is running and will be promoted shortly. I expect to have an I build launched and promoted as soon as bug #340094 is out of the way. Acceleo 3.1.0M6a, including this fix, is now available from the milestones update site. *** Bug 342298 has been marked as a duplicate of this bug. *** |