thanks for pointing this
out.
So I have to do the described process of branching for each bundle
separatly?
As for the package namespaces: they coincide with the bundle
names. So yes, each bundle has its separate namespace.
And the first consumer of all this will be the eTrice project. We
had a Google Summer of Code project [1] last year with the goal to
employ the KIELER library for layouting our state machine and
structure diagrams.
The student obtained very nice results and I think they even have
potential to be improved.
For those who are interested in more details please refer to the
KIELER homepage [2].
Thanks,
Henrik
[1] http://wiki.eclipse.org/ETrice/GSoC/2012/DiagramLayout_Kieler
[2] http://www.informatik.uni-kiel.de/en/rtsys/kieler/
Am 04.02.2013 19:27, schrieb David M
Williams:
No, features would
not be appropriate for
Orbit. In a properly modularized system, any feature you come up
with (or,
they've come up with, in this case) should be just one
recommendation on
how to combine the bundles, not required. It might be helpful if
you created
a wiki describing the "recommended features and use", and point
to it in your "notes" that are part of the ip log xml files,
but there's no reason consumers would have to use those
particular features.
Normally a separate CQ is
required for
each bundle ... though that's more IP process policy, not part
of Orbit.
As for "container", in cvs,
normally each bundle would have its own, and see no reason this
would be
different.
de.cau.cs.kieler.core.kgraph
de.cau.cs.kieler.core
de.cau.cs.kieler.kiml.gmf
de.cau.cs.kieler.kiml.graphiti
de.cau.cs.kieler.kiml.graphviz.dot
etc.
One question that comes to mind, just going by
names,
does each bundle have its own package namespace, matching the
bundle's
name?
Ones like "de.cau.cs.kieler.kiml.graphiti"
sound like it might have the same, but modified, packages as
graphiti itself,
which if true, requires extra care not to interfere with
others who may
just "import packages" from graphiti.
What project is this for, just out of
curiosity?
Thanks,
From:
Henrik Rentz-Reichert
<hrr@xxxxxxxxx>
To:
orbit-dev@xxxxxxxxxxx,
Date:
02/04/2013 12:13 PM
Subject:
[orbit-dev]
Adding KIELER diagram layout library to Orbit
Sent by:
orbit-dev-bounces@xxxxxxxxxxx
Hi,
I'd like to add the KIELER diagram layout library to Orbit. The
library
is developed at the University of Kiel (Germany) and is
published under
the EPL.
The part that I would like to add to Orbit comprises some basic
bundles
and adapters to GMF and Graphiti.
In total I have to add 3 features and 11 plug-ins (and sources,
see the
listing below).
Should I add a top level container, e.g.
de.cau.cs.kieler
and place the features and plug-ins inside that?
Are features supported by Orbit at all?
Thanks for advising me,
Henrik
./features:
de.cau.cs.kieler.kiml.gmf.feature.source_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.gmf.feature_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.graphiti.feature.source_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.graphiti.feature_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.feature.source_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.feature_0.7.1.201212192152.jar
./plugins:
de.cau.cs.kieler.core.kgraph.source_0.4.1.201212192152.jar
de.cau.cs.kieler.core.kgraph_0.4.1.201212192152.jar
de.cau.cs.kieler.core.source_0.8.0.201212192152.jar
de.cau.cs.kieler.core_0.8.0.201212192152.jar
de.cau.cs.kieler.kiml.gmf.source_0.5.1.201212192152.jar
de.cau.cs.kieler.kiml.gmf_0.5.1.201212192152.jar
de.cau.cs.kieler.kiml.graphiti.source_0.3.1.201212192152.jar
de.cau.cs.kieler.kiml.graphiti_0.3.1.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.dot.source_0.6.1.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.dot_0.6.1.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.layouter.source_0.6.2.201212192152.jar
de.cau.cs.kieler.kiml.graphviz.layouter_0.6.2.201212192152.jar
de.cau.cs.kieler.kiml.service.source_0.3.0.201212192152.jar
de.cau.cs.kieler.kiml.service_0.3.0.201212192152.jar
de.cau.cs.kieler.kiml.source_0.11.1.201212192152.jar
de.cau.cs.kieler.kiml.ui.source_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml.ui_0.7.1.201212192152.jar
de.cau.cs.kieler.kiml_0.11.1.201212192152.jar
de.cau.cs.kieler.klay.force.source_0.1.1.201212192152.jar
de.cau.cs.kieler.klay.force_0.1.1.201212192152.jar
de.cau.cs.kieler.klay.layered.source_0.3.1.201212192152.jar
de.cau.cs.kieler.klay.layered_0.3.1.201212192152.jar
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
|
