[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [bpmn2-modeler-dev] Target Platform improvements
|
Yes, like I said "Graphiti is a moving target". I know there were some breaking API changes going from 0.6 to 0.8 - don't know if 0.9 will work on helios, indigo and juno but if it does, we might think about moving to that version...
----- Original Message -----
> Hi,
>
> Now I'm understanding Bob's warnings points in last email... :)
>
> But I could create the p2 and target projects. It seems to be ok on
> indigo.
>
> But I couldn't find a solution for juno, because I just figure out
> now
> that graphiti has some api changes in version 0.9 (that is the
> version
> for juno), as this:
>
> > /**
> > * The Class DiagramEditorFactory.
> > *
> > * A factory for creating DiagramEditorInput objects.
> > *
> > * @see {@link DiagramEditorInputFactory}
> > * @see {@link DiagramEditorInput}
> > * @since 0.9 results from renaming DiagramEditorFactory
>
>
> I'm thinking here and initialy I don't know if would be possible to
> build against both graphiti's 0.8.1 and 0.9.0 using same git tree
> code
> in such case... would ?
>
> what do you think guys ?
>
> 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
>
> _______________________________________________
> bpmn2-modeler-dev mailing list
> bpmn2-modeler-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/bpmn2-modeler-dev
>