Hello Maarten, I have tried to do an upload tonight and have not been successful so far.
Using the URL resolver, I got these messages : [ivy:publish] parameter found as ivy variable: ivy.status=integration [ivy:publish] :: publishing :: org/apache#ant [ivy:publish] validate = true [ivy:publish] post 1.3 ivy file: using exact as default matcher [ivy:publish] authentication: k='Sonatype Nexus Repository [email protected]' c='Sonatype Nexus Repository [email protected] antoine/********' [ivy:publish] HTTP response status: 404 url=https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ant/ant-parent/1.8.1/ant-parent-1.8.1.pom [ivy:publish] CLIENT ERROR: The server has not found anything matching the request URI url=https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ant/ant-parent/1.8.1/ant-parent-1.8.1.pom [ivy:publish] published ant-parent to https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/ant/ant-parent/1.8.1/ant-parent-1.8.1.pom I am not sure whether the url resolver is able to create the subdirectory or if there is some other problem. I have checked in what I created to try the upload in ant's svn in a new folder from ant-core's trunk called release. [1] Regards, Antoine [1] http://svn.apache.org/repos/asf/ant/core/trunk/release/ Maarten Coene wrote: > First of all, I've never published something to Nexus myself, so I cannot > share you my experience with that... > > >> Is there any support for uploading .asc files in ivy other than >> declaring each asc file as an artefact in its own right ? >> > > I'm afraid you'll have to declare them as artefact. > And maybe you should add the pom + pom.asc too? > So you end up having 1 ivy.xml file for each ant jar file and that ivy.xml > defines 4 artefacts. > > >> I was also wondering whether ivy will recreate sha1 and md5 files >> automatically when publishing, and whether nexus likes to receive them >> or not ? >> > > You can disable Ivy checksum generation by specifying an empty checksums > attribute on the resolver used for publishing. > > >> I also notice that the official documentation of the ibiblio resolver >> [2] says that it does not handle publish, but some email threads lead me >> to think that it can handle publish [3] [4]. >> > > If I look at the source code, publish is not supported by the ibiblio > resolver. > But you can use an url resolver for publishing instead, which has support for > HTTP PUT. > > Maarten > > > > > > ----- Original Message ---- > From: Antoine Levy-Lambert <[email protected]> > To: [email protected] > Sent: Tue, May 18, 2010 5:01:04 AM > Subject: uploading ant with ivy to nexus central repository > > Hi, > > I will this week try to upload the build of ant 1.8.1 using ivy to the > nexus central repository [1] > > What I want to upload are the 20 odd jar files of ant along with their > POM files. I have to provide .asc (GPG ASCII armored signatures) files > for each jar and each POM. > > Is there any support for uploading .asc files in ivy other than > declaring each asc file as an artefact in its own right ? > > Does ivy have a setting to say something like : each jar file must come > with its companion asc file ? > > Also, ant has its own non standard POM files. Do I want to write one ivy > file for ant declaring its 20 odd jar files as artefacts, + the 20 odd > POM files, + 40 odd ASC files with my signature for each jar and each > POM ? Or does the ibiblio resolver automagically knows that each jar has > a POM and each > > I was also wondering whether ivy will recreate sha1 and md5 files > automatically when publishing, and whether nexus likes to receive them > or not ? > > I also notice that the official documentation of the ibiblio resolver > [2] says that it does not handle publish, but some email threads lead me > to think that it can handle publish [3] [4]. > > Regards, > > Antoine > > > > [1] https://issues.apache.org/jira/browse/IVY-1153 > [2] http://ant.apache.org/ivy/history/latest-milestone/resolver/ibiblio.html > [3] > http://article.gmane.org/gmane.comp.apache.incubator.ivy.user/5652/match=nexus > [4] > http://article.gmane.org/gmane.comp.apache.incubator.ivy.user/3426/match=nexus > > > > >
