The three minor hurdles to configuring Jetty 7 and Maven are making sure port 80 is not already taken, getting the right connector implementation configured, and running Maven as sudo so that Jetty has permission to run on Port 80. In OS X, you can see if anything is already running on port 80 by running the following command from Terminal:

If you're on OS X and see something running on Port 80 yet you didn't install a webserver, chances are it's Sharing. Go to System Preferences > Sharing and disable it. Otherwise, figure out what process is running on port 80 and make it go away.

Now to configure the Jetty Maven plug-in, here is what my configuration looks like which you should replicate in your pom.xml under the plugins section (and adjust to your particular directory structure and desired context):

One of the difficulties I encountered was getting the connector working correctly. Since Maven has moved to be an Eclipse project, the package structure for the connector has changed and thus the reason most of the existing documentation on getting custom connectors to work did not work for me.

The last remaining hurdle to overcome is that running a standard “mvn jetty:run” doesn't work on OS X (and likely Linux as well). You'll see the error message “Embedded error: Permission denied”. If you run Maven with error stacktraces enabled, you'll see an exception that looks like this:

This is because you need elevated permissions to run applications on lower ports on *nix based systems. Simply run it as sudo, “sudo mvn jetty:run” and you'll be good to go.

Not a terribly tough problem to overcome on your own, but I thought I'd try and try to save someone some time if they run across the same issues.

Microsoft Remote Desktop for OS X

Alternatively, you can also try downloading CoRD, an open source Remote Desktop Client and installing it. It seemed to have trouble connecting to my Windows XP workstation for whatever reason, but that doesn't mean it won't work for you of course.

CoRD

CoRD is a Mac OS X remote desktop client for Microsoft Windows computers using the RDP protocol. It's easy to use, fast, and free for anyone to use or modify.

Basically in any Unix type derivative such as Linux such (Ubuntu, RedHat, SuSe, etc.), as well as Mac OS X, all that you need to type this at the command line:

I remember there being a couple of commands in Windows which you could do this with, but it's been so long since I've used Windows on a regular basis I honestly don't remember how to do it. I do know you can use TCPView to accomplish the same thing, however.

I've been up pretty late doing a little work and tying-up some last minute Christmas shopping, and out of the blue this Apple update window popped-up:

I'm super glad to finally see an Apple release of Java 6! I've been developing with SoyLatte lately and was going to write a quick tutorial on how to get it up and running on MacOS X, so I guess I don't necessarily need to do that now. Although given Apple's secrecy about Java releases and the future of Java on MacOS X, it certainly doesn't hurt to have an alternative around.

I'm still on Tiger-- I assume Leopard users are seeing this update too?

Though Java 6 didn't provide quite as much new syntactic sugar as Java 5, the performance increases in Java 6 are pretty dramatic. I highly recommend giving Java 6 a look if you're doing any development which runs on the JVM if you haven't already switched.

Keep in mind that this is mostly a developers port as it's not yet integrated into Cocoa, the MacOS X native GUI. Desktop applications will run under X11, but this is the next hurdle to tackle (though it seems to be a pretty big one).

.DS_Store (Desktop Services Store) is a hidden file created by Apple Inc's Mac OS X operating system to store custom attributes of a folder such as the position of icons or the choice of a background image. By default, Mac OS X will create a .DS_Store file in every folder that it accesses, even folders on remote systems (for example, folders shared over a SMB or AFP connection) and even if the user has only customized the appearance of the folder by moving its Finder window. This is in contrast to the preexisting system for the same purpose used in previous versions of the Macintosh Finder, which would merely place a number of invisible files at the root of the volume being accessed (even on alien filesystems), always storing the settings and metadata for all of the folders in the entire volume within this single set of files.

Unfortunately it seems that you can only prevent Finder from creating these files on network shares and not on your local machine. Here's how you do it:

1. Open the Terminal application (though I highly recommend using iTerm instead)
2. Type in the following command:

   defaults write com.apple.desktopservices DSDontWriteNetworkStores true

   and press enter

3. Reboot your machine so that the changes will take effect

I haven't found a good way to prevent OS X from creating them on local file systems, but perhaps someone out there has some suggestions? Other than creating a script to delete them and adding it to cron, I'm not sure of a way to at least clean them up in an automated fashion. I did run across an application called DS_Store Cleaner which helps clean-up said files, though.

