Did you look at the http://enroute.osgi.org/qs/050-start.html <http://enroute.osgi.org/qs/050-start.html> tutorial? The http://enroute.osgi.org/qs/200-workspace.html <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 <pa...@a2zliving.com> 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
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
