|
|
|
|
|
|
|
|
| Re: Impossible to use External Java Action [message #1728265 is a reply to message #1728213] |
Fri, 01 April 2016 09:02   |
Eclipse User |
|
|
|
Hi
Le 01/04/2016 01:15, Frank Sorek a écrit :
> If I understand correctly, you have to create the Java Extensions in
> your first Eclipse. So create a new project next to your
> model/edit/editor project. I had a similar problem when I wanted to
> implement custom styles. In your "2nd eclipse" you have to add the Java
> Extension Project to the Dependencies.
> Hope this helps :)
This is a solution (which could allow to share some external java action
between different modelers without dependencies between the
corresponding plugins), but it requires to define a separated plugin.
What I called developpement mode ou live editing mode is simply the fact
to have your Viewpoint Specification Project in the same workspace than
your sample date (aird and domain model), so you can modify you odesign,
save and in live see the impacts ont your modeler. In your case your are
in a Runtime launched from a workspace containing your metamodel plugins.
If you want to use External Java Action but keep this External Java
Action in the same plugin than the odesign, I see two options:
. launch a second runtime from the runtime to edit your sample data
and test the modeler. However you will have to restart this runtime to
see the changes you make on the modeler, you are no more in this "Live
Editing Mode"
. put your Viewpoint Specification Project in the same workspace than
the metamodel plugins, launch a runtime so that it is deployed and then
import the project (without copying it) in the runtime workspace. Then
you will have the possibility to edit the odesign in the runtime and see
the impact on the test data. You just have ti pay attention when you
select the Viewpoints on your test Modeling Project: select the
Viewpoint from the workspace (see the decorators).
Regards,
--
Maxime - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
|
|
| Re: Impossible to use External Java Action [message #1823787 is a reply to message #1805351] |
Thu, 02 April 2020 02:33 |
| Eclipse User |
|
|
|
I checked and as of today, you still need to have the java action installed prior to launching the development workspace.
Specifically, what I do is one of two things:
1. For debugging the java action itself - I run another runtime environment from the development runtime environment (X.design). It's not smooth, but it's less demanding than creating a new plugin and installing it and then realizing the java action is not working well. One tip I can offer is that you can use the same sample project you use for debugging in the development environment for the new runtime (just import the project).
2. After the java action is working well, I deploy it (in a plugin), and then continue to work with the environment of the X.design project.
|
|
|
Powered by
FUDForum. Page generated in 0.06515 seconds
Home
