[
https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s...
]
Paul Leacu commented on LOCUS-50:
---------------------------------
[~nickboldt] [~lhein]
I've got a fix for this - I didn't think to look back to jsobschema2pojo's
manifest... *ugh* The new MANIFEST.MF should probably look like this:
{code}
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName:
org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core;singleton:=true
Bundle-Version: 0.4.13.qualifier
Bundle-ClassPath: .
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Require-Bundle: com.fasterxml.jackson.core.jackson-databind,
javax.validation
Export-Package: org.jsonschema2pojo,
org.jsonschema2pojo.exception,
org.jsonschema2pojo.rules,
org.jsonschema2pojo.util
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Eclipse-BuddyPolicy: registered
{code}
Building now...
Locus bundle for jsonschema2pojo has corrupted Export-Package
statement
-----------------------------------------------------------------------
Key: LOCUS-50
URL:
https://issues.jboss.org/browse/LOCUS-50
Project: JBoss Tools Locus
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Lars Heinemann
Assignee: Nick Boldt
Priority: Blocker
Fix For: 1.6.0
see
https://gist.github.com/lhein/47405c1fcb9dc2a7138e
Bundle:
org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710
When trying to resolve classes from this bundle it fails.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)