Hi all, Sorry to keep replying to myself :). It looks like there are some instructions for Ant/Ivy, so this should be technically feasible. The first step for the Xerces project to take (assuming you want to continue doing this) is to raise a JIRA and fill out the following questions (See http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up for details).
I've answered them as best I can below (in brackets): - *Project URL:* a link to your project page - ( http://xerces.apache.org/xerces2-j/) - *SVN URL:* where the source is located in case we need to lookup more information and to provide feedback on your pom - ( https://svn.apache.org/repos/asf/xerces/java) - *Maven Group Ids:* a list of the groupIds for this project. They should all be subgroups of org.apache (xerces) - *Managed By This TLP Project:* if this is a subproject, list the TLP that is responsible. Subprojects usually don't have their own LDAP group, so we need the TLP LDAP group for permissions. (Xerces top level project - http://xerces.apache.org/) Do those answers seem right to you? Would you like me to raise the JIRA on this project's behalf? Cheers, Martijn PS: For those who are curious, once this JIRA is filed, the following will happen: - *Setup the project in Nexus:* We will configure your groupIds in Nexus and link them to the appropriate LDAP group for Authorization - *Move Existing Artifacts:* In order to maintain the proper maven-metadata.xml files and to prevent rsync conflicts in Central, we must move all your artifacts to the new repository. We will move your artifacts from the old repository on people to the new repository and mark the folder in people as read-only to prevent accidental deployments. - *Check POMs:* We will quickly check your POM (if your project is Maven based) for any obvious problems. If you have specific questions or concerns, please call them out in the issue. On Tue, Dec 14, 2010 at 1:35 PM, Martijn Verburg <[email protected]>wrote: > Hi all, > > FYI I've found the following doc: > > http://www.apache.org/dev/publishing-maven-artifacts.html > > I'll be working through it and see what steps to take (I'm hoping there's > some advice/instructions for Ant). > > Cheers, > Martijn > > > On Mon, Dec 13, 2010 at 6:28 PM, Michael Glavassevich <[email protected] > > wrote: > >> Martijn Verburg <[email protected]> wrote on 12/13/2010 01:17:34 >> PM: >> >> > Hi Michael, >> > >> >> >> Hi Martijn, >> >> >> >> Not sure what your build script is going to do, but I suspect the >> >> ASF repository can only contain packages which were released by the >> >> project's PMC, in other words the jars that are already being >> >> distributed for 2.10.0 and 2.11.0. >> > I'm hoping to do exactly that - so get the build script to work with >> > the JARs produced by the 2.10.0 and 2.11.0 tags (I'm working off the >> > 2.11.0 tag for now as an experiment). The build script could then >> > be added to trunk for future releases. >> >> I recall Nathan Beyer (not sure if he's still subscribed to this >> >> list) did this for Xerces a few years back. Though I haven't >> >> searched I would expect that there would be something in the mailing >> >> list archives on what he deployed. >> > OK, I'll go look - but I don't think what was released in the past >> > went through the ASF Nexus (I've searched that repo and there are no >> > versions of xerces there). >> >> Okay. Perhaps the ASF Nexus is something different than the "Repository" >> I knew of. >> >> >> > As of yet I haven't found the admins that run the ASF Nexus - I'll >> > keep looking :) >> > >> > Cheers, >> > Martijn >> >> Michael Glavassevich >> XML Parser Development >> IBM Toronto Lab >> E-mail: [email protected] >> E-mail: [email protected] >> >> >
