1) created simple hello world eclipse app.
2) product configuration created.
3)In overview tab of product Configuration clicked on "Eclipse Product Export Wizard"
4)Destination chosen as Archive file and stored in local system.
5)extracted the zip folder and if i click on icon it is successfully showing the exported result.
6)But if I copy the zip folder in mac and if i extract and try to click on the .exe it is not showing the proper result instead it was showing Archive window.
I would like to know what steps should follow so that exported Eclipse RCP application(which built on windows) works in mac.
quicker response would help me to fix my issue.thanks in advance.
RCP builds are specific to a single operating system (Mac, Linux, Windows), GUI system (Cocoa, GTK, Windows) and architecture (64 bit, 32 bit). You will have to build separate Mac and Windows builds.
To build for multiple platforms you have to set up a target platform which includes the Mac specific code (and any other platforms you want). Using a target platform based on one of the Eclipse software sites will give you this.
Once you have done this the Export wizard will let you export for multiple platforms and lets you choose which platforms to export for.
I have done below steps to solve this issue
1)window+preference+TargetPlatform+select running platform +click on Edit.
2)then popup will open + click on add +click on istallation/software site+provide delta pack path.
3)so that when ever we trying to export RCP product from "Export product configuration" in product file we can observer the multiple platforms oprion in that dialog box.
Related
Some applications like PostMan, SpringToolSuite etc. which has to be downloaded in tar.gz, .zip files from official websites would give a hard time in setting up applets for quick access on the Linux Mint panel.
So after cracking my head for 3 to 4 hours. I was able to create applet for faster access using this method.
I have found this problem for most of the applications that I downloaded from tar.gz and zip file Linux Mint doesn't automatically create an applet that can be used for quick access.
But on the contrary, deb files that are executable on double-click can automatically create applet for quick access as it compiles with help of package installer.
So the solution that I followed is:
Extract the compressed package which generates a folder.
Right click and choose the option Create a new launcher here...
Select the name and select the main executable provided in the
generated folder.
This would create a rocket icon launcher(as of Linux Mint 17.1)
Right Click that icon and open in text-editor add this line
Icon=/icon-location..
Click on Menu type the rocket icon launcher Name that you given in
step 3
Right click on the result that has rocket icon launcher, add to
panel
That's it!!
I would like to use Eclipse in an intro programming class. Is there some way I can make some kind of preferences file or some such that I can distribute with it that would set defaults for:
which buttons are in the toolbar
which menus are enabled in the application
which context-menus are enabled
what kinds of completions are available
I'd like it to start with only completing words from the current document
that is no Java API completions or code generation or whatever
This can be done using Eclipse Preferences File. All you need to do is import preferences into your workspace.
You can also export the workspace folder itself & publish Eclipse together with a default workspace folder, which will contain all the preferences.
Then create a shortcut to start eclipse with -data <path to your workspace> parameter
I'd try the following:
Install Eclipse
Put the configuration files and workspace under version control and commit.
Configure Eclipse as required.
Check all the changes in the version control to understand what configuration files are relevant to my changes.
Continue as Zilvinas is suggesting.
Look into Eclipse Oomph. It essentially automates all the tasks that you need to do to set up a fresh dev environment.
Also of interest are Yatta profiles which do a similar thing based off Oomph.
They're pretty easy to set up and publish. Get your local eclipse working, record to a profile, publish the profile, get your students to consume said profile. We've used these in a professional environment to more easily on-board new devs!
I'm trying to get SceneBuilder to work with Eclipse v4.4.2 on Mac OS X. I'm following the advice from this tutorial: http://code.makery.ch/library/javafx-8-tutorial/part1/. I downloaded the Mac OS .dmg version of the SceneBuilder app from here: http://gluonhq.com/products/downloads/. It works when I run it as a stand alone.
When I try to configure Eclipse to use the app as part of the e(fx)eclipse package, Eclipse seems to be configured to look for the file Contents/MacOs/scenebuilder-launcher.sh in the application package contents. The version of the app I have doesn't have it, instead it just has the executable Contents/MacOs/SceneBuilder.
Failure to launch SceneBuilder [...] Cannot run program "/Applications/SceneBuilder.app/Contents/MacOs/scenebuilder-launcher.sh". No such file or directory.
Does anyone know which version of SceneBuilder I should be using (and where I can get it), or is there a hacky solution to sort this?
Just playing around with the SceneBuilder standalone it seems like it's a big step up from WindowBuilder, shame that just finding a packaged/compiled version of it has been so difficult!
The answer provided by ItachiUchiha is not the full solution with the new binaries provided by Gluon. Obviously they have forgotten to package the file Contents/MacOs/scenebuilder-launcher.sh with the new binaries. It is however sufficient to just copy over this file from an old version of SceneBuilder to make the launch from within Eclipse work.
Hi guys my solution is not clean by the way I use:
On OSX :
$cd /Applications/SceneBuilder.app/Contents/MacOS/
$ln -s SceneBuilder scenebuilder-launcher.sh
And for that works.
On a Mac:
I just installed sceneBuilder 8.3.
After setting up Eclipse with the proper SceneBuilder executable (in the Applications folder)
I had the same problem.
Failure to launch SceneBuilder [...] Cannot run program "/Applications/SceneBuilder.app/Contents/MacOs/scenebuilder-launcher.sh". No such file or directory.Error=2
Then in Eclipse I went to the
Help Menu, Check for Updates and Installed
all of the latest updates offered.
When I was asked if OK to Re-Start Eclipse I clicked OK.
After Eclipse restart
I Right Clicked on a Main.fxml and selected
Open with SceneBuilder.
It worked perfectly.
Best of Luck to you all
You can change the path in
Eclipse -> Preference -> JavaFX -> SceneBuilder Executable
I had this same issue on my mac following the code.makery tutorial but discovered you can still use the official JavaFX Scene Builder 2.0 download from oracle.com available at JavaFX Scene Builder 2.0.
After downloading and installing (by double-clicking on the downloaded .dmg file and dragging to the application folder), simply navigate to Eclipse>preferences>JavaFX and then browse to your Applications folder and select the JavaFX Scene Builder app you just installed. Worked and is still working for me!
I downloaded the older version of scene builder from oracle site. Copied the scenebuilder-launcher.sh from the fresh installation directory to the Glueon scenebuilder directory. And this fixed the issue.
My solution on Mac OSX was gleaned from the bug report at https://github.com/gluonhq/scenebuilder/issues/2. Apparently newer versions of Scene Builder (not including version 2 and before) are missing the scenebuilder-launcher.sh file. To make this all work, do the following.
Install a new version of Scene Builder from Gluon (not Oracle). I used https://gluonhq.com/products/scene-builder/. Install AND OPEN Scene Builder. For this to work, it is important to actually open Scene Builder before attempting to use it in Eclipse. If you don't, the first invocation under Eclipse will attempt to pop up a the normal OSX security message which, of course, it can't do because it is being invoked from a shell script. This only happens on first invocation, so the next time you won't have the problem. You get a message to the effect that the application is damaged. You will also get this message if you install a new version. Just invoke the Scene Builder application standalone before continuing to use it with Eclipse.
open a terminal session (sorry I don't know of another way to do this otherwise as you need to make the file you create executable)
cd /Applications/SceneBuilder.app/Contents/MacOS
sudo vi scenebuilder.sh (or use your favorite editor other than vi)
cut-and-paste the file from the Gluon issue into your editor and save it.
sudo chmod +x scenebuilder.sh
open Eclipse and open Preferences > General > Editors > File Associations (or type file in the filter box and select File Associations.
scroll down to .fxml in the file type box and select it. If you don't see it, click add to the right of the file types list. Enter .fxml and click OK.
in the associations pane, click Add to the right of the associations pane and click the Internal radio button. Scroll down to Scene Builder and select it. Click OK, the Apply and Close.
You should now be able to right-click on an .fxml file and click Open with Scene Builder and Scene Builder should start with the fxml file open in the builder.
I installed Eclipse Luna in XP yesterday and opened the sample project "Mutlipage Editor". When I click "Run" all that happens is another copy of Eclipse opens looking like the first copy but all the workspace boxes are empty.
I guess I was expecting either an emulator to start or the ability to run it on my Android phone. Can anyone get me started please?
When you run an Eclipse plugin it has to run in an instance of Eclipse so that all the other plugins that the plugin depends on are available.
The default 'Multipage Editor' is associated with a file type (.mpe I think). So create a file with that type and open it to see the editor.
You can also write an Eclipse Rich Client Program (RCP) where you can select the available plugins and the look of the UI, but this requires additional code.
I am working on using Eclipse as a basic file editor, without all the heap issues that comes with a Java tools install. I downloaded the platform version with no plugins, and added some editing tools for the code I wish to develop.
I do not intend to create new projects in this Eclipse, but would rather just edit individual files. Ideally, I can just open these from a File Explorer view within Eclipse (see image). Is there a plugin that I can download that will allow me to do this, or is there a simple hack to get this feature added?
I found a solution. It unfortunately adds nearly 30MB, and I was really hoping for a lighter weight solution (I will not choose this as the answer yet, in the event one is posted). The Target Management plugin provides a plugin (add this url to Eclipse's Install New Software... dialog: http://download.eclipse.org/tm/updates/3.4/ ) that allows the browsing of remote and local file systems. Opening the view Remote Systems will allow you to open the local file system and open files from within, that appear in the main editor window.