Re: maven bundles
On Thu, Aug 26, 2010 at 11:00:18AM -0400, Benson Margulies wrote: I repushed with the repaired POM. Everything looks fine. Thanks. See https://issues.apache.org/bugzilla/show_bug.cgi?id=49830 for how I did it. In short: 1. unpack the bundle.jar 2. run maven to automate the production of gpg signatures for all the pieces and to push them to the staging repo. 3. interact with the nexus gui to 'close' the staging repo. Thanks. But this does use maven, and I am working towards a solution without maven, which seems feasible, and more useful for projects which do not use maven as their build system. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
Simon, It uses maven to script signing the pieces in a way that works on both Windows and Linux. If you want to solve that problem some other way, go right ahead. Since only people with an account on Nexus and a key can do this procedure, you might feel that requiring Maven is acceptable. Or you might just require linux and write a shell script to do the signing. In any case, I felt called upon to document what I did. You might want to check this in just to answer the question, 'How was this done in 1.0?' even if you never use it again. --benson On Fri, Aug 27, 2010 at 5:38 AM, Simon Pepping spepp...@leverkruid.eu wrote: On Thu, Aug 26, 2010 at 11:00:18AM -0400, Benson Margulies wrote: I repushed with the repaired POM. Everything looks fine. Thanks. See https://issues.apache.org/bugzilla/show_bug.cgi?id=49830 for how I did it. In short: 1. unpack the bundle.jar 2. run maven to automate the production of gpg signatures for all the pieces and to push them to the staging repo. 3. interact with the nexus gui to 'close' the staging repo. Thanks. But this does use maven, and I am working towards a solution without maven, which seems feasible, and more useful for projects which do not use maven as their build system. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
I've released. It's now on Apache, and will show up on Central when replicated.
Re: maven bundles
On Mon, Aug 23, 2010 at 09:52:56AM +0200, Simon Pepping wrote: On Fri, Aug 20, 2010 at 07:18:11PM -0400, Benson Margulies wrote: I'm pretty sure that infra is not going to make an exception to the requirement that only a member of the LDAP group for project X can publish maven artifacts for X. I am perfectly sure, after some recent discussions at the incubator and on members@, that your PMC can vote to grant me membership in the group and nothing else. In fact, the PMC chair could just tell infra to make it so :-) I can do that. I have asked the PMC for their opinion. I will let you know progress ASAP. No objections. Done. You are now a member of the unix group xmlgraphics. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
On Fri, Aug 20, 2010 at 07:18:11PM -0400, Benson Margulies wrote: Otherwise, some committer is going to have to be willing to follow the instructions at: http://www.apache.org/dev/publishing-maven-artifacts.html#signing up Unfortunately, those instructions assume a maven build. I'm fairly sure that I know what to do instead in your case, but some improvisation may follow. To be clear, I've submitted the INFRA ticket for you already. I spent some time on understanding this maven repository business. I see that xmlgraphics commons and fop are already configured in Nexus. They are present in the repository with the previous releases. Does this mean that no action of infrastructure is needed? The Nexus book suggests that I can upload the bundle from a GUI, without the need for a maven build. I could get to this interface screen, but did not try the actual upload. I think we have to solve some issues with our bundle: Missing in our POM: the parent section. Missing in our bundle: signatures, md5 and sha1 checksums for the 3 jar files and the pom file. Should these files also be included in the bundle? I will try to get advice on the release-discuss list. Maybe I can do this deployment, without having to install maven. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
Simon, Brian Fox set up Nexus late last night my time after I pinged him, that's why Nexus is set up. I have a script that will create the checksums and signatures (using Maven itself) and push the pieces. You don't need that parent section. The document mixes up things that are convenient for maven builds with things that are required. I plan to push later today. --benson On Thu, Aug 26, 2010 at 7:09 AM, Simon Pepping spepp...@leverkruid.eu wrote: On Fri, Aug 20, 2010 at 07:18:11PM -0400, Benson Margulies wrote: Otherwise, some committer is going to have to be willing to follow the instructions at: http://www.apache.org/dev/publishing-maven-artifacts.html#signing up Unfortunately, those instructions assume a maven build. I'm fairly sure that I know what to do instead in your case, but some improvisation may follow. To be clear, I've submitted the INFRA ticket for you already. I spent some time on understanding this maven repository business. I see that xmlgraphics commons and fop are already configured in Nexus. They are present in the repository with the previous releases. Does this mean that no action of infrastructure is needed? The Nexus book suggests that I can upload the bundle from a GUI, without the need for a maven build. I could get to this interface screen, but did not try the actual upload. I think we have to solve some issues with our bundle: Missing in our POM: the parent section. Missing in our bundle: signatures, md5 and sha1 checksums for the 3 jar files and the pom file. Should these files also be included in the bundle? I will try to get advice on the release-discuss list. Maybe I can do this deployment, without having to install maven. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
On Thu, Aug 26, 2010 at 07:56:25AM -0400, Benson Margulies wrote: I've done the upload, but I'm not going to promote without giving people a chance to look around. https://repository.apache.org/service/local/staging/deploy/maven2 I'll post a patch with the explanation about how I did this. If I don't hear anything by tomorrow AM to the contrary, I'll promote the staging repository. Thanks. Unfortunately, I noticed one problem in our fop pom file: fop-1.0 depends on xmlgraphics-commons-1.4, not on 1.3. The following change: dependency groupIdorg.apache.xmlgraphics/groupId artifactIdxmlgraphics-commons/artifactId - version1.3/version + version1.4/version /dependency should be made. I made that change and added the parent element, and I updated the bundle on http://people.apache.org/~spepping/fop-1.0. The md5 and sha1 files do not include the file name, which is expected by my md5sum and sha1sum programs. I guess that that is not a real problem. Otherwise everything is as expected. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles
It is easier for me to update my copy and do this again. On Thu, Aug 26, 2010 at 9:59 AM, Simon Pepping spepp...@leverkruid.eu wrote: On Thu, Aug 26, 2010 at 07:56:25AM -0400, Benson Margulies wrote: I've done the upload, but I'm not going to promote without giving people a chance to look around. https://repository.apache.org/service/local/staging/deploy/maven2 I'll post a patch with the explanation about how I did this. If I don't hear anything by tomorrow AM to the contrary, I'll promote the staging repository. Thanks. Unfortunately, I noticed one problem in our fop pom file: fop-1.0 depends on xmlgraphics-commons-1.4, not on 1.3. The following change: dependency groupIdorg.apache.xmlgraphics/groupId artifactIdxmlgraphics-commons/artifactId - version1.3/version + version1.4/version /dependency should be made. I made that change and added the parent element, and I updated the bundle on http://people.apache.org/~spepping/fop-1.0. The md5 and sha1 files do not include the file name, which is expected by my md5sum and sha1sum programs. I guess that that is not a real problem. Otherwise everything is as expected. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: maven bundles [was: Re: findbugs results]
I'm pretty sure that infra is not going to make an exception to the requirement that only a member of the LDAP group for project X can publish maven artifacts for X. I am perfectly sure, after some recent discussions at the incubator and on members@, that your PMC can vote to grant me membership in the group and nothing else. In fact, the PMC chair could just tell infra to make it so :-) Otherwise, some committer is going to have to be willing to follow the instructions at: http://www.apache.org/dev/publishing-maven-artifacts.html#signing up Unfortunately, those instructions assume a maven build. I'm fairly sure that I know what to do instead in your case, but some improvisation may follow. To be clear, I've submitted the INFRA ticket for you already. On Thu, Aug 19, 2010 at 2:43 PM, Simon Pepping spepp...@leverkruid.eu wrote: On Thu, Aug 19, 2010 at 07:12:47AM -0400, Benson Margulies wrote: Maven is just not (yet) for me. I wait for a friendly ASF committer who is willing to do the deployment for us. That is simply the best solution for the FOP team and FOP's maven users. OK, I'm game. Do you have the official 1.0 Maven bits sitting someplace? XML Graphics Commons maven bundle, signature and MD5 checksum, and pom file (extracted from the jar file): http://people.apache.org/~spepping/commons-1_4/. MD5 checksum: 1c36c31e4ffa4a5293828adb41ac8788 xmlgraphics-commons-1.4-bundle.jar FOP maven bundle, signature and MD5 checksum, and pom file (extracted from the jar file): http://people.apache.org/~spepping/fop-1_0/. MD5 checksum: b47043cea49a9291bc0ed369a4150dd3 fop-1.0-bundle.jar Thanks for your help. Simon -- Simon Pepping home page: http://www.leverkruid.eu
