On 2/26/2013 8:14 AM, Peter Klügl wrote: > OK, I found the reason. I have set assembly.attach to false so the assemblies > (e.g. source-release) won't be uploaded to the staging repository. With > assembly.attach=true, as uimaj uses it I think, the asc files are present in > the target folder. > > May I solve this issue with a workaround, for example, by keeping > assembly.attach=false and manually signing the assemblies?
The other thing that the UIMA parent pom does is to have these assemblies "attached", so they get signed, but have the deploy step "skip" deploying them. See the profile "build distribution" which is activated if there is a file in /src/main/assembly/bin.xml, in the UIMA parent pom. Would this work for your case? -Marshall > > I prepared two new folders (dist2 and source2), which contain the assemblies > built with rc6 and assembly.attach=true. > > http://people.apache.org/~pkluegl/uima-releases/textmarker-2.0.0-rc6/dist2/ > http://people.apache.org/~pkluegl/uima-releases/textmarker-2.0.0-rc6/source2/ > > Peter > > > On 26.02.2013 10:26, Peter Klügl wrote: >> On 25.02.2013 16:37, Marshall Schor wrote: >>> The binary convenience builds zips/tar.gzs are missing the signatures >>> (.asc). >>> >>> -Marshall >> >> Hmm... can you give me a hint who schould create them? The gpg call? >> >> "mvn install -Papache-release" on uimaj creates them, but on textmarker it >> doesn't, and I could not yet find the reason. >> >> Peter > >
