[
http://jira.codehaus.org/browse/MAVENUPLOAD-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106611
]
Matt Raible commented on MAVENUPLOAD-1701:
------------------------------------------
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.
> Add scripts to sync AppFuse release repository
> ----------------------------------------------
>
> Key: MAVENUPLOAD-1701
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1701
> Project: maven-upload-requests
> Issue Type: Wish
> Reporter: Matt Raible
>
> Contegix manages the static.appfuse.org and they've confirmed the public key
> is in place.
> AppFuse Core:
> -------------------------
> #!/bin/sh
> CONTACTS="[EMAIL PROTECTED]"
> MODE=rsync_ssh
> [EMAIL PROTECTED]:/var/www/appfuse-releases
> GROUP_DIR=org/appfuse/
> AppFuse Maven Plugin:
> -------------------------
> #!/bin/sh
> CONTACTS="[EMAIL PROTECTED]"
> MODE=rsync_ssh
> [EMAIL PROTECTED]:/var/www/appfuse-releases
> GROUP_DIR=org/codehaus/mojo/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
