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 <[email protected]> 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 >
