Download Netbeans 16
Fonda Stacer
NetBeans seems to really like working with projects, but I don't want a stinkin' project, I just want to work with the files I've already got. I want to see all the files I've got in a directory in the sidebar. A tree view.
I should also note that these are SVN checked out files. I'll need to commit them back. I know NetBeans has SVN support, but will it recognize the file is versioned if I open it directly? Doesn't seem to acknowledge that.
There's a Window called "Favorites" that you can open from the Window menu. Inside that Window you have a context actions that lets you add any directory in your filesystem. It will then be displayed in a treeview. you will also have context menu Actions, like you have them in the Files view for "real" projects. Also there's a plugin called "Automatic Projects" that will open ANT based projects without screwing them up, importing, etc.
As near as I can tell (I've only been using netbeans for about a month), projects are not much more than links to directories - once I "import" an existing project/directory I can browse freely from the imported directory root.
Im trying to configure xdebug to work with Netbeans 6.9 and php 5.3
As far as i concern i have setup xdebug properly.
I can see xdebug extension from phpinfo page.
I have read other post and tried their suggestion but up to no avail
First, check that it isn't actually working for you, and you don't notice. I've done this...convinced it's not working I wasted a chunk of time trying to get it to work, only to find that everything was OK.
Look at your NetBeans status bar. If you see "netbeans-xdebug" and "running" then it is actually working just fine. You probably have the "Stop at first line" option turned off and you didn't hit any breakpoints you set (if any) yet. That would be a reason you are seeing the page with little or no indication that the debugger is actually connected.
If you instead see "Waiting for Connection (netbeans-xdebug)" and the progress bar is cycling, then you are indeed not connected. Open ToolsOptions, and go to the PHP page. On the general tab, make sure that the "Debugger port" is 9000 and the "Session ID" is "netbeans-xdebug". You may want to have "Stop at First Line" checked. I don't, as I find it a bit annoying. I would definitely ensure that "Watches and Balloon Evaluation" is not checked. This option causes NetBeans and the debugger to destabilize. If you need a watch, hack a local variable into the PHP code where you need it, and you'll see it on the "Variables" tab when the debugger is running. Also, confirm that file (index.php) is specified in the project's Run Configuration > Index File.
Since you see xdebug in phpinfo(), that end of it is fine. Just make sure that all of the values look reasonable, and that there is some reference to a cookie "XDEBUG_SESSION=netbeans-xdebug" somewhere on that page. (Make sure that you don't have cookies turned off on the browser!)
The only other thing to check is to see if some firewall/security program is running that would be blocking TCP/UDP locally (which would be super-odd, but not out of the realm of possibility), or that port 9000 isn't already used by another application. I am using a different port number in my local setup for some reason. I don't remember changing it, but I am sure that the only reason I would have is if I had hit a port conflict with something else.
One last thing... We've been assuming that you are running NetBeans and the web server on the same computer. That's a common configuration, but not the only one. If your web server is on a different computer, then change the localhost in xdebug.remote_host=localhost to the IP address of the computer on which NetBeans is running.
Another last thing: When cycling through frustrating iterations, until you see xdebug info in phpinfo(), restart apache/php. Once there, still restart NetBeans between iterations. And believe it or not, restart your browser.
I couldn't figure out why some of my projects would connect to the debugger and others wouldn't. Then I realized that the ones that wouldn't connect started with index.html. Once I renamed these files to index.php, the debugger connected with no problem.
When I tried to debug the Yeoman WebApps powered by PHP backend in Netbeans, the status keep showing 'Waiting for connection'. There's probably because the index.html has nothing to do with php at all. It's only when I've triggered the ajax which needed PHP processing, the connection with xdebug immediately connected and debug as usual. Hope this give another perspective to someone as I have stumbled to 'think' there is a problem and trying to fix the ini.
We have been using the bucket for years. The access changes in 2023 have dropped a nuke on productivity by cutting us off from our repo code. The latest change was to add "Repository Access Tokens" -- easy to create, but not easy to use. I have tried every combination of username/password possible to create the url to the .git file, without success. I have tried Git for Windows, and GCM, both created new rabbit holes to drop into. I just want to be able to push/pull from our shared repositories on bitbucket. Can someone please help?
did not know windows had a credentials manager. found it. does not contain any references to bitbucket. could have been referring to GIT credentials manager, but I don't know. I don't have git installed on my computer -- did not need it.
SSH seems impossibly complex -- six different applications to install, 2 or 3 different powershell versions, none of the powershell commands run without errors, -- in short, another weeks-long nightmare.
Two different issues, two different threads. I know of no limitations on the number of simultaneous issues that can be open. So, far neither issue has been completely resolved, and the two will soon merge into the same SSH issue. An active link would seem appropriate.
I believe what you're looking for is either in the section Repository Access Tokens through the interactive password prompt or in the section Include the Repository Access Token in the URL.
I finally got it to connect. The new repository access codes did not work. Period. One of the old shorter access codes did. I have no idea why. I thought those were supposed to be old and deleted. There was considerable confusion over what username to use in the url given to netbeans. Could be: 1) x-token-auth, 2) the bitbucket account username, 3) maybe even the RAT name. Who knows? It does not say anything in the docs about it, except the explicit reference to x-token-auth, which did not work. For clarity, I am talking about :pass...@bitbucket.org/this/that/repo.git
This is the url that netbeans wants, or used to be before the RATS sank the ship. Drum roll.... the answer is #2, the bitbucket account username. Omit the password from the url, form your complete url, enter the short access code from olden times (last year) manually as the password, and viola, it works. At least for now. Maybe it will change again tomorrow. My client managed to get SSH to work and storing the key solved all his problems. I think he used a Linux machine, though. Cheater.
"NBGit is a module for the NetBeans IDE that adds support for working with the Git version control system. It uses the JGit library created as part of EGit to interact with Git repositories. Because the module is Java code all the way, it should work better cross-platform modulo platform specific differences, such as file system behavior. It is based on the NetBeans Mercurial module." ( )
As far as I can tell, there is no way to get NetBeans to work with CVS keys on Mac/Linux via the system SSH binary, so you will need to use the internal SSH and your password (which you can choose to save).
If you wish to work with a plugin, you will need to check this out separately and add it to the Moodle code project you have just made. This because for some reason, the 'Do you want to create a project' option fails to show any of the files once you open it if you try to check out the plugin on its own (NetBeans 6.7.1 on a Mac).
Note that the last three points may cause you some grief when attempting to commit changes. CVS doesn't seem to like having subfolders with different origins. A workaround that operates well for me is to check out the contrib code manually into a folder using the command line as specified in the CVS for developers instructions, then import that code as a new project with existing sources. This allows easy commits and updates, whilst keeping it separate. You can then make a symlink from you main Moodle project to your contrib directory, restart NetBeans (the CVS info and symlink stuff is only refreshed on restart) and then right click the linked directory and choose 'Ignore', then do the same and choose 'Exclude from commit'. You can now use the code as if it were part of Moodle, still getting all the code completion stuff, and also do clean updates and commits from the secondary project. Matt Gibson 19:53, 6 June 2010 (UTC)
Your plugin will likely start with just a HEAD tag and at some point, you will want to branch it so that you can have versions for different Moodles. To add a MOODLE_20_STABLE branch, for example, do the following.
There is a small chance that the Merge link will not be there, in which case, you will have to copy the files into the directory by hand outside netbeans and then check them in. If you do this, make sure you don't copy over the 'CVS' folders that will have been made when you checked out the MOODLE_19_STABLE code.
1. You may want to run NetBeans with the Sun JDK. NetBeans seems to work a bit better with the Sun JDK. You'll have to edit NetBeans config file. Open netbeans/etc/netbeans.conf. Then uncomment and edit:
You can install the optional JIRA module in order to be able to interact with the Moodle Tracker from within NetBeans. This has the advantage of avoiding constantly switching back and forth from the browser and works quite well. Go to Tools->plugins->available plugins and search for JIRA. Once installed, right click 'issue trackers' in the 'services' pane to make a new tracker instance, then enter your details.
c80f0f1006