.classpath in R13.07

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

.classpath in R13.07

Jacques Le Roux
Administrator
Hi,

Since we removed all but ecommerce component in R13.07, Eclipse complains about missing libs in its classpath.
I wanted to comment out all references to them in .classpath
On the other hand it's not blocking. Just annoying when you lauch debug with the infamous exotic message "Errors exist in requred project".
So if I comment out ,when people will add the components they need from trunk, they will have to uncomment.

Between these 2 minors points, which one do you prefer?

Jacques
Reply | Threaded
Open this post in threaded view
|

Re: .classpath in R13.07

Jacques Le Roux
Administrator
Any opinions?

Jacques


On Tuesday, December 10, 2013 9:11 AM Jacques Le Roux <[hidden email]> wrote:

> Hi,
>
> Since we removed all but ecommerce component in R13.07, Eclipse complains about missing libs in its classpath.
> I wanted to comment out all references to them in .classpath
> On the other hand it's not blocking. Just annoying when you lauch debug with the infamous exotic message "Errors exist in requred
> project". So if I comment out ,when people will add the components they need from trunk, they will have to uncomment.
>
> Between these 2 minors points, which one do you prefer?
>
> Jacques
Reply | Threaded
Open this post in threaded view
|

Re: .classpath in R13.07

Jacopo Cappellato-4
I'd remove or comment out them.

Jacopo

On Dec 11, 2013, at 8:37 PM, Jacques Le Roux <[hidden email]> wrote:

> Any opinions?
>
> Jacques
>
>
> On Tuesday, December 10, 2013 9:11 AM Jacques Le Roux <[hidden email]> wrote:
>> Hi,
>>
>> Since we removed all but ecommerce component in R13.07, Eclipse complains about missing libs in its classpath.
>> I wanted to comment out all references to them in .classpath
>> On the other hand it's not blocking. Just annoying when you lauch debug with the infamous exotic message "Errors exist in requred
>> project". So if I comment out ,when people will add the components they need from trunk, they will have to uncomment.
>>
>> Between these 2 minors points, which one do you prefer?
>>
>> Jacques

Reply | Threaded
Open this post in threaded view
|

Re: .classpath in R13.07

Jacques Le Roux
Administrator
Done at revision: 1550399  

Jacques

On Thursday, December 12, 2013 8:30 AM Jacopo Cappellato <[hidden email]> wrote:

> I'd remove or comment out them.
>
> Jacopo
>
> On Dec 11, 2013, at 8:37 PM, Jacques Le Roux <[hidden email]> wrote:
>
>> Any opinions?
>>
>> Jacques
>>
>>
>> On Tuesday, December 10, 2013 9:11 AM Jacques Le Roux <[hidden email]> wrote:
>>> Hi,
>>>
>>> Since we removed all but ecommerce component in R13.07, Eclipse complains about missing libs in its classpath.
>>> I wanted to comment out all references to them in .classpath
>>> On the other hand it's not blocking. Just annoying when you lauch debug with the infamous exotic message "Errors exist in
>>> requred project". So if I comment out ,when people will add the components they need from trunk, they will have to uncomment.
>>>
>>> Between these 2 minors points, which one do you prefer?
>>>
>>> Jacques