Netbeans 7.4

[Yaima President]

NetBeansseems 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.

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.

While working with the netbeans integrated with visual paradigm for creating a model diagram where I misclicked and closed the diagram navigator and model tabs and they are not coming back again and also I hard tried to see them in view tan but not showing how to retrieve them again

To add a dark look and feel to the GUI but also to the colorschemes used in the code, you can install one of the following certified extensions from the plugin directory which can be reached from Tools > Plugins > Available Plugins:

If your system has a small tmpfs partition, you will have problems unpacking the maven index (will continue downloading again after failing to unpack). To fix this issue, append the following pieces of information in the Netbeans configuration file accordingly:

Just comment out this line; netbeans will find the proper path on startup. Since netbeans.conf might be overwritten during an update, this procedure might need to be done again after an update, or you put netbeans_jdkhome into the configuration file in your home directory (see above).

The unpack200 plugin was removed in JDK version 14, causing plugin installation in Netbeans to fail. As a workaround, one can set netbeans_jdkhome in /usr/share/netbeans/etc/netbeans.conf to an earlier JDK version. After plugin installation, you can return to the default JDK, but this will have to be repeated for each plugin update.

Large and complex Java programs are demanding of memory and processorresources, and NetBeans is no exception. Furthermore, whereas someprograms can anticipate approximately how much memory or CPU timethey will need, NetBeans, which allows the user to design anarbitrarily complex project, can make no such apriori assessment.

The absolute minima for running NetBeans aremuch more modest than the practical minima. Forinstance you can run NetBeans on an AMD 5x86 at166 MHz with 64 MB of RAM and a 640 X 480 screenresolution, but only if you have no real work to do in NetBeans orany other tasks to perform on the machine in question. We knowbecause we have tried it.

That said, we list in Table 1-1 thepractical minima for running NetBeans on severalpopular platforms. These are of necessity somewhat subjective. Onerule of thumb is that serious developers should take our word on theminima, but you can get by with less machine than we recommend if youonly plan to explore NetBeans lightly (preparatory to findingyourself a more satisfactory platform on which to do seriousdevelopment).

For instance, this chapter and its illustrations are being developedon a Sun Blade with a 500-MHz UltraSparc II and 640 MB of memory. Amedium-sized project currently open in NetBeans is consuming about184 MB of memory on this machine, with peaks noticeably higher whilecompiling. As with any advanced design tool, NetBeans will alwayscheerfully accept more hardware resources and perform better forhaving them. The bigger and the more complex your projects are, themore NetBeans will want.

Also, you must consider what else you will be running at the sametime as NetBeans. Are you developing an EJB project and debugging byrunning either JBoss or WebLogic as an application server instance onyour local machine? Give that Wintel/Lintel machine a minimum of 512MB physicalRAM and your Solaris Sparc machine 640 MB to 1 GB.

Many operating systems nowadays, such as Linux and Solaris, come witha JDK pre-installed. Even so, you may want to obtain a later versionof the JDK. At the web site java.sun.com ( ) you can obtain free ofcharge the JDK for the following operating environments:

3a8082e126