k3 icon indicating copy to clipboard operation
k3 copied to clipboard

action language providing open class mechanism to xtend/java

Results 40 k3 issues
Sort by recently updated
recently updated
newest added

The template generator that generates aspect from an ecore file currently supports single inheritance only (. (new K3 project, next, select _User Ecore Basic aspect_ template ) since we now...

enhancement

K3AL should always check _self against null. It is a nightmare to debug otherwise because xtend will enter the method even when called on a null object. ``` public static...

enhancement

When generating the java code from an extended metamodel, implement the java method body to call the proper java static methods generated by K3AL. F.

enhancement
k3sle

The way K3 generates Java code for aspects prevents the use of extension fields, see below: ``` abstract class ExtensionProvider { def void foo(String s) } class Test { extension...

bug

The new K3 project wizard allows to create a plugin. Usually plugin offer an Activator. we should generate one in the wizard. If possible this activator shoud suggest the use...

enhancement

Given the following piece of metamodel: ![2014-06-19_1158](https://cloud.githubusercontent.com/assets/6389784/3326076/59c5cf00-f798-11e3-9a33-a272e46a6616.png) See ActionSequenceAspect, this code will call the correct perform operation (ie operation from the aspect) if and only if the perform operation is...

enhancement

If an aspect is written as followed: ``` def private init() { _self._isInitialized = true; } ``` JAVA code is not properly geneated as the method _privk3_init does not return...

si un aspect est délcaré comme ceci: ``` java @Aspect(className=System) class SystemAspect { public LinkedListMultimap sharedMemory = LinkedListMultimap.create } ``` L'affectation ne passe pas par la méthode SystemAspect.sharedMemory(System, LinkedListMultimap) mais...

enhancement

In @Contracted, invariants and pre/postconditions checks are currently mixed. Thus, a violated invariant will result in either a PreConditionViolationException or PostConditionViolationException, depending on whether the violation occurs when calling or...

enhancement

@Opposite works great within plain Java types, but not within an @Aspect class. The following doesn't compile. Basically, the two processors are in conflict. ``` class BaseA {} class BaseB...

bug