Eclipse Community Forums: Plugin Development Environment (PDE) » 'Export Features'

Home » Eclipse Projects » Plugin Development Environment (PDE) » 'Export Features' - Unable to find: Installable Unit

Show: Today's Messages :: Show Polls :: Message Navigator

'Export Features' - Unable to find: Installable Unit [message #637498]

Fri, 05 November 2010 20:40

Mirko Raner

Messages: 125
Registered: July 2009
Location: New York City, NY

Senior Member

We have trouble exporting a feature that previously used to export without any problems. Now, when we use Export... -> Deployable features, we get this error message:

'Export Features' has encountered a problem:
/Users/mraner/Perforce/mraner_mac/sdtax/te/tpe/incubator/Xte xt/thx-helptext/com.intuit.eclipse.xtext.thx-feature/assembl e.com.intuit.eclipse.xtext.thx.group.group.group.xml:88: The following error occurred while executing this line:
/Users/mraner/Perforce/mraner_mac/sdtax/te/tpe/incubator/Xte xt/thx-helptext/com.intuit.eclipse.xtext.thx-feature/assembl e.com.intuit.eclipse.xtext.thx.group.group.group.xml:179: Unable to find: Installable Unit [ id=com.intuit.eclipse.xtext.thx version=1.0.0.r0002 ]
The following error occurred while executing this line:
/Users/mraner/Perforce/mraner_mac/sdtax/te/tpe/incubator/Xte xt/thx-helptext/com.intuit.eclipse.xtext.thx-feature/assembl e.com.intuit.eclipse.xtext.thx.group.group.group.xml:179: Unable to find: Installable Unit [ id=com.intuit.eclipse.xtext.thx version=1.0.0.r0002 ]

The problem happens in the p2.mirror task inside the mirrorArchive target. When we turn off the "Generate metadata repository" option the plugins and features folders are exported properly (but we obviously don't get a complete update site). When we remove the offending com.intuit.eclipse.xtext.thx plug-in from the feature, the export succeeds. Apparently, there is something wrong with that particular plug-in that causes the export to fail.

Any ideas what's going wrong here or how we could further debug the issue?

Thanks Smile

Report message to a moderator

Re: 'Export Features' - Unable to find: Installable Unit [message #637504 is a reply to message #637498]

Fri, 05 November 2010 21:09

Mirko Raner

Messages: 125
Registered: July 2009
Location: New York City, NY

Senior Member

I found this in the error log:
org.eclipse.osgi.service.pluginconversion.PluginConversionEx ception: Error parsing plugin manifest. Missing attribute "id" in element "plugin".
at org.eclipse.core.runtime.internal.adaptor.PluginConverterImp l.fillPluginInfo(PluginConverterImpl.java:126)
at org.eclipse.core.runtime.internal.adaptor.PluginConverterImp l.convertManifest(PluginConverterImpl.java:711)
at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.conve rtPluginManifest(BundlesAction.java:475)
at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.basic LoadManifest(BundlesAction.java:574)
at org.eclipse.pde.internal.build.publisher.GatherBundleAction. getBundleDescriptions(GatherBundleAction.java:52)
at org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.perfo rm(BundlesAction.java:595)
at org.eclipse.pde.internal.build.publisher.GatherBundleAction. perform(GatherBundleAction.java:43)
at org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.r un(Publisher.java:207)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.executeBatch(SimpleArtifactRepositor y.java:1044)
at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher .java:231)
at org.eclipse.equinox.p2.publisher.AbstractPublisherApplicatio n.run(AbstractPublisherApplication.java:281)
at org.eclipse.pde.internal.build.publisher.GatherBundleTask.ex ecute(GatherBundleTask.java:71)
...

The fact that the code goes into BundlesAction.convertPluginManifest tells me that there is apparently some problem reading the MANIFEST.MF of that problem, though that file looks O.K. and doesn't have any warnings or errors. Could this be a whitespace or line terminator issue?

Report message to a moderator

Re: 'Export Features' - Unable to find: Installable Unit [message #637575 is a reply to message #637504]

Sun, 07 November 2010 05:18

Mirko Raner

Messages: 125
Registered: July 2009
Location: New York City, NY

Senior Member

Somehow we ended up with mixed line separators in our MANIFEST.MF. Apparently, Eclipse's regular classpath resolution can deal with that, but the P2 export cannot. After fixing the line separators and re-running the Manifest builder we were able to export the feature again.

Report message to a moderator

Previous Topic:	Where to start? Eclipse-diff-viewer for custom file format.
Next Topic:	Inherit from GCC eclipse toolchain

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 08:55:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter