Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EEF] Converting EEF to standalone
| [EEF] Converting EEF to standalone [message #516083] |
Mon, 22 February 2010 12:54  |
 Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
When I added the EEF tutorial to my project, my project already had a standalone product that worked. Now that I have the EEF stuff working, I re-synchronized my product and launched an Eclipse application from the Overview tab of the product page.
My old product ran instead of the EEF changes. I assume there are some changes that need to be made to the product. Maybe the application needs to change.
Does anyone know what changes I need to make to my product in order to get the EEF code to run in my product?
Thanks.
|
|
| |
| Re: [EEF] Converting EEF to standalone [message #516366 is a reply to message #516223] |
Tue, 23 February 2010 13:13  |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
Well, maybe I did not explain it too clearly.
I started with an EMF model named Myapp. I made the genmodel. Then I generated Myapp.edit, Myapp.editor and Myapp.tests (standard EMF stuff).
In the Myapp.editor I added a product based on the editor. I built the product and deployed it and it ran fine.
In this same workspace, I added the EEF code to the Myapp.edit project, and I continued until the EEF code worked all the way through the Myapp.editor. The Myapp.editor works fine with the EEF code added as long as I run it as an Eclipse Application.
Then I tried to rebuild my product. When I rebuild the product, I get this error (and boy is it a long one):
C:\Users\hmiller\workspace_rcp2\.metadata\.plugins\org.eclip se.pde.core\temp\org.eclipse.pde.container.feature\assemble. org.eclipse.pde.container.feature.p2.xml:33: The following error occurred while executing this line:
Target "gather.sources" does not exist in the project "Publish p2 metadata".
Is there something in the EEF code that breaks the product build?
Since the code in the product used the Myapp.editor project, the Dependencies in the product are the same as the Myapp.editor. In other words, the EEF runtime, and the Myapp.edit projects are already dependencies. But the product still will not build.
Should I delete the current product and try to build a new one? Maybe there were so many changes that the old product will not build?
Thanks,
Herb
|
|
| |
| Re: [EEF] Converting EEF to standalone [message #516613 is a reply to message #516366] |
Wed, 24 February 2010 05:18 |
Stephane Bouchet
Messages: 239
Registered: July 2009 |
Senior Member |
|
|
Herb,
As mikes says, i supect too there is somethnig missing on your product
configuration.
If EEF is working well in a runtime, it might work as well in RCP.
did you try to export the 3 projects alone and install them in a fresh
eclipse to simulates the product build ?
Herb Miller a écrit :
> Well, maybe I did not explain it too clearly.
>
> I started with an EMF model named Myapp. I made the genmodel. Then I
> generated Myapp.edit, Myapp.editor and Myapp.tests (standard EMF stuff).
>
> In the Myapp.editor I added a product based on the editor. I built the
> product and deployed it and it ran fine.
>
> In this same workspace, I added the EEF code to the Myapp.edit project,
> and I continued until the EEF code worked all the way through the
> Myapp.editor. The Myapp.editor works fine with the EEF code added as
> long as I run it as an Eclipse Application.
>
> Then I tried to rebuild my product. When I rebuild the product, I get
> this error (and boy is it a long one):
>
> C:\Users\hmiller\workspace_rcp2\.metadata\.plugins\org.eclip
> se.pde.core\temp\org.eclipse.pde.container.feature\assemble.
> org.eclipse.pde.container.feature.p2.xml:33: The following error
> occurred while executing this line:
> Target "gather.sources" does not exist in the project "Publish p2
> metadata".
> Is there something in the EEF code that breaks the product build?
>
> Since the code in the product used the Myapp.editor project, the
> Dependencies in the product are the same as the Myapp.editor. In other
> words, the EEF runtime, and the Myapp.edit projects are already
> dependencies. But the product still will not build.
>
> Should I delete the current product and try to build a new one? Maybe
> there were so many changes that the old product will not build?
>
> Thanks,
> Herb
>
>
>
>
--
Cheers,
Stéphane Bouchet, OBEO
|
|
| |
| Re: [EEF] Converting EEF to standalone [message #516759 is a reply to message #516654] |
Wed, 24 February 2010 20:04 |
Miles Parker
Messages: 1266
Registered: July 2009 |
Senior Member |
|
|
| Herb Miller wrote on Wed, 24 February 2010 11:56 | In the meantime, I will try to get smarter before I ask the next question.
|
I think you mean "more indoctrinated"  . We've all been on various branches of the Eclipse learning path so my advice is really meant to be helpful and not discouraging of questions -- personally I found that with Eclipse plumbing that my default style of "learning by doing" didn't work so well, and I did need to spend some time reading up in order to get up to speed on various things. Also, if you find yourself really puzzled by something general, the newcomer forum is really helpful even for those of us who aren't so new to Eclipse.
[Updated on: Wed, 24 February 2010 20:06] Report message to a moderator |
|
| | | |
| Re: [EEF] Converting EEF to standalone [message #517052 is a reply to message #517050] |
Thu, 25 February 2010 17:14 |
Miles Parker
Messages: 1266
Registered: July 2009 |
Senior Member |
|
|
See below. 
| Herb Miller wrote on Thu, 25 February 2010 16:58 | I don't get any errors when I generate the standalone app, and I don't get any errors when I run it.
I did a comparison of the dependencies between the plugin that is used to build the app and the app itself. I did find some discrepancies, but I don't know if they are significant or not.
The plugin seemed to have a few more dependencies than the standalone app, like:
com.instantiations.designer.jdt.fragment and a few other jdt related dependencies.
I wonder if this is something that should be posted on the RCP forum?
|
Yah, or perhaps PDE. My approach to this stuff is "if in doubt throw it in". One issue with the product definition is that I'm not sure that the add dependencies works in the same way. One thing to try is to create a runtime Eclipse application with your plugins, add dependencies, and then see if there are any descripencies. And actually -- yeah try this -- if you get the Runtime App working, you can create a product from that and then compare the two of those...
hope it helps,
Miles
|
|
| | | | | |
| Re: [EEF] Converting EEF to standalone [message #518072 is a reply to message #517681] |
Tue, 02 March 2010 17:29 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
It took a while, but I rebuilt everything in a clean workspace, and I still have the same problem.
I generated the model, edit and editor code. I added the EEF changes (initialize, generate, src-gen, dependencies, plug-in edit, code changes).
The editor ran perfectly when launched from the workbench as an Eclipse application. The window popped up. I loaded a model file. I expanded and selected a node and the EEF generated form opened up in the properties view with all GUI widgets visible and filled with data.
I created a product in the editor project, synchronized and launched it from the product overview tab as an Eclipse application - this also worked great.
Then I deployed the application. The deployment worked great. Then I ran the application as a standalone deployed product. The window popped up, I loaded a model file, I expanded the tree and selected a node and the EEF generated form opened up in the properties view but NO WIDGETS WERE VISIBLE.
The outline of the form, and the tab that says Base were visible, but no labels or text boxes, etc.
I was able to accidentally duplicate this behavior when running as an Eclipse application in the workbench. This same behavior occurred if I did not export the "providers" (note plural) package from the edit project. The "provider" class was already exported.
Any more ideas?
Thanks.
|
|
| | | | | | |
| Re: [EEF] Converting EEF to standalone [message #518370 is a reply to message #518342] |
Wed, 03 March 2010 17:12 |
Miles Parker
Messages: 1266
Registered: July 2009 |
Senior Member |
|
|
Herb, that's good news. Configuration hassles alas are par for the course. As I think I mentioned, there is a big mismatch between what you get from hosted runtime application and PDE build. I'm not surprised that there is a mismatch between the build path stuff and what is actually going on.
The best single advice I can give on that is to pretend the "Build Path" item and any of the rest of the standard project UI is just not there. You should always be referring to and editing the PDE / plugin build information, i.e. the editor that shows up when you open one of the project resources such as build.properties.
cheers,
Miles
| Herb Miller wrote on Wed, 03 March 2010 15:35 | I found the problem.
The build.properties file in the edit project had to be modified.
Old:
source.. = src/
New:
source.. = src/, \
src-gen
When I originally added the src-gen folder to the edit project, I selected the edit project and used the right-mouse button to select New->Source folder. One would think that this would have updated the src entry in the build.properties file.
I also used the right-mouse button on the src-gen folder and used Build Path-> Configure Build Path to bring up the "Java Build Path" view in order to check the src-gen folder. The src-gen folder showed up in the "Source" tab and the "Order and Export" tab.
For some reason, it was not in the build.properties file. As soon as I added the src-gen in the build.properties file, everything started working.
I checked the tutorial. It suggested using the Build Path->Use as a source folder option. I could not find that option.
Thanks Miles and Stephane for your help.
|
|
|
|
| Re: [EEF] Converting EEF to standalone [message #518601 is a reply to message #516083] |
Thu, 04 March 2010 10:30 |
Stephane Bouchet
Messages: 239
Registered: July 2009 |
Senior Member |
|
|
Hi Herb,
congrats to finally make it :)
Just 2 things :
first, i am using the forums the old-style-way, using it via nntp ( AKA
news.eclipse.org / newsgroup ) so i get all your messages.
Second, when you export product or plugin, PDE will base it's build on
the build.properties files to know which sources files to compile and
what to include in the jar. this is totally different from the runtime
process that is based on the .classpath file.
this is a common mistake made by all of us ( and me first :D )
anyway, i will update the tutorial with this tip.
Herb Miller a écrit :
> When I added the EEF tutorial to my project, my project already had a
> standalone product that worked. Now that I have the EEF stuff working,
> I re-synchronized my product and launched an Eclipse application from
> the Overview tab of the product page.
>
> My old product ran instead of the EEF changes. I assume there are some
> changes that need to be made to the product. Maybe the application
> needs to change.
>
> Does anyone know what changes I need to make to my product in order to
> get the EEF code to run in my product?
>
> Thanks.
>
>
--
Cheers,
Stéphane Bouchet, OBEO
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622201 is a reply to message #516223] |
Tue, 23 February 2010 13:13 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
Well, maybe I did not explain it too clearly.
I started with an EMF model named Myapp. I made the genmodel. Then I generated Myapp.edit, Myapp.editor and Myapp.tests (standard EMF stuff).
In the Myapp.editor I added a product based on the editor. I built the product and deployed it and it ran fine.
In this same workspace, I added the EEF code to the Myapp.edit project, and I continued until the EEF code worked all the way through the Myapp.editor. The Myapp.editor works fine with the EEF code added as long as I run it as an Eclipse Application.
Then I tried to rebuild my product. When I rebuild the product, I get this error (and boy is it a long one):
C:\Users\hmiller\workspace_rcp2\.metadata\.plugins\org.eclip se.pde.core\temp\org.eclipse.pde.container.feature\assemble. org.eclipse.pde.container.feature.p2.xml:33: The following error occurred while executing this line:
Target "gather.sources" does not exist in the project "Publish p2 metadata".
Is there something in the EEF code that breaks the product build?
Since the code in the product used the Myapp.editor project, the Dependencies in the product are the same as the Myapp.editor. In other words, the EEF runtime, and the Myapp.edit projects are already dependencies. But the product still will not build.
Should I delete the current product and try to build a new one? Maybe there were so many changes that the old product will not build?
Thanks,
Herb
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622216 is a reply to message #622201] |
Wed, 24 February 2010 10:14 |
Stephane Bouchet
Messages: 239
Registered: July 2009 |
Senior Member |
|
|
Herb,
As mikes says, i supect too there is somethnig missing on your product
configuration.
If EEF is working well in a runtime, it might work as well in RCP.
did you try to export the 3 projects alone and install them in a fresh
eclipse to simulates the product build ?
Herb Miller a écrit :
> Well, maybe I did not explain it too clearly.
>
> I started with an EMF model named Myapp. I made the genmodel. Then I
> generated Myapp.edit, Myapp.editor and Myapp.tests (standard EMF stuff).
>
> In the Myapp.editor I added a product based on the editor. I built the
> product and deployed it and it ran fine.
>
> In this same workspace, I added the EEF code to the Myapp.edit project,
> and I continued until the EEF code worked all the way through the
> Myapp.editor. The Myapp.editor works fine with the EEF code added as
> long as I run it as an Eclipse Application.
>
> Then I tried to rebuild my product. When I rebuild the product, I get
> this error (and boy is it a long one):
>
> C:\Users\hmiller\workspace_rcp2\.metadata\.plugins\org.eclip
> se.pde.core\temp\org.eclipse.pde.container.feature\assemble.
> org.eclipse.pde.container.feature.p2.xml:33: The following error
> occurred while executing this line:
> Target "gather.sources" does not exist in the project "Publish p2
> metadata".
> Is there something in the EEF code that breaks the product build?
>
> Since the code in the product used the Myapp.editor project, the
> Dependencies in the product are the same as the Myapp.editor. In other
> words, the EEF runtime, and the Myapp.edit projects are already
> dependencies. But the product still will not build.
>
> Should I delete the current product and try to build a new one? Maybe
> there were so many changes that the old product will not build?
>
> Thanks,
> Herb
>
>
>
>
--
Cheers,
Stéphane Bouchet, OBEO
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622257 is a reply to message #517681] |
Tue, 02 March 2010 17:29 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
It took a while, but I rebuilt everything in a clean workspace, and I still have the same problem.
I generated the model, edit and editor code. I added the EEF changes (initialize, generate, src-gen, dependencies, plug-in edit, code changes).
The editor ran perfectly when launched from the workbench as an Eclipse application. The window popped up. I loaded a model file. I expanded and selected a node and the EEF generated form opened up in the properties view with all GUI widgets visible and filled with data.
I created a product in the editor project, synchronized and launched it from the product overview tab as an Eclipse application - this also worked great.
Then I deployed the application. The deployment worked great. Then I ran the application as a standalone deployed product. The window popped up, I loaded a model file, I expanded the tree and selected a node and the EEF generated form opened up in the properties view but NO WIDGETS WERE VISIBLE.
The outline of the form, and the tab that says Base were visible, but no labels or text boxes, etc.
I was able to accidentally duplicate this behavior when running as an Eclipse application in the workbench. This same behavior occurred if I did not export the "providers" (note plural) package from the edit project. The "provider" class was already exported.
Any more ideas?
Thanks.
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622258 is a reply to message #622257] |
Tue, 02 March 2010 19:56 |
Miles Parker
Messages: 1266
Registered: July 2009 |
Senior Member |
|
|
Herb Miller wrote on Tue, 02 March 2010 17:29
> I
> I was able to accidentally duplicate this behavior when running as an Eclipse application in the workbench. This same behavior occurred if I did not export the "providers" (note plural) package from the edit project. The "provider" class was already exported.
Something odd is certainly going on here. But this is progress! My guess is that your extensions are not being registered or they aren't being picked up. Perhaps there is something going on on on the EFF side. In your RCP app, open the "Plugin Registry" view (you'd need include the relevant PDE stuff in your RCP build if it isn't already there). You should be able to see the EEF registered providers there. If not then that narrows it down.
I haven't actually tried to do an EEF standalone app yet, but I'll let you know if I run into any issues there. Curious if you've tried to run the tarot example projects..
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622259 is a reply to message #622258] |
Wed, 03 March 2010 04:22 |
Stephane Bouchet
Messages: 239
Registered: July 2009 |
Senior Member |
|
|
Hi guys,
i am curious too to know what's going on on this issue.
Miles Parker a écrit :
> Herb Miller wrote on Tue, 02 March 2010 17:29
>> I
>> I was able to accidentally duplicate this behavior when running as an
>> Eclipse application in the workbench. This same behavior occurred if
>> I did not export the "providers" (note plural) package from the edit
>> project. The "provider" class was already exported.
>
HUmmm, this may cause the problem. the "providers" package is used by
the EEF extension points to provide forms view, and is indeed necessary
to make EEF working :)
Try to export every packages in the .edit project and re-create your
application.
>
> Something odd is certainly going on here. But this is progress! My guess
> is that your extensions are not being registered or they aren't being
> picked up. Perhaps there is something going on on on the EFF side. In
> your RCP app, open the "Plugin Registry" view (you'd need include the
> relevant PDE stuff in your RCP build if it isn't already there). You
> should be able to see the EEF registered providers there. If not then
> that narrows it down.
>
> I haven't actually tried to do an EEF standalone app yet, but I'll let
> you know if I run into any issues there. Curious if you've tried to run
> the tarot example projects..
--
Cheers,
Stéphane Bouchet, OBEO
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622264 is a reply to message #518305] |
Wed, 03 March 2010 12:54 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
After my last post, I checked the standalone app that was deployed. It has a repository directory with plugin files and it has an application directory with plugin files. In both places the edit project jar file was delivered without the "providers" .class files. The "provider" .class files were there. I am in the process of hand building a jar file with both provider and providers. I will post again if this fixes the problem.
Thanks.
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622265 is a reply to message #518144] |
Wed, 03 March 2010 14:01 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
Stephane,
I finally discovered the tree view in the forum. For some reason, I could not see your last post until I went to the tree view.
As you can see, I am pursuing the "providers" problem. I will try what you said to see if I can get the "providers" to export from the edit project. I will let you know how it goes.
Thanks.
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622266 is a reply to message #622264] |
Wed, 03 March 2010 15:35 |
Herb Miller
Messages: 139
Registered: January 2010 |
Senior Member |
|
|
I found the problem.
The build.properties file in the edit project had to be modified.
Old:
source.. = src/
New:
source.. = src/, \
src-gen
When I originally added the src-gen folder to the edit project, I selected the edit project and used the right-mouse button to select New->Source folder. One would think that this would have updated the src entry in the build.properties file.
I also used the right-mouse button on the src-gen folder and used Build Path-> Configure Build Path to bring up the "Java Build Path" view in order to check the src-gen folder. The src-gen folder showed up in the "Source" tab and the "Order and Export" tab.
For some reason, it was not in the build.properties file. As soon as I added the src-gen in the build.properties file, everything started working.
I checked the tutorial. It suggested using the Build Path->Use as a source folder option. I could not find that option.
Thanks Miles and Stephane for your help.
|
|
|
| Re: [EEF] Converting EEF to standalone [message #622267 is a reply to message #622266] |
Wed, 03 March 2010 17:12 |
Miles Parker
Messages: 1266
Registered: July 2009 |
Senior Member |
|
|
Herb, that's good news. Configuration hassles alas are par for the course. As I think I mentioned, there is a big mismatch between what you get from hosted runtime application and PDE build. I'm not surprised that there is a mismatch between the build path stuff and what is actually going on.
The best single advice I can give on that is to pretend the "Build Path" item and any of the rest of the standard project UI is just not there. You should always be referring to and editing the PDE / plugin build information, i.e. the editor that shows up when you open one of the project resources such as build.properties.
cheers,
Miles
Herb Miller wrote on Wed, 03 March 2010 15:35
> I found the problem.
>
> The build.properties file in the edit project had to be modified.
>
> Old:
> source.. = src/
>
> New:
> source.. = src/, \
> src-gen
>
> When I originally added the src-gen folder to the edit project, I selected the edit project and used the right-mouse button to select New->Source folder. One would think that this would have updated the src entry in the build.properties file.
>
> I also used the right-mouse button on the src-gen folder and used Build Path-> Configure Build Path to bring up the "Java Build Path" view in order to check the src-gen folder. The src-gen folder showed up in the "Source" tab and the "Order and Export" tab.
>
> For some reason, it was not in the build.properties file. As soon as I added the src-gen in the build.properties file, everything started working.
>
> I checked the tutorial. It suggested using the Build Path->Use as a source folder option. I could not find that option.
>
> Thanks Miles and Stephane for your help.
|
|
|
Goto Forum:
Current Time: Wed May 22 23:49:29 EDT 2013
Powered by FUDForum. Page generated in 0.03376 seconds
|
] 
Search
Help
Register
Login
Home
