Updates:
Status: Duplicate
Labels: -Component-Tools
Mergedinto: 533
Comment #6 on issue 187 by tudor.gi...(a)gmail.com: infusion does not set
Invocation#receiver?
http://code.google.com/p/moose-technology/issues/detail?id=187
(No comment was entered for this change.)
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.4
New issue 551 by tudor.gi...(a)gmail.com: VerveineJ should export
parameterized types
http://code.google.com/p/moose-technology/issues/detail?id=551
These are the Java Generics.
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-VerveineJ
New issue 548 by tudor.gi...(a)gmail.com: VerveineJ should export both
packages and namespaces
http://code.google.com/p/moose-technology/issues/detail?id=548
Because the Java package plays both the role of a FAMIX namespace and of a
FAMIX package, VerveineJ should export both.
Excellent!
Regarding the problem: parentModule comes from the C extension which you got because you exported the complete meta-model. You should use parentScope.
Cheers,
Doru
On 10 Mar 2011, at 10:25, Nicolas Anquetil wrote:
>
> I generated the new Famix Java.
>
> There is one error in ScopingEntity :
>
> @FameProperty(name = "globalVariables", opposite = "parentModule", derived = true)
> public Collection<GlobalVariable> getGlobalVariables() {
> if (globalVariables == null) {
> globalVariables = new MultivalueSet<GlobalVariable>() {
> @Override
> protected void clearOpposite(GlobalVariable e) {
> e.setParentModule(null);
> }
> @Override
> protected void setOpposite(GlobalVariable e) {
> e.setParentModule(ScopingEntity.this);
> here ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> setParentModule wants a Module and not a Scope
> }
> };
> }
> return globalVariables;
> }
>
--
www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
I am in the process (that is, when my mind is not full with the 1000 things to do when moving to a new city) of refactoring package blueprints, with multiple objectives in mind:
- make package blueprints work with namespaces
- a testbed for Chef queries
- rewriting the code to make it a bit more object-oriented
- add tests
There is one loophole I would like to expose and get your opinion about. Package blueprints shows references between classes across packages. Unfortunately nothing has been planned to handle class extensions. Right now there are just ignored so the picture given by package blueprints might be incomplete (but not false).
I don't plan for now to do something about this but if some people want to give a thought about this and later add their idea, they are welcome.
--
Simon Denier
Hi all,
What do you think about integrate Fuel in next release of Moose ?
It seems to work well, so it is a good candidate to save models.
Cheers
---
Jannik Laval
Hi!
I am ready to continue working on the Fuel extension for binary
export/import in Moose.
I am working on:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
Tasks:
- create ConfigurationOfFuel with a default config
- fix an error running tests (I thin the problem raises because now
I'm on Windows, not MacOs)
- fix a buf found by Doru last time: "a bug with FAMIXAccess that when
the isWrite flag was nil, isRead would raise an error (it is fixed in
the meantime). This appeared when I exported the model with MSE, but
it did not appear when I used Fuel".
- fix the icon for Fuel import in MoosePanel.
Is this ok?
Cheers,
Martin
Hi All,
Vanessa and I are running an experiment about measuring and increasing the test coverage. We choose to do this on Moose, and especially on Moose-Core.
We have some questions:
- What do we do with deprecated classes and method? For example MooseIntegerIdGenerator is used nowhere. I think it can be safely removed. It is referenced nowhere in 4.4
- Is the following used?
MooseElement>>navigationPragma
<pragmas: #instance>
<pragmas: #class>
^#(#navigation:)
and its friends like menuPragma, propertyPragma and expressionPragma? I cannot find sender of them
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.