You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Nathan Beyer <nb...@kc.rr.com> on 2006/06/20 05:06:39 UTC
Eclipse Plug-in Dependencies not resolving
Is anyone else that's using Eclipse having trouble resolving the Plug-in
Dependencies? When I updated and rebuilt everything after the Swing/AWT code
was introduced none of the plug-in dependencies resolve any longer, so my
projects don't compile. I'm back to just manually adding all of the JARs
from the build to the project.
-Nathan
Re: Eclipse Plug-in Dependencies not resolving
Posted by Alex Blewitt <al...@gmail.com>.
I agree. One of my pet peeves was that Eclipse moved from a nice,
structured, parsable format in the form of XML to a bastardised text
format that uses ;name=value to attach parameters with weird syntax
(like the fact that leading whitespace is ignored and means line
continuation so you end up with trailing whitespace to separate the
Jars -- or in the OSGi's case, a comma). And technically, 72 chars is
the max length of a line, though in practice everyone seems to ignore
it.
Peter Kriens doesn't seem to like XML files, which might explain it:
http://www.osgi.org/blog/2006/04/maven.html
"How anybody can use XML for a human writeable/readable format escapes
me, but it has taken epidemic forms."
Perhaps because it doesn't suffer from the insane fragility that
Manifest.MF and Makefiles before them?
Alex.
On 21/06/06, Nathan Beyer <nb...@kc.rr.com> wrote:
> Was it just that the value of the Import-Package had a newline before the
> actual package names? I was just frustrated with myself that I couldn't
> figure it out.
>
> I like how OSGi uses the manifest, but manifest file format is the most
> fragile thing I've ever dealt with; one wrong whitespace or extra character
> and BOOM.
>
> -Nathan
>
> > -----Original Message-----
> > From: George Harley [mailto:george.c.harley@googlemail.com]
> > Sent: Tuesday, June 20, 2006 8:42 AM
> > To: harmony-dev@incubator.apache.org
> > Subject: Re: Eclipse Plug-in Dependencies not resolving
> >
> > Hi Tim,
> >
> > Thank you very much, it all works fine for me now. Hopefully things are
> > now fixed for Nathan (and everyone else) too.
> >
> > Best regards,
> > George
> >
> >
> > Tim Ellison wrote:
> > > I've been through and fixed the manifest and classpath files for the
> > > incoming Swing/AWT/Accessibility/Misc code (in repo > r415629).
> > >
> > > Regards,
> > > Tim
> > >
> > > George Harley wrote:
> > >
> > >> Hi Nathan,
> > >>
> > >> Yes, seeing this too. Suspect that the Swing and AWT manifests are
> > >> currently broken and that this is upsetting PDE. Perhaps things can be
> > >> temporarily solved for you by reverting your Eclipse PDE target to a
> > >> build prior to the Swing/AWT ? Assuming you have one lying around.
> > >>
> > >> Best regards,
> > >> George
> > >>
> > >>
> > >> Nathan Beyer wrote:
> > >>
> > >>> Is anyone else that's using Eclipse having trouble resolving the Plug-
> > in
> > >>> Dependencies? When I updated and rebuilt everything after the
> > >>> Swing/AWT code
> > >>> was introduced none of the plug-in dependencies resolve any longer, so
> > my
> > >>> projects don't compile. I'm back to just manually adding all of the
> > JARs
> > >>> from the build to the project.
> > >>>
> > >>>
> > >>>
> > >>> -Nathan
> > >>>
> > >>>
> > >>>
> > >>>
> > >> ---------------------------------------------------------------------
> > >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> > >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: Eclipse Plug-in Dependencies not resolving
Posted by Tim Ellison <t....@gmail.com>.
Nathan Beyer wrote:
> Was it just that the value of the Import-Package had a newline before the
> actual package names? I was just frustrated with myself that I couldn't
> figure it out.
Well originally I thought it was, but actually when I looked at the
manifest after Ant had put it into the JAR file, the new line after
Import had been removed (and all the crazy line wrapping conducted), so
that appears to be valid.
The real problem was that Swing was missing a required java.lang.ref as
an import, and AWT was not exporting it's org.apache.harmony.awt.*
packages that were being imported by Swing. This mean that Swing and
AWT would not resolve.
Since our bundles have cyclical dependencies, and Swing and AWT would
not resolve, therefore Beans (which requires AWT APIs), and Archive
(which requires Beans APIs), and LUNI (which requires Archive APIs), and
the rest of the world (that requires LUNI APIs) would also not resolve.
The house of cards came tumbling down, and unfortunately figuring out
the root cause in such cases is non-trivial with today's tools (I keep
moaning to the Eclipse PDE guys about it, and things are gradually
improving).
To find this problem I (temporarily) added the full JRE library onto AWT
build path so that it did not suffer from upstream resolution failures,
then could fix AWT and Swing, and then it all worked again.
> I like how OSGi uses the manifest, but manifest file format is the most
> fragile thing I've ever dealt with; one wrong whitespace or extra character
> and BOOM.
Yup -- and I think the tools could help better.
Regards,
Tim
--
Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
RE: Eclipse Plug-in Dependencies not resolving
Posted by Nathan Beyer <nb...@kc.rr.com>.
Was it just that the value of the Import-Package had a newline before the
actual package names? I was just frustrated with myself that I couldn't
figure it out.
I like how OSGi uses the manifest, but manifest file format is the most
fragile thing I've ever dealt with; one wrong whitespace or extra character
and BOOM.
-Nathan
> -----Original Message-----
> From: George Harley [mailto:george.c.harley@googlemail.com]
> Sent: Tuesday, June 20, 2006 8:42 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: Eclipse Plug-in Dependencies not resolving
>
> Hi Tim,
>
> Thank you very much, it all works fine for me now. Hopefully things are
> now fixed for Nathan (and everyone else) too.
>
> Best regards,
> George
>
>
> Tim Ellison wrote:
> > I've been through and fixed the manifest and classpath files for the
> > incoming Swing/AWT/Accessibility/Misc code (in repo > r415629).
> >
> > Regards,
> > Tim
> >
> > George Harley wrote:
> >
> >> Hi Nathan,
> >>
> >> Yes, seeing this too. Suspect that the Swing and AWT manifests are
> >> currently broken and that this is upsetting PDE. Perhaps things can be
> >> temporarily solved for you by reverting your Eclipse PDE target to a
> >> build prior to the Swing/AWT ? Assuming you have one lying around.
> >>
> >> Best regards,
> >> George
> >>
> >>
> >> Nathan Beyer wrote:
> >>
> >>> Is anyone else that's using Eclipse having trouble resolving the Plug-
> in
> >>> Dependencies? When I updated and rebuilt everything after the
> >>> Swing/AWT code
> >>> was introduced none of the plug-in dependencies resolve any longer, so
> my
> >>> projects don't compile. I'm back to just manually adding all of the
> JARs
> >>> from the build to the project.
> >>>
> >>>
> >>>
> >>> -Nathan
> >>>
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >>
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: Eclipse Plug-in Dependencies not resolving
Posted by George Harley <ge...@googlemail.com>.
Hi Tim,
Thank you very much, it all works fine for me now. Hopefully things are
now fixed for Nathan (and everyone else) too.
Best regards,
George
Tim Ellison wrote:
> I've been through and fixed the manifest and classpath files for the
> incoming Swing/AWT/Accessibility/Misc code (in repo > r415629).
>
> Regards,
> Tim
>
> George Harley wrote:
>
>> Hi Nathan,
>>
>> Yes, seeing this too. Suspect that the Swing and AWT manifests are
>> currently broken and that this is upsetting PDE. Perhaps things can be
>> temporarily solved for you by reverting your Eclipse PDE target to a
>> build prior to the Swing/AWT ? Assuming you have one lying around.
>>
>> Best regards,
>> George
>>
>>
>> Nathan Beyer wrote:
>>
>>> Is anyone else that's using Eclipse having trouble resolving the Plug-in
>>> Dependencies? When I updated and rebuilt everything after the
>>> Swing/AWT code
>>> was introduced none of the plug-in dependencies resolve any longer, so my
>>> projects don't compile. I'm back to just manually adding all of the JARs
>>> from the build to the project.
>>>
>>>
>>>
>>> -Nathan
>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>>
>>
>>
>
>
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: Eclipse Plug-in Dependencies not resolving
Posted by Tim Ellison <t....@gmail.com>.
I've been through and fixed the manifest and classpath files for the
incoming Swing/AWT/Accessibility/Misc code (in repo > r415629).
Regards,
Tim
George Harley wrote:
> Hi Nathan,
>
> Yes, seeing this too. Suspect that the Swing and AWT manifests are
> currently broken and that this is upsetting PDE. Perhaps things can be
> temporarily solved for you by reverting your Eclipse PDE target to a
> build prior to the Swing/AWT ? Assuming you have one lying around.
>
> Best regards,
> George
>
>
> Nathan Beyer wrote:
>> Is anyone else that's using Eclipse having trouble resolving the Plug-in
>> Dependencies? When I updated and rebuilt everything after the
>> Swing/AWT code
>> was introduced none of the plug-in dependencies resolve any longer, so my
>> projects don't compile. I'm back to just manually adding all of the JARs
>> from the build to the project.
>>
>>
>>
>> -Nathan
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>
--
Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: Eclipse Plug-in Dependencies not resolving
Posted by George Harley <ge...@googlemail.com>.
Hi Nathan,
Yes, seeing this too. Suspect that the Swing and AWT manifests are
currently broken and that this is upsetting PDE. Perhaps things can be
temporarily solved for you by reverting your Eclipse PDE target to a
build prior to the Swing/AWT ? Assuming you have one lying around.
Best regards,
George
Nathan Beyer wrote:
> Is anyone else that's using Eclipse having trouble resolving the Plug-in
> Dependencies? When I updated and rebuilt everything after the Swing/AWT code
> was introduced none of the plug-in dependencies resolve any longer, so my
> projects don't compile. I'm back to just manually adding all of the JARs
> from the build to the project.
>
>
>
> -Nathan
>
>
>
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org