You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2008/02/22 20:49: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_124697 ] 

Carlos Sanchez commented on MAVENUPLOAD-1934:
---------------------------------------------

can you put it in some rsync/ssh server and I'll add it to the automatic sync. 
groupId can't be that, should be net.sf.gnu-hylafax

> 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
>
> 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