Re: [bpmn2-modeler-dev] Target Platform improvements

[Cristiano Gavião <cvgaviao@xxxxxxxxx>]

Hi Bob,

Ok, I'll take some hours tomorrow to work in what I've proposed related 
to tycho.

There won't be any problem about the temporary sites because they will 
be configured at target definition file... when they have changed the 
urls we just need to update our as we do in pom's today.

cheers

Cristiano


On 17/11/11 17:45, Bob Brodt wrote:
> Hi Cristiano,
>
> As you know, this project is still in its infancy and development is "fast and furious" and we welcome all contributions, but keep in mind:
>
> * the BPMN2 metamodel project is still not where it needs to be, that's why I'm keeping a link to a temporary update site
> * graphiti is a "moving target" and trying to build an editor on top of this platform is a challenge
>
> Any help you can provide to improve this project is welcomed!
>
> Bob
>
>
> ----- Original Message -----
> > Hi guys,
> >
> > I got happy to see that bpmn2-modeler is part of eclipse now, and
> > happy
> > to see lot of improvements since last time I worked with the editor
> > from
> > github. Congratulations to all team.
> >
> > But I got some problems installing the plugin from the created update
> > site.
> >
> > After clone the source, I saw some outdated things within the tycho
> > build, mainly in the org.eclipse.bpmn2.modeler.updatesite.feature,
> > that
> > is not creating the site.zip properly. I got some difficult to create
> > a
> > target platform properly inside the IDE, too.
> >
> > So I would like to propose some improvements:
> >
> > - move the site project to a p2 repository project instead;
> >     Besides, using a P2 repo let us to create Composite Repositories,
> >     so
> > we can facilitate the installation of the plugin and all dependencies
> > using only one p2 address.
> >
> > - create a target platform description project (containing one target
> > file per eclipse version, helios/indigo/juno) to easy creation of the
> > dev environment at IDE; actually, this is better than work with
> > repositories at pom, because it will be cases where we need to build
> > with different dependencies components versions depending which IDE
> > version (for example: EMF, 2.7 at Indigo and 2.8 at Juno).
> >
> > - add a juno profile at main pom;
> >
> >
> > cheers
> >
> > Cristiano
> > _______________________________________________
> > bpmn2-modeler-dev mailing list
> > bpmn2-modeler-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/bpmn2-modeler-dev
> _______________________________________________
> bpmn2-modeler-dev mailing list
> bpmn2-modeler-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/bpmn2-modeler-dev