> On 10 jun. 2016, at 13:51, Paul F Fraser <[email protected]> wrote: > Peter, > Yes I have been through those many times. Please let me know what we can improve …
> 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. The git dir/workspace == bnd workspace. This is paramount because it makes the CI work automatically. The Eclipse workspace contains a lot of stuff in the .metadata directory that is personal and should never be stored in git. (I understand that the mean reason to separate them is that the EGit tends to get confused or at least overburdened when it makes changes in there.) > As a side matter should the orange diagram on > <http://enroute.osgi.org/qs/200-workspace.html>http://enroute.osgi.org/qs/200-workspace.html > <http://enroute.osgi.org/qs/200-workspace.html> have 2 project.a entries? Ehh, no should probably be project.b :-) > 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. Can you point me to a concrete example? The cnf dir must be an eclipse project (it does not have to be a bndtools project though.) In the https://github.com/osgi/workspace <https://github.com/osgi/workspace> template the cnf has the .profile/.classpath files. > So to import into the bnd workspace (git) do I just copy the project folder? I realize that this is unfortunately yes. After you copied them you can then import them. I think you should file an issue on Bndtools to ensure that if the copy checkbox is selected it should copy to the project into the bnd workspace and not the Eclipse workspace. I now understand your question better … sorry if I sounded impatient … Kind regards, Peter Kriens > > Paul > > > On 10/06/2016 9:31 PM, Peter Kriens wrote: >> 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 <[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 >>> <https://mail.osgi.org/mailman/listinfo/osgi-dev> >> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] <mailto:[email protected]> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <https://mail.osgi.org/mailman/listinfo/osgi-dev> > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
