Hi Hasan, Bramwell, Hasan M. a écrit : > I have successfully developed a Java Component using your excellent Eclipse > plugin, but I had several frustrations with it. These may be dealt with in > documentation I haven't yet found or they may be design flaws, I don't know.
Thanks for using the Eclipse plugin. You will find a better version (thought not released yet) here: http://cedric.bosdonnat.free.fr/ooeclipseintegration_site.zip + It's easier to add UNO services (and get them registered) + The UNO project build is more reliable (and the configuration is defined in a .unoproject file) This file is an archived Eclipse update site: you will use it the same way than a remote update site in Eclipse. However, the version numbers of the plugin may not have been changed and you may have to uninstall the previous plugins before to install this one. > The difficulty I had was not with initial use, but with subsequent use after > I had created a fairly complicated set of attributes and methods. I could > see no way to regenerate all the artifacts without recreating the whole > project! Is this really necessary? First, what do you call artifacts exactly ? There are build problems which have been fixed in the update site mentionned in the previous lines. > If I manually edit an idl file, how do I force regeneration of the other > artifacts? If you manually edit an idl file the types.rdb and the .class files are regenerated. However if you have added a property in one of your interfaces, you'll have to add it in the implementation class "at hand". In fact, Eclipse will tell you that there are unimplemented methods and then a quickfix will add the methods skeleton for you. Please do not hesitate to report any other problem on the Eclipse plugin. Regards, Cedric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
