Hi, > I suggest that we only do 1.3+ to avoid confusion... Ok, but so if our 1.3 jars doesn't contain the (really required ?) files under META-INF like LICENSE, NOTICE, DISCLAIMER) are we ready to publish (after the 1.3 release has been accepted) or should they be regenerated (and maybe voted another time) ?
> Signed in Apache jargong only means ".asc" files. Those are so called > detached PGP signatures, and from that it is possible to verify > authenticity of artifacts published. See Ok, I'll try to look, thanks. > Yes, Maven wants the POMs to be present, but succeeds even without > them. Maven also have deployment tools, so once the release is > properly cut, the publishing to Maven central will go via a "mvn > deploy:deploy-file" which if it is not given a POM will create a > skeletal one, which I think for our usage is good enough (we don't > have dependencies). I agree, I've tried some times, and for simpler projects (in terms of dependencies) auto-generated poms are already good. > You can ssh directly to the people.apache.org server with your username > and password. Once the server is back up, that is :). If you're > in Windows, you'll need Putty, SecureCRT, or some equivalent. Once there, > you have shell access, with the appropriate permissions on the appropriate > parts of the file system :). I can certainly help more if you're unfamiliar > with Linux/Unix commands once you get in. Ok, I'll try after the release has been accepted. Thanks a lot to everyone, Sandro
