topic Re: problem with release strategy in Alfresco Archive

problem with release strategy

m2spring — Wed, 11 Jul 2012 20:20:59 GMT

Hi Tijs,I'm working on an integration of the Activiti engine with Jenkins in form of a Jenkins plugin (http://wikicentral.cisco.com/display/JENKINS/Jenkow).This integration allows to define Jenkins job "orchestrations" as BPMN workflows.For the authoring of these workflows I rely on Activiti Designe

Re: problem with release strategy

m2spring — Fri, 10 Aug 2012 22:55:16 GMT

Tijs,

here's a simple solution, in module org.activiti.designer.updatesite
- change the packaging from clipse-update-site to eclipse-repository,
- rename site.xml to category.xml.

Tycho will then also create org.activiti.designer.updatesite-5.9.3.zip which is the zipped-up update site.

If you do 'mvn deploy' this zip file will end up on the Maven repository.
From there I can consume it as a versioned artifact.

This would solve my problem.

Thanks!
-Max

Re: problem with release strategy

trademak — Wed, 15 Aug 2012 07:54:45 GMT

Hi Max,

That sounds like a decent solution. Will Tycho also keep generating an update site as well when you change it to an eclipse-repository?
If that's not the case I can still add an additional project for this of course.

Best regards,

Re: problem with release strategy

m2spring — Mon, 20 Aug 2012 17:22:36 GMT

Hi Tijs,

yes, with packaging=eclipse-repository Tycho produces the typical update site hierarchy, too.
It sits under target/repository/ (with packaging=eclipse-update-site it sits under target/site/).

Can you make this change?

Thanks!
-Max