Community
Participate
Working Groups
With the same configuration as explained here: http://aniszczyk.org/2011/05/18/eclipse-org-signing-support-for-maven-tycho/#disqus_thread for GMF-Tooling ) https://hudson.eclipse.org/hudson/job/tycho-gmp.gmf.tooling/ ), the sequence of executions always creates a signed/site_assembly.zip file after signing. Then the process of repacking continues with the not-signed file. Is there an outputFile configuration prossible?
Well you can just reset the inputFile configuration option on the pack mojo to get this working, that is what most of the examples do. but to make this a bit easier I extended the PackMojo with a new RepackMojo that sets the default for inputFile to ${project.build.directory}/signed/site_assembly.zip" which should address the common use case
Sounds good, IMHO, it would be even easier if all the signing stuff would take place "on site" on the default file produced by Tycho.
What is that one called, I think its streamlined for our jetty builds atm and what the site production produces, I suspect its called something else for products, etc.
I think for most projects, it will be ${project.build.directory}/${artifactId}.zip. I agree with the need to be able to put something else as inputFile, but with this default value, it will be much easier to use for most eclipse projects.
