|
|
|
|
|
|
|
|
|
|
Re: Error exporting product in eclipse 3.2 rc2 [message #448831 is a reply to message #448827] |
Thu, 04 May 2006 03:41  |
Eclipse User |
|
|
|
Hi Paul,
Thanks a lot mentioning other threads that ware very usefull to find my
mistake.
Based in you references I genereted the ant build and sow that since I had
the sources from org.eclipse.ui in my workspace, instand using the jar from
target when the hiperbola project was loaded it used the sources cheked out
in my workspace from cvs to test fragments in my locale pt-BR. When I
generated the ant bild using pde tools it easy too see that the classpath to
ui is from a project and not from a plugin. Even when you chage in louncher
to use the plugins from target, you need to close the project (I dont know
if it was this way before) when you delete and add ui dependencies again ,
couse if not when you try to in list apears the project (it is decoretade
with a gold circle).
Thanks again Paul
Ry Paul,
Thanks a lot about you coments
"Paul Webster" <pwebster@ca.ibm.com> wrote in message
news:e3b7mn$7o8$1@utils.eclipse.org...
> IIRC, there was another thread on this recently. It really depends on
> how you export and run your RCP app.
>
> If you are exporting from 3.1.2 and then just move into 3.2, you have to
> make sure that your product export includes all of the new lower level
> plugins ... org.eclipse.core functionality was spread out, and your list
> of plugins for your RCP app must increase accordingly. ex: go to your
> launch config, deselect all, select your main RCP plugin(s), and add
> required plugins. Then compare that list with what your product is
> trying to export.
>
> Another problem I think that was mentioned in a thread recently was that
> an export that included a "New plugin from JAR archives" would fail, but
> the corresponding ant-based export script would work.
>
> Later,
> PW
|
|
|
Powered by
FUDForum. Page generated in 0.05492 seconds