Peter,
Yes I have been through those many times.
I presume when you speak of the bnd workspace we are talking about the content we put in the git dir
as detailed in the tutorial.
As a side matter should the orange diagram on http://enroute.osgi.org/qs/200-workspace.html have 2
project.a entries?
Also when I create a new Bnd OSGi workspace as per the tut a cnf dir is created in the eclipse
workspace dir with a .project file inside a well as a cnf in the bnd workspace.
This does not appear in forks of the osgi examples etc.
So to import into the bnd workspace (git) do I just copy the project folder?
Paul
On 10/06/2016 9:31 PM, Peter Kriens wrote:
Did you look at the http://enroute.osgi.org/qs/050-start.html tutorial? The
http://enroute.osgi.org/qs/200-workspace.html should explain this split setup, please tell me what
is missing.
If you import projects, ALWAYS copy them into the bnd workspace.
It is highly recommended by Eclipse (and for good reasons) to mix the git==bnd workspace and the
Eclipse workspace. It does suck a bit however :-(
Kind regards,
Peter Kriens
On 10 jun. 2016, at 12:46, Paul F Fraser <[email protected]
<mailto:[email protected]>> wrote:
Hi,
With the spit setup for EnRoute with eclipse workspace containing very little and the actual code
in a git directory.
If I import an existing project into eclipse with the normal process it end up in the eclipse
workspace, as I suppose I should expect.
How do I import an existing project into the EnRoute environment (git dir)?
Do I need to create new projects and just copy the code into the src dir?
Regards
Paul Fraser
_______________________________________________
OSGi Developer Mail List
[email protected] <mailto:[email protected]>
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
