[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nebula-dev] Signing nebula jars

Seems like the build-server profile is not activated on Hudson, then the signing is not performed. Try adding a "-P build-server" to the Maven options of the build.
However, I think this will fail after, because the signing expect the creation of a org.eclipse.nebula.updatesite/target/org.eclipse.nebula.updatesite-${project.version}.zip whereas this does not exist after the build. In GMF and wtp.sieditor, there is no assembly for update-site, everything is performed with the default behavior, and then signing works well.

On 16/08/2011 13:49, Tom Schindl wrote:
Hi,

Well in fact all i did was to copy the root pom.xml egit ;-) One thing i
saw is the directory given there is not available so this might be the
problem.

I'll retry ping the dash mailing list maybe someone is able to point out
whats wrong (my current guess is that the pom, ... is correct but the I
missed some hudson configuration or the wrong directory).

Tom

Am 16.08.11 13:44, schrieb Mickael Istria:
I just saw it is what you did...

On 16/08/2011 13:41, Mickael Istria wrote:
I usually use the eclipse-maven-signing-plugin on the output
repository artifact (packaging=eclipse-repository) of the project. I
always refer to this article:
http://aniszczyk.org/2011/05/18/eclipse-org-signing-support-for-maven-tycho/.
You should try this on the org.eclipse.nebula.updatesite module.

HTH

On 16/08/2011 13:12, Tom Schindl wrote:
Hi Mickael,

No there's currently none, the maven pom is found in CVS though so I've
you'd like to take a look you can do so.

The module is
org.eclipse.swt.nebula/org.eclipse.swt.nebula.nebula-release. If you
find something obvious I'd be very happy if you can show it to me.

Tom

Tom

Am 16.08.11 13:08, schrieb Mickael Istria:
Is there anywhere you track this issue with signing? I'd be glad to help.

On 16/08/2011 13:00, Tom Schindl wrote:
Am 16.08.11 12:59, schrieb wondog:
Hi, is anybody here who could help me with my issue?

I've updated our build to tycho and hudson but I'm still failing to sign
the created artifacts and I didn't yet found someone to help me fix this
issue.

Can we sign nebula plugin jar with our certificate to avoid "unsigned
content warning" during installation?
thanks

Sure you can.

Tom
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
-- 

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink <http://www.petalslink.com> - Open Source SOA

My blog <http://mickaelistria.wordpress.com> - My Tweets
<https://twitter.com/#%21/mickaelistria>



_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev

-- 

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink <http://www.petalslink.com> - Open Source SOA

My blog <http://mickaelistria.wordpress.com> - My Tweets
<https://twitter.com/#%21/mickaelistria>


_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev

-- 

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink <http://www.petalslink.com> - Open Source SOA

My blog <http://mickaelistria.wordpress.com> - My Tweets
<https://twitter.com/#%21/mickaelistria>



_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev


--

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink - Open Source SOA

My blog - My Tweets