> On 2 jun. 2016, at 13:11, Paul F Fraser <[email protected]> wrote: > So if you were working on osgi.enroute, osgi.enroute.bundles, > osgi.enroute.examples at the same time you would have 3 instances of eclipse > open? That is on a good day … I sometimes have 6 or 7 Eclipse’s open. Neil Bartlett’s MacBadge is my favorite piece of software of all times.
At €62 for 16 Gb RAM memory seems not an issue any more? That will give you at
least 20 workspaces simultaneously.
Kind regards,
Peter Kriens
>
> Paul
>
> On 2/06/2016 8:59 PM, Peter Kriens wrote:
>> I love this kind of feedback!
>>
>> Yes, in the bnd world a bnd workspace is like a module. It imports bundles
>> and it exports bundles from/to repositories. (Modules are a nice fractal
>> pattern.) A workspace should be cohesive to work well and for that reason
>> you should not mix it with other workspaces.
>>
>> I tried very hard to explain it clearly on the OSGi enRoute website,
>> especially the Eclipse workspace and bnd workspace. Any efforts to help me
>> to improve this are highly appreciated by me and your successors.
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>>
>>> On 2 jun. 2016, at 12:23, Paul F Fraser <
>>> <mailto:[email protected]>[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>> Hi Peter,
>>>
>>> Oh, Oh.
>>> I was trying to import the git repository as a general project.
>>> It has to be imported as an existing eclipse project...
>>>
>>> Am I correct in assuming that each of the EnRoute github repos,
>>> osgi.enroute, osgi.enroute.bundles etc., have to be in their own workspace
>>> when imported?
>>>
>>> I am trying to learn the process so I can get involved in feeding back some
>>> corrections to the site documentation in the form of pull requests rather
>>> than bug reports.
>>>
>>> I would also like to create some videos from an EnRoute newby aspect to
>>> help others avoid the heartache/terror I have experienced in taking on the
>>> task.
>>>
>>> Probably, I am suffering from playing around with bnd and bndtools from too
>>> far in the past. Google searches provide a horrible mess of OSGi and bnd
>>> knowledge and bad habits emerge.
>>>
>>> I have some more questions which I will carry to a new message.
>>>
>>> As they say, the only stupid questions are the ones that are not asked.
>>>
>>> Paul
>>>
>>> On 2/06/2016 6:53 PM, Peter Kriens wrote:
>>>> I think we tried to answer these questions on for example
>>>> http://enroute.osgi.org/qs/200-workspace.html
>>>> <http://enroute.osgi.org/qs/200-workspace.html>
>>>>
>>>> Could you take a look and indicate what you’re missing from there? Then I
>>>> can add the answer to this page so others can take advantage.
>>>>
>>>> Thanks. Kind regards,
>>>>
>>>> Peter Kriens
>>>>
>>>>
>>>>> On 2 jun. 2016, at 01:13, Paul F Fraser <[email protected]
>>>>> <mailto:[email protected]>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I clone osgi.enroute into my local git directory OK.
>>>>>
>>>>> I think I need a clean eclipse workspace dedicated to osgi.enroute and
>>>>> another clean workspace for osgi.enroute.bundles.
>>>>>
>>>>> If I have a new clean workspace, how do I set up the clean workspace to
>>>>> import the local git repo?
>>>>>
>>>>> If I preset the workspace to a new bnd osgi workspace how do I handle the
>>>>> imported cnf because I already have one?
>>>>>
>>>>> If I just import the local git repo to a clean workspace, how do I set up
>>>>> the bnd repositories in eclipse?
>>>>>
>>>>> Hope you follow what I am talking about :)
>>>>>
>>>>> 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] <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
