APF-874: Changed the appfuse-maven-plugin's groupId to org.appfuse.

In order to get the appfuse-maven-plugin uploaded to Maven's Central repository, it can't have org.codehaus.mojo as its groupId. The original reason I started using this groupId is because I couldn't get the "appfuse" prefix to work w/o it. Now the prefix seems to work fine (at least locally).

http://jira.codehaus.org/browse/MAVENUPLOAD-1701

NOTE: We realize it makes good sense to change the groupIds to be more specific than "org.appfuse" for many of AppFuse's modules. However, it seems somewhat risky to do this late in the 2.0 game. If we do decide to change them, we'll likely do it for 2.1. Please comment on the following thread if you have any opinions on this:

http://www.nabble.com/Thinking-out-loud-about-groupIds-tf4387544s2369.html

APF-874: Reverted invalid change

APF-874: Changed groupId from org.codehaus.mojo to org.appfuse

APF-874: Changed groupId from org.appfuse back to org.codehaus.mojo.

If we want to allow users to type "appfuse:*", they'll need to register the plugin in their ~/.m2/settings.xml with this change. Therefore, I'm reverting to org.codehaus.mojo as its easier for users. We won't be able to upload AMP to Maven's central repo until we move to Codehaus, but that's OK IMO.

After more IRC discussions, it appears it *is* possible to distribute this plugin w/o requiring users to modify settings.xml, but the fact that we're already using org.codehaus.mojo causes that one to always be picked up first.

Since we're approaching 2.0, I'm going to leave it as org.codehaus.org for now. We can rename it to something else when Maven allows the search order to be configurable or we're ready to remove it completely from AppFuse's repository. Another option is to get everything in Maven's central repository and disable AppFuse's repository so the new one is found instead.