PDE build does not include correct versions of required plugins
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
PDE build does not include correct versions of required plugins
by kennywest
::
Rate this Message:
I am using Eclipse 3.3
I have the following plug-in structure: plugin/A plugin/B plugin/C A is actually a product. The product configuration is based on plug-ins. The A.product file lists all required plug-ins for A, B and C. B is using a custom version of the databinding framework (most recent SVN trunk). So, B lists the following required bundles in its MANIFEST.MF: ... org.eclipse.core.databinding;bundle-version="1.3.0", org.eclipse.core.databinding.beans;bundle-version="1.3.0", org.eclipse.jface.databinding;bundle-version="1.3.0" ... Running the product from Eclipse IDE resolves the correct databinding framework. When building the application using PDE build + Maven, the databinding plug-ins that ship with 3.3 are copied to the .zip file. If I remove the original versions from eclipse/plugin directory, of course, my versions are copied to the .zip file. This is rather annoying, since I am not the only developer on this project :) How can I tell PDE build to copy a specific version of the databinding plug-ins to the resulting .zip file? Thanks. |
|||||||||||
|
|
Re: PDE build does not include correct versions of required plugins
by Your Friendly WTP Builder
::
Rate this Message:
Perhaps related to Bug 203270 - Problems with qualifier substitution and bundle look-up? https://bugs.eclipse.org/bugs/show_bug.cgi?id=203270 Which was worked around by including the qualifier in the feature.xml.
I am using Eclipse 3.3 I have the following plug-in structure: plugin/A plugin/B plugin/C A is actually a product. The product configuration is based on plug-ins. The A.product file lists all required plug-ins for A, B and C. B is using a custom version of the databinding framework (most recent SVN trunk). So, B lists the following required bundles in its MANIFEST.MF: ... org.eclipse.core.databinding;bundle-version="1.3.0", org.eclipse.core.databinding.beans;bundle-version="1.3.0", org.eclipse.jface.databinding;bundle-version="1.3.0" ... Running the product from Eclipse IDE resolves the correct databinding framework. When building the application using PDE build + Maven, the databinding plug-ins that ship with 3.3 are copied to the .zip file. If I remove the original versions from eclipse/plugin directory, of course, my versions are copied to the .zip file. This is rather annoying, since I am not the only developer on this project :) How can I tell PDE build to copy a specific version of the databinding plug-ins to the resulting .zip file? Thanks. -- View this message in context: http://www.nabble.com/PDE-build-does-not-include-correct-versions-of-required-plugins-tf4555419.html#a13000758 Sent from the Eclipse PDE - build mailing list archive at Nabble.com. _______________________________________________ pde-build-dev mailing list pde-build-dev@... https://dev.eclipse.org/mailman/listinfo/pde-build-dev _______________________________________________ pde-build-dev mailing list pde-build-dev@... https://dev.eclipse.org/mailman/listinfo/pde-build-dev |
|||||||||||
|
|
Re: PDE build does not include correct versions of required plugins
by kennywest
::
Rate this Message:
Thank you for your reply.
My "product configuration" is based on plug-ins, instead of features. So the feature.xml is generated by PDE build, I assume. If I open the feature.xml, all versions are 0.0.0. Any possibilities to let PDE build generate a feature.xml containing the correct versions?
|
|||||||||||
|
|
Re: PDE build does not include correct versions of required plugins
by portal on behalf of Andrew Niefer
::
Rate this Message:
That bug (203270) would be slightly more specific than Ken's case. It is about when the feature specifies a version like 3.2.1.qualifier and pde.build chooses something like 3.2.2 Ken, the .product file does not currently support specifying versions, and the code that generates the feature does not have a way to specify them either. The only way to do this would be to make your own features and base your .product file on features instead. However, if you want to stay with a plugin based product, it would be possible to modify the generated feature before build scripts are generated. Using either a preFetch or preGenerate customTarget you could actually use pde.build's eclipse.idReplacer task to modify the version numbers in the generated feature. Something like: <eclipse.idReplacer featureFilePath="${buildDirectory}/features/org.eclipse.pde.build.container.feature/feature.xml" selfVersion="1.0.0" featureIds="" pluginIds="org.eclipse.core.databinding:0.0.0,1.3.0.qualifier,org.eclipse.jface.databinding:0.0.0,1.3.0.qualifier,"/> The pluginIds specifies the plugin, the current version in the feature.xml and the version to replace it with. Note however there are 2 bugs that might cause you problems here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=198536 : Inifinite Loop : Rare in this case, depends on how your VM does HashMaps. Exists in 3.3.0, fixed in 3.3.1 https://bugs.eclipse.org/bugs/show_bug.cgi?id=205230: NPE : You will hit this unless you replace versions of every plugin listed in the feature. Does not exist in 3.3.0, occurs in 3.3.1 I would suggest using the 3.3.0 pde.build unless the infinite loop is a problem for you. -Andrew
Thank you for your reply. My "product configuration" is based on plug-ins, instead of features. So the feature.xml is generated by PDE build, I assume. If I open the feature.xml, all versions are 0.0.0. Any possibilities to let PDE build generate a feature.xml containing the correct versions? David M Williams wrote: > > Perhaps related to Bug 203270 - Problems with qualifier substitution and > bundle look-up? > https://bugs.eclipse.org/bugs/show_bug.cgi?id=203270 > Which was worked around by including the qualifier in the feature.xml. > -- View this message in context: http://www.nabble.com/PDE-build-does-not-include-correct-versions-of-required-plugins-tf4555419.html#a13034798 Sent from the Eclipse PDE - build mailing list archive at Nabble.com. _______________________________________________ pde-build-dev mailing list pde-build-dev@... https://dev.eclipse.org/mailman/listinfo/pde-build-dev _______________________________________________ pde-build-dev mailing list pde-build-dev@... https://dev.eclipse.org/mailman/listinfo/pde-build-dev |
| Free embeddable forum powered by Nabble | Forum Help |
