Maven Upload Requests

Carlos Sanchez added a comment - 05/Sep/07 1:51 PM you can't sync org.codehaus group, your plugin must be in in your group, or hosted in the codehaus mojo project

Matt Raible added a comment - 05/Sep/07 1:55 PM The reason we're in the org.codehaus group is because 1) we were hosted there and there were too many problems managing development at the SVN level and publishing code and 2) because if we're in this group, users don't have to type the full path to the plugin, they can simply use the "appfuse" prefix. If this is a deal-breaker, we're more than happy to keep hosting it at http://static.appfuse.org/repository. We're just trying to make things easier for our users.

Carlos Sanchez added a comment - 05/Sep/07 1:58 PM definitely you can't publish to org.codehaus.mojo. You don't want other people to post to org.appfuse, right? ;)

Matt Raible added a comment - 05/Sep/07 2:07 PM Is it possible to get the "appfuse" prefix working w/o the plugin having a org.codehaus.mojo groupId?

Carlos Sanchez added a comment - 05/Sep/07 3:03 PM what are you exactly trying to do? in the pom you can put the groupId you want For goals that can run without poms you can use pluginGroups in the settings.xml http://maven.apache.org/settings.html or the commandline mvn groupId:artifactId:version:goal

Matt Raible added a comment - 05/Sep/07 3:15 PM I'm trying to make it possible to allow end users to run "appfuse:*" without further modifying their system. Modifying their settings.xml is a pain and I don't want to make them do that. If they're new to Maven, that's an overwhelming step for newbies. Also, using "org.appfuse.plugins:appfuse:gen" is way too verbose. So I guess my options are 1) Move the plugin to codehaus or 2) continue hosting the plugin in AppFuse's repo? Thanks, Matt

Carlos Sanchez added a comment - 05/Sep/07 4:52 PM they can use appfuse:* in any project that has a pom if it doesn't it's likely gonna be only once and I don't see a big deal on copying and pasting the command line but definitely yes, you can only deploy to org.codehaus.mojo from the mojo project

Matt Raible added a comment - 05/Sep/07 4:57 PM In a project (or archetype's) pom.xml, can I specify a <pluginGroup>? AFAIK, it's only possible to do this in settings.xml. Therefore, if this plugin has an org.appfuse.plugins groupId, users will have to 1) modify settings.xml or 2) use the fully-qualified command. Correct?

Carlos Sanchez added a comment - 05/Sep/07 6:51 PM AFAIK if you have a plugin in the <plugins> section of the pom you can use it the short way

Matt Raible added a comment - 05/Sep/07 7:21 PM Nope, that's not how it works - at least not on my machine with Maven 2.0.7. I tried changing the appfuse-maven-plugin to have a groupId of org.appfuse.mojo and then installed it locally. I then tried changing an appfuse-generated project from using org.codehaus.mojo as the groupId (for the plugin). The result is that it doesn't find the plugin: [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] The plugin 'org.codehaus.mojo:appfuse-maven-plugin' does not exist or no valid version could be found Conclusion: If I want to publish the appfuse-maven-plugin in the central repo, I need to move the code to Codehaus.

Matt Raible added a comment - 05/Sep/07 7:47 PM After blowing away my local repository, I was able to get this to work. I suspect I wasn't able to get it to work in the past because of the http://jira.codehaus.org/browse/MNG-2432? Who knows.