I'm trying to test my plug-in, but it always comes up with only 40MB and I keep getting out of memory error. If I change the setting, it doesn't take it. It creates a brand new one with default value as shown below.
I think what you are asking is that you want some default arguments to be populated automatically for each new PDE launch configuration.
You can do this:
Go to preferences -> Plug in development -> Target platform
Select the target platform you are using and click edit
Click on the arguments tab
Add your program and vm arguments and these will be applied to all new launch configurations for that target platform
Here's a screenshot of the preferences page:
Related
I'm just trying to implement react-native code push on my react-native application but I just can't find Build Location -> Per-configuration Build Products Path on Xcode 10.
Here's the guide I'm following: https://learn.microsoft.com/en-us/appcenter/distribution/codepush/react-native#multi-deployment-testing
Where did that change go to?
Xcode 11 has removed this setting moving to the new build settings found in the Workspace Settings.
For CodePush, you want to create another user-defined section named CONFIGURATION_BUILD_DIR, using the same per-configuration settings.
NOTE: I found that Xcode would crash anytime I set the section name to CONFIGURATION_BUILD_DIR after creating it (most likely due to the empty values). To avoid this issue, create the section without renaming, set the configuration specific build folders, and then change the name.
Best of luck!
Press Cmd+1 to open Project Navigator
Click on Project you need to edit
In the pane that opens click on target
Click on Build Settings tab
Select "All" in the filters
Select "Levels" in the filters
Search for "Build Location" in search.
Xcode 11, you can find this option at PODS_CONFIGURATION_BUILD_DIR
I have recently finished building a mini-app using IntelliJ IDEA in javaFx. It is my first time using this ide and language, so I am having difficulties manufacturing an exe file. I watched all sorts of youtube videos and different methods.
It does generate an exe file but when I click it, nothing happens.
Any idea?
I do know that with IntelliJ Ultimate edition you can build down with an EXE file.
There are a couple things you need to double check.
First, is that in your project structure under artifacts, you have the "Type:" set to JavaFx Application(which is on the top right of the window).
Secondly, switch to the Java FX tab and make sure Application class is set to your main class.
Thirdly, Select "all" under Native bundle: which is located towards the bottom of the window.
Lastly, Select the Output Layout tab and move all your available elements to output root then click on the module of your application and look at the settings that appear at the bottom. "Make sure that main class setting is in fact the main class to your application.
Side note: make sure you delete your artifacts build folder just to start from a clean slate. Also make sure your Environment variables are set to the system path correctly.
For any change I made to my class, which contains a main() method, I have to run "Build->rebuild project", to make the changes effective. I am afraid my environment or settings have a problem.
Please help.
Please check that you still have Build step in the Before launch setting of the Run/Debug configuration. This is the default, but you could have removed it by accidentally clicking on the — icon.
I think you'll have to repeat this for every JUnit test case.
To alter the behaviour for all test cases:
Run -> Edit Configurations...
In left-hand column, select Templates -> JUnit
Make your changes
Hit OK
I had the same problem and I solved it setting the SDK. You need to go in Project Setting and select the Project tab, as show below
Then you can download a JDK or add a new SDK. Finally, you click on OK and run the code.
I'm using Xcode 8 to automate my application.
I get started by downloading an existing code: XCUIToDo project. I opened the project in Xcode, and when I click on the Record button, I'm seeing a warning message "Please select a scheme where "XCUITodo" is the executable" and the record feature does not start.
Please let me know where I'm missing.
TIA
Ensure that an executable is selected for your UITest scheme.
Select Product > Scheme > Manage Schemes
Select your UITest scheme in the list
Select Edit
Select the Info tab under Run
Ensure that the required Executable is selected
The problem is not on the UITest schema or target. When starting to record, the main schema (the one which runs the application) needs to be selected regardless if you have your UI tests on a different schema.
Click on Project Root, then Targets -> XCUIToDoUITests target. From the General tab, check the "Target Application" setting under Testing section. The value in the dropdown should match the XCUIToDo target.
For me after making sure everything mentioned above is selected properly, I had to choose same scheme (as selected under info in edit scheme) next to device selection on the top.
Every time I open a new project in IntelliJ IDEA, the first time I open a particular tool window, for example 'Maven Projects', it appears in 'pinned' mode and remains visible until either I close it, or I go to the view settings for the window (the little cog) and deselect "Pinned Mode". I don't want any of my tool windows to be pinned so this gets a little annoying.
Do you know of a way to change the default behaviour of new project / tool windows?
As far as IJ 2016.2 I don't know about a dedicated setting for this. However I used an approach which allows you to define a default layout for all projects. Although the window-pinning works, which is what this question is about, some may not be persisted, such as Group Modules setting in the maven tool-window.
Nonetheless, to configure the pinning, you need to do 2 simple things, which you can also see in the GIF below:
1) Manually go and unpin all desired windows
2) Open the Windows menu and select Store current layout as default
P.S. If you'll be using tool-windows that you've never opened before, or install new plugins which add their own tool-windows, just follow these steps again.