tobin:~ brandon$ defaults write com.apple.finder AppleShowAllFiles TRUE
tobin:~ brandon$ killall Finder

Now you can actually see all of the directories which start with periods, etc. Enjoy!

Anyhow there are several symptoms you'll see if the permissions are wrong in your user folder such as:

• If you're browsing to your home folder using Finder and get a message like 'The folder "username" could not be opened because you do not have sufficent access privileges'
• When trying to access your home folder in a terminal, you keep getting redirected back to /

Basically if you can't access your home directory in Mac OS X, this blog entry is for you. There is a "repair permissions" utility in OS X but it does not repair permissions for user directories, so you have to take care of it manually.

To repair a specific users permissions in Apple OS X, type the following command in a terminal and replace "username" in the command below with the name of the users permissions you need to fix:

You'll need to reboot so that Finder will pick-up the permission changes, but that should clear-up any user specific permission problems if you are locked out of your home directory.

The first day or two I felt like a bull in a China shop on the MacBook. The process for installing software didn't make any sense to me, I kept using the control key for common shortcuts, and in general I was trying to figure-out how to setup the full software stack I'm now working on without really having a good understanding of the OS I was using on my workstation. I'm sure I've looked retarded to my new co-workers for the most part so far, but I feel like making the switch is really starting to pay dividends.

For starters, there is just no comparison between the fit and feel of a MacBook Pro to a Dell laptop. My Dell seems like a total piece of crap now, and it annoys me to have to use it. It's big, heavy, clumsy, and shodily assembled compared to the MacBook. I look at some of my co-workers Dell laptops and am very glad that I picked the Mac, though some of them have some 12" Lenovo's which are pretty sweet.

Since I'm only a couple of weeks in, I hesitate to list all of the various software and so forth that I've found useful, but I'll get around to posting that in a couple of weeks once I feel like that list is more finalized. Instead, I thought it might be useful to post some of the pros and cons I've noticed coming from using Windows and Linux:

Pros:

• Unix with a very nice GUI. That's really enough to sell someone right there. I'm a command line junkie and it's nice to have Bash and all of the assorted Unix facilities and software available
• The hardware is really good-- it has great fit and finish. I can even use the MacBook Pro on my lap without getting scalded. There are just so many little things that you notice over time about the MacBook which are ingenious (like the light sensitive keyboard backlighting for instance)
• Everything just works. Had I attempted to set the same environment up on Windows I would have had to bludgeon myself with Cygwin. I haven't had to deal with any of the annoying dependency problems that Linux has.
• I actually like the hardware lock-in. It makes it much easier to find accessories for your given hardware, and you can easily compare specs and application performance with other users, etc. I'm sure this also helps make the OS a lot better as well since they don't have to support every chipset and piece of hardware under the sun.

Cons:

• Some of the software seems like it's dumbed down too much. I understand it's a design philosophy of the Mac, but with some software I find myself looking for the "Advanced" mode. I'm not sure what you would call the file browsing software, but it was my primary complaint until I found Path Finder
• The concept of Free Software seems to be beyond a lot of people in the Mac community. Every little add-on that makes software suck less is likely to cost you $12-$15.
• There aren't really any Mac specific ergonomic keyboards. I'm currently using an MS Natural keyboard when I dock at work, but I find it hard to get used to shortcuts because I'm still using a keyboard with a Windows layout

All that I can say is that from the perspective of a big Unix fan who does Java development, I feel like the Mac offers a great platform for both software development as well as an everyday workstation OS. I'll get around to posting a list of software that I've found to be useful in a couple of weeks once I feel like I've got most of what I need.

Find the following registry entry:

And set it to 0. Restart the ColdFusion Server service, and go to the Administrator to set a new password.

OR:

Use this code snippet to retrieve the password values:

For ColdFusion 6 MX, ColdFusion 7 MX, and ColdFusion 8:

• Stop the "ColdFusion MX Application Server" Service
• Open the "neo-security.xml" file contained at %CFMXInstallRoot%\lib
• Find the line: "<var name='admin.security.enabled'><boolean value='true'/></var>" and change the true to false, then save the file
• Restart the "ColdFusion MX Application Server" Service
• Go to the ColdFusion Administrator again and set a password