Hi Brian, In the JIRA ticket, you mention that "the bundles that were created do not have signatures so they won't pass". Step 4 in the earlier document suggests that we should sign the files within the bundles, rather than the bundles themselves:
http://www.apache.org/dev/release-publishing.html#repo-step-by-step Is that also the expected procedure for the new system? If so, can you confirm that we should sign both the pom.xml file as well as the JAR? Thanks, Greg On Dec 6, 2009, at 7:59 AM, Greg Brown wrote: > Thanks Brian. I just took a look at the JIRA ticket - I'll follow the steps > you suggested and post any additional questions/comments there. > Greg > > On Dec 5, 2009, at 11:01 PM, Brian Fox wrote: > >> Greg, I created the issue and setup the project. See my comments here >> regarding the bundles: >> https://issues.apache.org/jira/browse/INFRA-2364 >> >> On Fri, Dec 4, 2009 at 5:37 PM, Brian Fox <[email protected]> wrote: >>> Hi Greg, yes I'll take a look. Since it's an apache project, we should >>> use http://repository.apache.org for this. We have support to stage >>> bundles in the latest version so let me get the pivot project setup >>> and then I'll give some docs on this. Can you file a jira >>> here:https://issues.apache.org/jira/browse/INFRA-1896 ? >>> >>> On Fri, Dec 4, 2009 at 5:24 PM, Greg Brown <[email protected]> wrote: >>>> Hi Brian, >>>> >>>> I managed to install the Pivot artifacts in a local Maven repository and >>>> successfully built a sample project that lists them as dependencies. So, I >>>> am optimistic that the POMs are structured correctly. >>>> >>>> Next, I attempted to package the artifacts for manual upload as described >>>> on this page: >>>> >>>> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >>>> >>>> The results are in this zip file, which contains one JAR per Pivot >>>> artifact: >>>> >>>> http://ixnay.biz/pivot-bundles.zip >>>> >>>> Would it be possible for you to take a quick look and verify that they are >>>> in the correct format for manual upload? >>>> >>>> If so, what would be the next steps to get them into the central >>>> repository? Is there still a way for Apache projects to do this without >>>> needing to go through the 4-week process described on the upload page? If >>>> not, that's OK - I'm just wondering. >>>> >>>> (Note that the artifacts themselves are not actually ready for upload - I >>>> am just trying to get the process worked out in anticipation of Pivot's >>>> graduation. The final artifacts for Pivot 1.4 probably won't be ready for >>>> another few weeks.) >>>> >>>> Thanks again for your help, >>>> Greg >>>> >>>> >>>> On Dec 3, 2009, at 11:27 AM, Brian Fox wrote: >>>> >>>>> Hi Greg, I'll take a look later today and ping back on the pivot dev >>>>> list with what I find. >>>>> >>>>> On Thu, Dec 3, 2009 at 6:44 AM, Greg Brown <[email protected]> wrote: >>>>>> Forwarding this message to [email protected] in case >>>>>> [email protected] wasn't the right place. Also, since sending the >>>>>> original message, I have heard that the document I had been referring to >>>>>> might be outdated. >>>>>> >>>>>> Can anyone help? >>>>>> >>>>>> Thanks! >>>>>> Greg >>>>>> >>>>>> Begin forwarded message: >>>>>> >>>>>>> From: Greg Brown <[email protected]> >>>>>>> Date: December 2, 2009 12:38:13 PM EST >>>>>>> To: [email protected] >>>>>>> Cc: [email protected] >>>>>>> Subject: Upload Apache Pivot artifacts to central repository >>>>>>> Reply-To: [email protected] >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Apache Pivot is preparing for graduation, and we would like to upload >>>>>>> our next set of release artifacts to the central Maven repository. We >>>>>>> don't currently use Maven as a build tool, so I have been trying to >>>>>>> follow the manual upload instructions listed here: >>>>>>> >>>>>>> http://www.apache.org/dev/release-publishing.html#maven-repo >>>>>>> >>>>>>> There is a section at the bottom that is meant to explain how to create >>>>>>> an appropriate POM file, but it does not appear to be complete: >>>>>>> >>>>>>> http://www.apache.org/dev/release-publishing.html#repository-descriptor >>>>>>> >>>>>>> I have created some POMs that I think should work, but it would be very >>>>>>> helpful if someone with a knowledgeable eye could take a quick look to >>>>>>> make sure that they contain the correct information, are structured >>>>>>> properly, etc. There is a root POM in the trunk, and a POM in each >>>>>>> project-specific subdirectory that we plan to publish to the repository >>>>>>> (note that these files refer to the anticipated future name and >>>>>>> location of the project, as opposed to its current Incubator name and >>>>>>> location): >>>>>>> >>>>>>> http://svn.apache.org/repos/asf/incubator/pivot/trunk/ >>>>>>> >>>>>>> Based on the documentation I have read thus far, I assume that we'll >>>>>>> want to place our compiled JARs in a pivot/jars directory, and >>>>>>> structure our POMs as follows: >>>>>>> >>>>>>> pivot/poms >>>>>>> pom.xml >>>>>>> /core/pom.xml >>>>>>> /web/pom.xml >>>>>>> /wtk/pom.xml >>>>>>> /wtk-terra/pom.xml >>>>>>> >>>>>>> I don't think we'll need to use the distributions directory, and I >>>>>>> assume that the licenses directory should simply contain a copy of our >>>>>>> main LICENSE file. Is this all correct? >>>>>>> >>>>>>> Also, one of our mentors, Martijn Dashorst, suggested that there might >>>>>>> be a top-level ASF POM that the root Pivot POM could extend (rather >>>>>>> than duplicating the ASF info). If so, could you point us to it? >>>>>>> >>>>>>> Thanks - your assistance is very much appreciated! >>>>>>> >>>>>>> Greg Brown >>>>>>> Apache Pivot >>>>>>> >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
