You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steven Jardine (JIRA)" <ji...@codehaus.org> on 2008/03/07 17:11:28 UTC
[jira] Commented: (MAVENUPLOAD-1934) gnu-hylafax 1.0.0-b2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126464 ]
Steven Jardine commented on MAVENUPLOAD-1934:
---------------------------------------------
I am the admin of the GNU-HylaFAX project. I have setup a repository located at
scp://shell.sourceforge.net/home/groups/g/gn/gnu-hylafax/m2repo
Would you mind adding it to the automatic sync. Thanks!
> gnu-hylafax 1.0.0-b2
> --------------------
>
> Key: MAVENUPLOAD-1934
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1934
> Project: maven-upload-requests
> Issue Type: Task
> Reporter: fabrizio giustina
> Assignee: Carlos Sanchez
>
> the release is made up by 4 artifacts (4 upload bundles below) + 1 parent pom:
> http://repository.openmindonline.it/_bundle-upload/gnu-hylafax-core-1.0.0-b2-bundle.jar
> http://repository.openmindonline.it/_bundle-upload/gnu-hylafax-inet-ftp-1.0.0-b2-bundle.jar
> http://repository.openmindonline.it/_bundle-upload/gnu-hylafax-pool-1.0.0-b2-bundle.jar
> http://repository.openmindonline.it/_bundle-upload/gnu-hylafax-utils-1.0.0-b2-bundle.jar
> http://repository.openmindonline.it/_bundle-upload/gnu-hylafax-1.0.0-b2.pom
> Note that gnu-hylafax uses maven 2 to build, so these are official poms. Groupid is "gnu-hylafax", which is not so good accorting maven convention, but this is how artifacts are officially released.
--
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