I have an existing Eclipse project with Java 8 and Maven. Now I want to create a window with Oracle's Scene Builder. How can I do that?
All the tutorials start with "Create a new JavaFX project". This doesn't help me. I want to work with my existing project.
You should be able to just create a basic fxml file in your project hierarchy. Then right-click on it and choose "Open with SceneBuilder".
To create the file, if you have e(fx)clipse installed, you can do File -> New -> Other. Then under "JavaFX" choose "FXML document". Put in the name (without the .fxml extension), and choose your root element. Then once the file is created, close it, right-click on it in the package explorer, and open with SceneBuilder.
If you don't have e(fx)clipse, I think you can still do this; just create a blank file (File -> New -> File) and name it with the fxml extension. Then, again, right-click and choose "Open with SceneBuilder". (The only thing I am not sure about is whether this option is available without e(fx)clipse.)
Related
I have installed the ResourceBundle Editor plugin (http://essiembre.github.io/eclipse-rbe/) the usual way. In the plugins folder there's the JAR com.essiembre.eclipse.rbe_1.0.6.jar, in the features folder there's the sub folder com.essiembre.eclipse.rbe_1.0.6 with only the feature.xml in it.
The problem is:
I neither get the RIGHT-CLICK on properties file -> Open with... -> ResourceBundle Editor entry nor do I get any preferences as depicted on http://essiembre.github.io/eclipse-rbe/ ...
The above menu entry is missing entirely, even though Help -> Install new software... repeatedly tells me the plugin was/is installed.
Any ideas what's going on and how to fix this?
PS: I think programming tools questions belong here... (?)
Try creating a new file association with the ResourceBundle Editor
Go to Preferences > General > Content Types.
Add a content type: click "Add Root..." and choose a name you want, e.g. "Properties files"
Add a file association: click "Add..." and type "*.properties" (without quotes).
Add an associated editor: click "Add..." and choose "ResourceBundle Editor"
Apply and close.
I have recently updated to Eclipse 4.3 (SR1, WTP). And I have an issue: when I want to create something: a file, a class, a dir, etc:
I right click on a dir (or package); e.g. "myDir", or "myPackage"
the wizard appears, but it doesn't propose "myDir" or "myPackage" as parent element. I need to manually specify it
Do you have any idea what may cause this strange behaviour?
For Java Eclipse will only use the folder / package if the folder you right click on in is a source folder (usually the src folder). Source folders are defined in the project preferences in the Java Build Path Source tab.
Current setup:
MainProject which is a Library Project
BranchProject which is a new projects and has MainProject as a Reference
Whenever I debug and a file from MainProject is on focus (actually BranchProject has only graphic and xml layout changes) the Debug window opens a .class file which is read only. I want it to open the .java file so I can edit it directly.
Skyler's answer from this post worked for me:
Opening source code from debug view edits .class after Android R18 update
Here is a summary:
The fix is to right click the Project name in the debug view, and select "Edit Source Lookup..." from the menu. From there, remove the Default lookup path. After that, manually add the associated projects (not jars) that your project references. This is done by clicking Add, selecting Java Project, then checking the appropriate projects.
When you're using a Library project one of the things you're in fact doing is compiling your Library project into a jar and then referencing that jar in your calling Project.
If you right click the Project, and select "Configure Build Path" you'll see a tab called "Libraries", if you look inside "Android Dependencies" you'll notice a list of jar's corresponding to your Library projects.
These jars are expandable, showing you that they have a slot for a source attachment. Usually this would be editable allowing you to directly link the source but in terms of ADT these are already filled and are uneditable.
When debugging these files you're linked to a read-only class file with this attached source. This is because you're not running against source files directly, you're running against a pre-compiled class file. Until the ADT team get this functionality in place, you're pretty much forced to jump to the direct source code and rebuild everything.
EDIT
See #Steven linked answer :)
I faced the same issue while debugging the a .java file using Eclipse IDE. As per my understanding this issue comes when we put the xyz.class file of xyz.java file or JAR at the project build path. Delete the .class or JAR file from the project class path and rerun .java file in the debug mode. This time you see a source not found window. Click on "Source not found" button and check "Find duplicates..." at the bottom of the window. Done your problem is solved :)
The problem is that the class file is preferred over the java (by default), here is how you can change that for Eclipse (tested on NEON 2):
Right-click on the Project in the Project-Explorer, click Properties
On the new window select: Run/Debug Settings
Create a new configuration (or duplicate another one)
Select the new config and click Edit...
Go to the tab Source
Select the Default and Remove
Create a new path with Add..., select Java Library, then JRE System Library
Create a new path with Add..., select the location where the sourcecode is by Workspace folder (if it is a project in the same workspace) or File System directory (it it is not)
I think this depends on, how you set up the dependency in eclipse. You should set up your BranchProject to depend on the source-Files of your MainProject. If you depend on compiles Class-Files is obvious that the debugger opens the class files, because it does not know about the source files.
I found a good solution for me here:
Using Android library in eclipse and jumping to class files instead of source file that is within eclipse workspace
Simply, select each library project your project depends on, and use Top or Up to move it above the projects outputs. Eg. move all library projects to the top.
Open main project properties -> Java Build Path -> Projects tab and add there projects the main project depend on.
Switch to Order and Export tab and uncheck Android Dependencies
Enjoy
If you tried all above hints and it still doesn't work try this solution, it worked form me:
Right-click on the Project in the Package-Explorer, click Build Path -> Configure Build Path...
Select tab Order and Export
select library that you can't reach code and then click on button Bottom
Then click on Apply and Close
hope this can help you
Most of the time it happens when specific source folder are not added in build path Sources tab.
Right-click on the Project in the Package-Explorer, click Build Path -> Configure Build Path -> Source Tab
Add the source folder if your project source folder is not there.
Select Add folder -> select your project source folder specifically. Eg: project_name/src . Then Apply it and restart server.
In Eclipse, I have one existing project, A. Right now, I have just created another project, B, which is empty. Is it possible to copy all the files of project A, including its source code and related libraries to project B? There are a lot of involved libraries in project A. How to do this copying process correctly to ensure the copied files can still be compiled?
This question appears in Google search as top result for query "copy project in eclipse".
To copy project in Eclipse:
1) right click on project in Package Explorer view;
2) choose Copy;
3) right click on free place in Package Explorer view;
4) choose Paste;
5) enter new name in the prompt window.
To answer actual question, the best way is to delete project B and after -- copy project A as explained above and give it name B.
Close Eclipse
Copy the folder of existing project to anywhere on your disk.
Start Eclipse. Turn off the automatically build.
In the Eclipse do Refactor / Rename to the new project name. (If it connected to CVS/SVN disconnect before rename.)
Import back the old project from place where you copied in the second step.
Turn on the automatically build.
Enjoy them!
You can Import the project
OR
Assuming both project A and B are of same type:
You can copy the contents of src folder as it is.
For the libraries, just go to the build path and add them in the ssame way you did for project A.
Since B is empty, you can just copy project A in the Package Explorer and name the copy B.
Create a duplicate/copy of an existing project (in the workspace).
Then in Eclipse, click file->import
Select import existing projects into workspace
Check the radio button "Select root directory"
Browse your project (the new file you copied in workspace in step 1)
Done!
In the project Explorer, right click your old project, click "Copy", right click again click on "Paste" this time, change the default given name "Copy of My_Old_Project" to any of your choice, after the copy is done, go to the "Search" tab in Eclipse, then to --> "Search", on the File Search, type the old name of your project, make sure that your scope is only "Enclosing project", change all occurrences into the new name, run the project, you are all set...
only thing I noticed about this is that the url will still be of the old project.
For a Gradle project, I had to add two extra steps to mOna's answer, which I will copy for completeness.
Create a duplicate/copy of an existing project (in the workspace).
Then in Eclipse, click file->import
Select import existing projects into workspace
Check the radio button "Select root directory"
Browse your project (the new file you copied in workspace in step 1)
Edit .project file and change the and the to match the new project.
Edit settings.gradle and change rootProject.name to match the new project.
I assume that the renaming in some of the above answers does step 6, but I couldn't get it to work. No matter what I tried, without those extra steps the code looked ok but dependencies were not handled correctly and errors appeared everywhere. I was even able to run gradle on my project from the command line and it "built", but was actually building the old project.
Eclipse has a option in file menu like import existing projec.From that you can import the existing project with all content.I hope this is the solution that you are looking for.
I want to create a project that uses source files already on my filesystem, but the IDE always wants to create a directory and make a second copy of all the source.
This has always annoyed me about Aptana and Eclipse, is there a workaround for this?
I am using Aptana Studio 3 on my mac and the way I do it is:
Click on File
Select Import from the dropdown menu
Select the General tab and open it, you will see the option Existing Folder as New Project
Select it and click on Next
On the next page select the folder where you have the old project files, name the new project(if you want to change it). You can also select the languages that you have used on the project.
Click Finish and you are set to go.
One small addendum, the existing folder doesn't actually need to be in your workspace. I have several projects in my workspace but also several located elsewhere for assorted reasons.
have the files in a directory under your workspace
use "create project" and change the default folder to the one created above.
I too wasn't aware of how to do this..
But i tried this way and it worked..
Step 1: Try to create new workspace with the name and location as you wish
Step 2: click new->Java Project
Step3: In the create a Java Project Window select the option for Creating from existing Resource" and select the resource you want
Step4: You can see the project name as automatically set by itself based on the folder containing the project that you select.
Step5: click finish
Step 6: I guess, you need to open Navigator view(Window->show view-> navigator) for best viewing
Hope this works gud.. Post here if its not working,..
There is a checkbox named "Prompt for workspace on startup". It's in Window -> Preferences -> General -> Startup and Shutdown -> Workspaces. If you check this, on next Aptana startup you will be prompted to define a new Default workspace directory which would be your default projects folder.
There is also another way to do that.
Create an empty project (right-click in the Project Window and go to "New->Project" and then "General->Project" and click "Next", after that type in a project name and click "Finish").
Add a new connection to this project (right-click on "Connections" and then "Add New Connection"). The "Source" should be your project and the "Destination" should be the type "Filesystem" with a folder of your choice.
Finished.
I only use that method in very rare cases, as example, if u need a simple file-reference of any folder on your harddrive or if you need an overall file-reference to your workspace folder which contains all project folders, etc..
This answer by no means solves the issue above in Aptana but if you are in a rush, try using FreeCommander http://www.freecommander.com. It is a dual pane file manager with a slew of options. I have been using it for almost 3 years and there is never a day I don't use it.
What I did for now, is I allowed Aptana to create a folder in the workspace at the same level as the original folder I would like to use. Using FreeCommander I then have the original (src) folder in one pane with the new folder (dst) in the other pane.
I then manually copy (F5) or use FreeCommander's built in sync function (Alt + s) so that both folders have the same contents at all times.
Again, not the right answer but a workaround as work needs to be done. Cheers.