:-) Yes, you are right, but anyway in some cases I would be nice to have this feature available. When I use eclipse PDE tools it helps me to avoid to copy the jar files back and forth from one repo and perform quick fixes without switching from a workpsace to another.
In any case the solution for the problem about a CI build is to generate the jar files of these ‘foreign’ projects into the cnf directory instead of generating them inside the project folder. I think that it should be left to the developer to decide how to arrange its own projects. The developer knowing the limitations of his setup knows also how use it in the right way. Thanks BJ, for your answer. N. Da: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] Per conto di BJ Hargrave Inviato: lunedì 22 agosto 2016 16:26 A: osgi-dev@mail.osgi.org Oggetto: Re: [osgi-dev] R: R: Import in the same Eclipse workspacve bnd projects from different filesystem locations Well, all things are possible in programming :-) But as you note, we need fidelity with non-Eclipse usage like gradle, ant, etc. And they cannot depend upon decoding Eclipse metadata (which is not API) to figure out where on the file system all the projects in the bnd workspace are located. How would this possibly translate to a CI build where there is nothing other than the git repo? Basically you need to think that one bnd workspace == one git repo == one Eclipse workspace. -- BJ Hargrave Senior Technical Staff Member, IBM // office: +1 386 848 1781 OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 hargr...@us.ibm.com<mailto:hargr...@us.ibm.com> ----- Original message ----- From: Portinaro Nicola <nicola.portin...@telecomitalia.it<mailto:nicola.portin...@telecomitalia.it>> Sent by: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>> Cc: Subject: [osgi-dev] R: R: Import in the same Eclipse workspacve bnd projects from different filesystem locations Date: Mon, Aug 22, 2016 10:14 AM Clear, but I supposed that bnd could be instructed by bndtools about the location of the projects to build and of the cnf one. Why not? Of course this would not be possible if you build with gradle. In this case the only possibility would be to pass to gradle the location of the eclipse workspace in order to know the location of the projects. I guess that location of the projects is somewhere in the .metadata directory. N. Da: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> [mailto:osgi-dev-boun...@mail.osgi.org] Per conto di BJ Hargrave Inviato: lunedì 22 agosto 2016 15:25 A: osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> Oggetto: Re: [osgi-dev] R: Import in the same Eclipse workspacve bnd projects from different filesystem locations You can't do that. All the bnd projects must be in the same file system folder as the cnf folder. They all can be in a different folder than the Eclipse workspace folder but you cannot split bnd projects across file system folders. Remember Bndtools is a set of Eclipse plugins which use Bnd to build bundle projects. Bnd knows nothing about Eclipse and Eclipse workspaces. It only knows about the file system. So it Bnd does not know how you may have logically arranged projects in an Eclipse workspace. Bnd only cares about how things are arranged on the file system. -- BJ Hargrave Senior Technical Staff Member, IBM // office: +1 386 848 1781 OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 hargr...@us.ibm.com<mailto:hargr...@us.ibm.com> ----- Original message ----- From: Portinaro Nicola <nicola.portin...@telecomitalia.it<mailto:nicola.portin...@telecomitalia.it>> Sent by: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>> Cc: Subject: [osgi-dev] R: Import in the same Eclipse workspacve bnd projects from different filesystem locations Date: Mon, Aug 22, 2016 9:05 AM Hi BJ, Consider this example. I have git workspace repo1 with cnf and project1 bnd projects Then I have a second git repo with cnf and project2 bnd projects. I create an eclipse workspace and I import (not copy): - From repo1 the cnf and project1 bndtoos projects - From repo2 project2 I can see all the projects in my Eclipse workspace but bndtools do not show project2 in the Workspace repository and therefore it is not possible to add it in the bndrun configuration because it is simply not listed in the browse repos listbox. Moreover bndtools doesn’t build it (If I delete any jar file present in project2/generated folder, it is not generated anymore). N. Da: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> [mailto:osgi-dev-boun...@mail.osgi.org] Per conto di BJ Hargrave Inviato: lunedì 22 agosto 2016 14:10 A: osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> Oggetto: Re: [osgi-dev] Import in the same Eclipse workspacve bnd projects from different filesystem locations Yes. The git repo holding your project can be in a different folder than the eclipse workspace. -- BJ Hargrave Senior Technical Staff Member, IBM // office: +1 386 848 1781 OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 hargr...@us.ibm.com<mailto:hargr...@us.ibm.com> ----- Original message ----- From: Portinaro Nicola <nicola.portin...@telecomitalia.it<mailto:nicola.portin...@telecomitalia.it>> Sent by: osgi-dev-boun...@mail.osgi.org<mailto:osgi-dev-boun...@mail.osgi.org> To: "osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>" <osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org>> Cc: Subject: [osgi-dev] Import in the same Eclipse workspacve bnd projects from different filesystem locations Date: Mon, Aug 22, 2016 5:30 AM Hi, Eclipse PDE tools allows to import in a workspace (without copy them), projects from different filesystem locations. Is this use case supported in some way by the EnRoute/Bndtools toolchain? Thanks in advance, N. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
