| Access restrictions [message #251765] |
Sat, 01 March 2008 21:08  |
Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Hi,
I have weird access restriction errors in my workspace that I can't
understand nor cure.
Say I have 3 plugin projects in my ws:
- o.e.libs (several contained jars on the bundle classpath, all packages
exported in manifest.mf)
- o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
- o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
Now I get aceess restriction build errors in the o.e.bundle2 for classes
in the o.e.libs bundle although the respective packages are properly
exported.
The o.e.bundle1 doesn't seem to have a problem with using the same
classes from the o.e.libs bundle.
I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
Does anybody have an idea and can give me a hint on what else to try?
Cheers
/Eike
|
|
|
| Re: Access restrictions [message #251769 is a reply to message #251765] |
Sat, 01 March 2008 21:17  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Eike,
It's more of a PDE question than a JDT question. Does invoking PDE
Tools->Update Classpath... on the project help? If you remove bundle2's
dependencies on o.e.libs, does that make a difference (given that it
depends on bundle1, which reexports them anyway). Does the problem
appear to be new to this I build?
Eike Stepper wrote:
> Hi,
>
> I have weird access restriction errors in my workspace that I can't
> understand nor cure.
> Say I have 3 plugin projects in my ws:
>
> - o.e.libs (several contained jars on the bundle classpath, all
> packages exported in manifest.mf)
> - o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
> - o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
>
> Now I get aceess restriction build errors in the o.e.bundle2 for
> classes in the o.e.libs bundle although the respective packages are
> properly exported.
> The o.e.bundle1 doesn't seem to have a problem with using the same
> classes from the o.e.libs bundle.
>
> I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
>
> Does anybody have an idea and can give me a hint on what else to try?
>
> Cheers
> /Eike
|
|
|
| Re: Access restrictions [message #251773 is a reply to message #251769] |
Sat, 01 March 2008 21:38 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Ed,
I know that this question is related with PDE but the error message is
configurable through the JDT compiler settings on the project, so I
guess it's somehow related with the both of them. May be the kind PDE
uses JDT. BTW. I couldn't find a PDE newsgroup...
More comments below...
Ed Merks schrieb:
> Eike,
>
> It's more of a PDE question than a JDT question. Does invoking PDE
> Tools->Update Classpath... on the project help?
No, I tried the following:
- update all classpaths
- delete the prjects from the ws and reimport them (to clear JDT/PDE state)
- used a fresh ws
- purged the configuration folder
No influence ;-(
> If you remove bundle2's dependencies on o.e.libs, does that make a
> difference (given that it depends on bundle1, which reexports them
> anyway).
No difference.
> Does the problem appear to be new to this I build?
Not really. It was the same in M5.
Unfortunately I can't say exactly what actually happened so that the
errors resulted. The defendants are the new HibernateStore plugins for
CDO. The story is:
1) My ws was ok.
2) Martin updated his ws and had build errors. He rearranged the bundle
classpaths, mainly by importing packages instead of requiring bundles.
Seemed to work for him.
3) When I updated my ws with Martins changes I got the same errors
although it worked for him. I rearranged the bundle classpaths and now
nothing works for me. Neither Import-Package nor Require-Bundle
Since we're currrently testing in standalone mode I found out that I can
switch off the error messages in the JDT compiler properties and
everything runs properly. But that's of course unsatisfying.
Weird story. I have no more ideas...
Cheers
/Eike
>
>
> Eike Stepper wrote:
>> Hi,
>>
>> I have weird access restriction errors in my workspace that I can't
>> understand nor cure.
>> Say I have 3 plugin projects in my ws:
>>
>> - o.e.libs (several contained jars on the bundle classpath, all
>> packages exported in manifest.mf)
>> - o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
>> - o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
>>
>> Now I get aceess restriction build errors in the o.e.bundle2 for
>> classes in the o.e.libs bundle although the respective packages are
>> properly exported.
>> The o.e.bundle1 doesn't seem to have a problem with using the same
>> classes from the o.e.libs bundle.
>>
>> I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
>>
>> Does anybody have an idea and can give me a hint on what else to try?
>>
>> Cheers
>> /Eike
|
|
|
| Re: Access restrictions [message #251785 is a reply to message #251769] |
Sat, 01 March 2008 21:44 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
This is a multi-part message in MIME format.
--------------030508060605050909030803
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Here is the error:<br>
<br>
<img src="cid:part1.05040703.06050406@sympedia.de" alt=""><br>
<br>
Although the package com.mysql.jdbc is exported and JDT doesn't show
restrictions on the java build path page:<br>
<br>
<img src="cid:part2.04020602.05040507@sympedia.de" alt=""><br>
<br>
Cheers<br>
/Eike<br>
<br>
<br>
Ed Merks schrieb:
<blockquote cite="mid:fqch5n$q4k$1@build.eclipse.org" type="cite">Eike,
<br>
<br>
It's more of a PDE question than a JDT question.
|
|
|
| Re: Access restrictions [message #251795 is a reply to message #251785] |
Sun, 02 March 2008 11:52 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------070205090604080306060202
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Eike,
Perhaps a bug was introduced. This didn't happen until you moved to the
latest I-Build? If it is a new bug, a bugzilla to reproduce it would be
a good thing...
Eike Stepper wrote:
> Here is the error:
>
>
>
> Although the package com.mysql.jdbc is exported and JDT doesn't show
> restrictions on the java build path page:
>
>
>
> Cheers
> /Eike
>
>
> Ed Merks schrieb:
>> Eike,
>>
>> It's more of a PDE question than a JDT question. Does invoking PDE
>> Tools->Update Classpath... on the project help? If you remove
>> bundle2's dependencies on o.e.libs, does that make a difference
>> (given that it depends on bundle1, which reexports them anyway).
>> Does the problem appear to be new to this I build?
>>
>>
>> Eike Stepper wrote:
>>> Hi,
>>>
>>> I have weird access restriction errors in my workspace that I can't
>>> understand nor cure.
>>> Say I have 3 plugin projects in my ws:
>>>
>>> - o.e.libs (several contained jars on the bundle classpath, all
>>> packages exported in manifest.mf)
>>> - o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
>>> - o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
>>>
>>> Now I get aceess restriction build errors in the o.e.bundle2 for
>>> classes in the o.e.libs bundle although the respective packages are
>>> properly exported.
>>> The o.e.bundle1 doesn't seem to have a problem with using the same
>>> classes from the o.e.libs bundle.
>>>
>>> I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
>>>
>>> Does anybody have an idea and can give me a hint on what else to try?
>>>
>>> Cheers
>>> /Eike
--------------070205090604080306060202
Content-Type: multipart/related;
boundary="------------080305080809060109050302"
--------------080305080809060109050302
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eike,<br>
<br>
Perhaps a bug was introduced.
|
|
|
| Re: Access restrictions [message #251821 is a reply to message #251795] |
Mon, 03 March 2008 09:52 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
This is a multi-part message in MIME format.
--------------030508010800090305040808
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Ed Merks schrieb:
> Eike,
>
> Perhaps a bug was introduced. This didn't happen until you moved to
> the latest I-Build? If it is a new bug, a bugzilla to reproduce it
> would be a good thing...
I double checked: it makes no difference whether I use M5 or latest
I-build. It must be something that we have caused but we have no idea
what it is. Everything looks correct for our sorely afflicted eyes ;-(
I'm just about to restructure the setup a bit (split server and client)
so that the problem is easier to reproduce. May be someone would like
have a look then...
Cheers
/Eike
>
>
> Eike Stepper wrote:
>> Here is the error:
>>
>>
>>
>> Although the package com.mysql.jdbc is exported and JDT doesn't show
>> restrictions on the java build path page:
>>
>>
>>
>> Cheers
>> /Eike
>>
>>
>> Ed Merks schrieb:
>>> Eike,
>>>
>>> It's more of a PDE question than a JDT question. Does invoking PDE
>>> Tools->Update Classpath... on the project help? If you remove
>>> bundle2's dependencies on o.e.libs, does that make a difference
>>> (given that it depends on bundle1, which reexports them anyway).
>>> Does the problem appear to be new to this I build?
>>>
>>>
>>> Eike Stepper wrote:
>>>> Hi,
>>>>
>>>> I have weird access restriction errors in my workspace that I can't
>>>> understand nor cure.
>>>> Say I have 3 plugin projects in my ws:
>>>>
>>>> - o.e.libs (several contained jars on the bundle classpath, all
>>>> packages exported in manifest.mf)
>>>> - o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
>>>> - o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
>>>>
>>>> Now I get aceess restriction build errors in the o.e.bundle2 for
>>>> classes in the o.e.libs bundle although the respective packages are
>>>> properly exported.
>>>> The o.e.bundle1 doesn't seem to have a problem with using the same
>>>> classes from the o.e.libs bundle.
>>>>
>>>> I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
>>>>
>>>> Does anybody have an idea and can give me a hint on what else to try?
>>>>
>>>> Cheers
>>>> /Eike
>
--------------030508010800090305040808
Content-Type: multipart/related;
boundary="------------070701090807080309010606"
--------------070701090807080309010606
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ed Merks schrieb:
<blockquote cite="mid:fqe4f8$hmd$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
Eike,<br>
<br>
Perhaps a bug was introduced.
|
|
|
| Re: Access restrictions [message #251825 is a reply to message #251821] |
Mon, 03 March 2008 12:23 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------070607090205000206090308
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Eike,
If you care to send me the zip files that I can use to reproduce this
problem, I'll be happy to have a look myself if there's something I can
spot...
Eike Stepper wrote:
> Ed Merks schrieb:
>> Eike,
>>
>> Perhaps a bug was introduced. This didn't happen until you moved to
>> the latest I-Build? If it is a new bug, a bugzilla to reproduce it
>> would be a good thing...
> I double checked: it makes no difference whether I use M5 or latest
> I-build. It must be something that we have caused but we have no idea
> what it is. Everything looks correct for our sorely afflicted eyes ;-(
> I'm just about to restructure the setup a bit (split server and
> client) so that the problem is easier to reproduce. May be someone
> would like have a look then...
>
> Cheers
> /Eike
>
>
>>
>>
>> Eike Stepper wrote:
>>> Here is the error:
>>>
>>>
>>>
>>> Although the package com.mysql.jdbc is exported and JDT doesn't show
>>> restrictions on the java build path page:
>>>
>>>
>>>
>>> Cheers
>>> /Eike
>>>
>>>
>>> Ed Merks schrieb:
>>>> Eike,
>>>>
>>>> It's more of a PDE question than a JDT question. Does invoking PDE
>>>> Tools->Update Classpath... on the project help? If you remove
>>>> bundle2's dependencies on o.e.libs, does that make a difference
>>>> (given that it depends on bundle1, which reexports them anyway).
>>>> Does the problem appear to be new to this I build?
>>>>
>>>>
>>>> Eike Stepper wrote:
>>>>> Hi,
>>>>>
>>>>> I have weird access restriction errors in my workspace that I
>>>>> can't understand nor cure.
>>>>> Say I have 3 plugin projects in my ws:
>>>>>
>>>>> - o.e.libs (several contained jars on the bundle classpath, all
>>>>> packages exported in manifest.mf)
>>>>> - o.e.bundle1 (with Require-Bundle on o.e.libs, reexported)
>>>>> - o.e.bundle2 (with Require-Bundle on o.e.libs and o.e.bundle1)
>>>>>
>>>>> Now I get aceess restriction build errors in the o.e.bundle2 for
>>>>> classes in the o.e.libs bundle although the respective packages
>>>>> are properly exported.
>>>>> The o.e.bundle1 doesn't seem to have a problem with using the same
>>>>> classes from the o.e.libs bundle.
>>>>>
>>>>> I'm working with the latest Eclipse 3.4 I-build (Feb 27th).
>>>>>
>>>>> Does anybody have an idea and can give me a hint on what else to try?
>>>>>
>>>>> Cheers
>>>>> /Eike
>>
--------------070607090205000206090308
Content-Type: multipart/related;
boundary="------------070005080302030300070806"
--------------070005080302030300070806
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eike,<br>
<br>
If you care to send me the zip files that I can use to reproduce this
problem, I'll be happy to have a look myself if there's something I can
spot...<br>
<br>
<br>
Eike Stepper wrote:
<blockquote cite="mid:fqghpi$d4j$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
Ed Merks schrieb:
<blockquote cite="mid:fqe4f8$hmd$1@build.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
Eike,<br>
<br>
Perhaps a bug was introduced.
|
|
|
| Re: Access restrictions [message #251836 is a reply to message #251825] |
Mon, 03 March 2008 16:00 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Ed Merks schrieb:
> Eike,
>
> If you care to send me the zip files that I can use to reproduce this
> problem, I'll be happy to have a look myself if there's something I
> can spot...
That's great!!! The email is just going out. I hope you can receive the
12MB attachment ;-)
I'm sending it to your email address because it contains non EPL jars...
Cheers
/Eike
|
|
|
Powered by
FUDForum. Page generated in 0.03844 seconds
] 
Search
Help
Register
Login
Home
