CN1 projects have an additional Builder "jar_project" configured.
Apparently this builder is looping when "Refresh using native hooks or polling" is checked in Eclipse Preferences -> General -> Workspace. "Refresh using native hooks or polling" is a nice feature to refresh the workspace files for changes made outside the IDE.
When editing the builder configuration via right click on a project -> properties -> builders -> jar_project and chiising edit I see that in the refresh tab the option "The project containing the selected resource" is selected. That is probably incorrect.
Anyway what is the builders "jar_project" purpose? Does it really need to be called after change of any project file?
The project is built using the build.xml file. It verifies that compilation works.
We don't support that eclipse mode and don't test against it. If you want to make changes manually they might work but we can't warrant them.
Related
We have 4 containers in an array, we show the first perfectly, but when we set as current the next container to show it, we call forceRevalidate() on it but only the most general container is showed.
When i update the project libraries through Codename One Settings -> Basic -> Update Project Libs and clean&build project the error persist.
#Versions.properties
It hasn't changed locally for a while since we didn't push an update for Ant in ages. I suggest migrating to maven where you can check such functionality.
Notice that if this applies only to device builds those do get updated for Ant and will be consistent with the latest maven version.
I have a VScode extension which is created by my team, which also has UI to enter arguments once function has written in the extension and I need to automate the functional test for that. I need to know which tool, package I can use to automate the same.
Steps to automate:
Open extension in vscode
Create project using that extension
Click on details icon of project
Verify the Details page (UI) opened for the that project
Enter arguments on the details page
Click on execute button on that UI
Verify message
Note: When we click on details icon of a project, it opens UI for the project created using extension in VScode itself
Already checked below link but had issues installing this
https://developers.redhat.com/blog/2019/11/18/new-tools-for-automating-end-to-end-tests-for-vs-code-extensions/
I'm able to automate VS code extension using playwright and gitpod OpenVSCode server to automate. refer: https://medium.com/modern-mainframe/test-automation-with-playwright-for-vs-code-extensions-facilitating-the-growing-interest-in-dcc463f81efa.
https://github.com/gitpod-io/openvscode-server
I am trying to get my react extension working for local development, but "Components" and "Profiler" is missing in the Chrome developer tools. This only happens for local development, any other production code is displaying the two tabs in the developer tools as expected. I was wondering if this can be resolved somehow? I triple checked if the tabs are hidden on that occasion, and they are not. As said, this only happens for development version. When I click on the extension, I get the following message:
This page is using the development build of React. 🚧
Note that the development build is not suitable for production.
Make sure to use the production build before deployment.
Open the developer tools, and "Components" and "Profiler" tabs will appear to the right.
Based on this information I should have the tabs displayed.
When I go to a production app and click on the React extension, I can see the following displayed:
This page is using the production build of React. ✅
Open the developer tools, and "Components" and "Profiler" tabs will appear to the right.
And I also see those two tabs without a problem.
Any idea why this would happen? I searched for a solution, but did not encounter one. The only thing I found was someone mentioning you need to set the environment variable REACT_APP_ENV. I tried to set this value in the .env file where I defined REACT_APP_ENV='dev' as well as REACT_APP_ENV='development'. It did not resolve the issue, even with application and browser restart.
This happened to me as well. Looks like a bug in Chromium, but a temp solution is:
Change the chrome DevTools theme, only once it is required.
Now open devtools, you find the extension tab in DevTools.
You can again change the theme whatever you want to keep and this will fix your problem.
Check this out:
https://github.com/facebook/react/issues/19002#issuecomment-637462179
Was having the same issue, the Components and Profiler tabs weren't showing up, so I tried changing the theme as suggested by BobTheBuilder, that didn't work, so tried setting the debug levels to Default + Verbose (in addition to the others) in the console and they finally showed up.
The steps that helped me:
Remove React Developer Tools extension
Install React Developer Tools extension
Open a brand new tab containing react app
Open Dev Tools
React Developer Tools should be available
I had the same issue where Components and Profiler tabs were not showing. What worked for me was to open up the DevTools settings and to click the 'Restore defaults and reload' button (under the 'Sync' heading).
The steps that worked for me
Open chrome extensions
Disable the react dev tools extension
Enable the react dev tools extension
Enable Developer mode
Refresh target page
Where steps 1 and 2 are the little slide control at the bottom right of the extension in the extension manager.
Step 4 is the slider in the top right above all the extensions in the manager.
I recently started to learn about AngularJS and came across WebStorm and the AngularJS plugin by John Lindquist. Started by creating a new project using the angular-seed project and imported to WebStorm using File -> Open Directory. My directory structure looks like this
Now when I try to Debug it I get a 404 error. If I move the file app/index.html to the root folder and adjust all URL's to begin with app then it works fine. Is there a way to keep the default folder structure without moving the index.html to the root folder and also make it work with WebStorm?
I am using WebStorm 6.0.2.
I use WebStorm 7, so there might be some discrepancy in comparison with version 6 that you're using, but the over-all functionality is the same.
Quick solution:
Open the file in the editor and right click in the code to access the context menu. Choose the "Debug" option, which should start a debug session pointing to the current page.
Configuration solution:
WebStorm supports configurations for setting up different debugging scenarios. From the "Run" menu, choose the "Configurations" option. Add a JavaScript debug configuration, and add the URL you want in the designated field within the dialog presented.
Then, when you initialize a debugging session (a general one, not one for a specific page), you're presented a small dialog that allows you to choose a debug configuration.
Maybe there are more options or ways to accomplish the same thing as well, but I've never really given it more thought. I hope this is a working solution for you, but if not there's alway the documentation. If you need further clarification with regard to my answer, just give me a comment.
I'm using Groovy and Google App Engine. I'm trying out Intellij, but I can't figure out how to get hotswap to work for changes to Groovy classes. It works for me in Eclipse. Is there something special I have to do for it to work in Intellij?
In settings (CTRL + ALT + S).
Navigate to Build, Execution, Deployment -> Debugger -> HotSwap.
In here make sure that Enable hot-swap agent for Groovy code and Reload classes in background are checked and that either Always or Ask are selected for Reload classes after compilation.
You need to run your app in debug mode and you need to make (CTRL + F9, or Build -> Make Project) after you've done any changes.
You should see a green text bubble pop up if your classes were reloaded and a red one if they couldn't be reloaded for some reason.
To configure reloading behavior:
On the main menu, choose File | Settings , and then expand the
Debugger node.
Open HotSwap page.
Click one of the radio buttons in the group Reload classes after compilation. You can opt to always reload classes, reload after
confirmation, or never do it.
Also check the Enable hot-swap agent for Groovy code option in
File -> Settings -> Debugger -> Groovy.