I can do everything from the eclipse 3.3.2 version, I am not that concern with RCP.
What is the new post link you will create? On Sat, May 3, 2008 at 3:57 AM, Steinar Bang <[EMAIL PROTECTED]> wrote: > >>>>> Steinar Bang <[EMAIL PROTECTED]>: > > >>>>> Steinar Bang <[EMAIL PROTECTED]>: > >> The problem with that, is that I can't find anything that looks like a > >> PDE build logfile within the pde-maven-plugin project. Does anyone > >> know where it's supposed to reside? > > > I've found the logfile, in the eclipse/configuration/ directory, but I > > don't know what to make of it. > > > - First error: unable to create config file in the configuration > > directory (ie. the directory where the log file resides, so there > > cannot be writing privilege problems. What config file? config.ini? > > There already is one in this directory that came from the 3.3.2 SDK) > > > - Second error: unable to resolve the bundle org.eclipse.core.jobs > > (there is an org.eclipse.core.jobs_3.3.1.R33x_v20070709.jar in the > > eclipse/plugins/ directory) > [snip!] > > I still don't know what to make of it, but I've experimented with > starting the eclipse installation used by pde-maven-plugin, and it > failed to start, and gave the same kind of error log (or almost), in the > eclipse/configuration directory. > > The eclipse installation consists of the eclipse SDK, with the GEF SDK, > and some WTP SDK zip files unzipped over it. On top of that comes some > of our own OSGi bundles, built with the apache felix > maven-bundle-plugin, and finally some directory bundles containing third > party software. > > And it's those directory bundles that are the problem. If I remove them > all, the eclipse installation will start. > > I haven't been able to track it down closer than that. > > The directory bundles are very simple, a directory, with a META-INF > directory, containing a MANIFEST.MF, with a bundle-version, a > bundle-symbolic-name, a bundle-classpath, and export-package of the > packages that are to be exported. No activator. > > I thought maybe the missing activator was the problem. But there are > other directory bundles following the same pattern, that has no problem. > > I've tried to spot a difference between them, and the problem packages, > but so far have been unsuccessful. > > Second theory: could it be related to some of the exported packages? > This worked with eclipse 3.2.2. The thirdparty bundles wrap some of > apache commons libraries. Could a difference between eclipse 3.2.2 and > 3.3.2, be that some of these libraries are included, and there is a > package conflict? > > Hm... this is quickly getting more eclipse RCP and equinox-related, than > pde-maven-plugin related, so I guess I should move this to a different > forum. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
