Community
Participate
Working Groups
After adding Help to a working rcp application I get errors. When I select lucene 2.9.1 instead of lucene 3.5.0 in Run Configurations > Plugins the application works in eclipse. However, the exported application does not work, because lucene 3.5 gets exported.
Can you provide some simple steps for me to reproduce? Do you have a product configuration file? Changing something in the run configuration has no effect on your exported application.
Closing due to lack of info. Please reopen if you can answer my previous questions.
I would like to re-open this bug because I see the same problem under 4.2.2: I have an RCP application that runs under 4.2.2 using the compatibility layer. When I open my *.product file, press "Synchronize" and "Launch an Eclipse application", the help system does not start because it requires org.apache.lucene and org.apache.lucene.analysis version 2.9.1, but the launch configuration adds lucene plugins with version 3.5.0. I can adjust the Run Configuration in the IDE: Select the 2.9.1 lucene plugins, and the RCP app will start. But whenever I "Synchronize", or when I "export" the product from the IDE, this results in Eclipse trying to use the 3.5.0 version of the lucene plugins. My product is based on features, and in one feature I explicitly listed <plugin id="org.apache.lucene" download-size="0" install-size="0" version="2.9.1.v201101211721" unpack="false"/> <plugin id="org.apache.lucene.analysis" download-size="0" install-size="0" version="2.9.1.v201101211721" unpack="false"/> No difference, the "Synchronize" step will still create a run configuration with lucene 3.5.0 plugins, and then the help.base plugin fails to load.
Reopening. I don't have time to investigate this further right now. Perhaps another plug-in requires the newer version of Lucene or somewhere the dependency only has a lower bound.
(In reply to comment #3) > But whenever I "Synchronize", or when I "export" the product from the IDE Tried again: The "Export" works. It picks lucene plugin versions 2.9.1.v201101211721 as explicitly requested in my feature.xml. The "Synchronize" & "Launch.." inside the IDE picks some version 3.5.0 plugins. After manually adjusting the Run Configuration to only use 2.9.1, it's OK. So this is limited to the IDE Synchronize/Launch. Seems to be less picky than the "export" or headless build. Usually, during development, that's good: While the "export" or headless build fails unless all plugins are perfectly resolved, the product still starts up in the IDE. In this case, the IDE second-guessig what I put in the feature.xml is not helpful. But not fatal, either: Can adjust the run configuration, and the 'export' works fine.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
