Eclipse Community Forums: Papyrus » Build error: incorrect version format for import-packages in manifest files

Help

Home

Home » Modeling » Papyrus » Build error: incorrect version format for import-packages in manifest files

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

Build error: incorrect version format for import-packages in manifest files [message #1787155]

Sun, 20 May 2018 09:46

Charlie Zhang

Messages: 1
Registered: May 2018

Junior Member

Hi folks,

I tried to build Papyrus 4.0.0-M6 on Eclipse Photon these days, but failed with many errors. Among them, there are some caused by the incorrectly-set version attributes of import-packages in many manifest files (MANIFEST.MF).

The error descriptions are like this:

'com.google.common.base' dependency must specify a version range...

However, currently the manifest file of project org.eclipse.papyrus.infra.core (and more others) is written as:

Import-Package: com.google.common.base;version="21.0.0",...

Please see the screenshot in the attachment for details. I guess version ranges like [21.0.0,...) should be used here.

Is this a bug? If it is, hope it could be fixed soon.

Thanks!

Attachment: Screenshot 2018-05-20 4.56.46pm.png
(Size: 1.79MB, Downloaded 103 times)

Report message to a moderator

Re: Build error: incorrect version format for import-packages in manifest files [message #1787517 is a reply to message #1787155]

Mon, 28 May 2018 07:18

Benoit Maggi

Messages: 129
Registered: March 2013
Location: Bordeaux, France

Senior Member

Hi,

I don't have the error.
Did you change the pde compiler option with more aggressive checks ?
(Window > Preference > Plug-in Development > Compiler

Or did you install some tooling to check Manifest?
(It's recommended to use range but not required)

It's very unlikely that we will use version range for Guava (which includes com.google.common ...)
Main reasons:
- Guava is evolving a lot faster than release train (See https://github.com/google/guava/releases )
- we already got many issues with Guava ranged version (See Bugs Papyrus Guava)

IMHO: time spent around Guava should be used to replace it (if possible) by Java 8/9 newest API

Regards
Benoit

Report message to a moderator

Previous Topic:	Problem with architecture configuration
Next Topic:	Add a new code generator

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 06:23:36 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter