Herrmann <stephan.herrm...@berlin.de>
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Date: 05.10.2017 23:10
Subject: [cross-project-issues-dev] Eclipse plug-ins as automatic
modules in Java 9?
Sent by:cross-project-issues-dev-boun...@eclipse.org
On Fri, Oct 6, 2017 at 10:23 AM, Ed Willink wrote:
> A SimRel check requires David/Frederic to do a lot of chasing to get
> complete compliance.
>
I'd like to remind that SimRel is a community project just like any other,
and that contributions are most likely welcome from
Hi
https://bugs.eclipse.org/bugs/show_bug.cgi?id=525660 raised.
Since the problem is in the Manifest, manifest tools in the workspace
seem the place to solve it.
A SimRel check requires David/Frederic to do a lot of chasing to get
complete compliance.
A Tycho check only works for Tycho
> "I propose to make this a rule"
>
+1
> Do you mean an informal good practice
> or a Manifest editor warning and a quick fix
> or a Manifest builder automated edit?
Or even a Simrel requirement with an automated check?
Or if this is a general good practice for OSGi at large (and not just
On Fri, Oct 6, 2017 at 10:34 AM, Ed Willink wrote:
> Hi
>
> "I propose to make this a rule"
>
> Do you mean an informal good practice
>
> or a Manifest editor warning and a quick fix
^^ is probably best. It would be nice if someone opens PDE bug with the details.
>
> or a
Hi
"I propose to make this a rule"
Do you mean an informal good practice
or a Manifest editor warning and a quick fix
or a Manifest builder automated edit?
Regards
Ed Willink
On 05/10/2017 22:10, Stephan Herrmann wrote:
Hi,
I just noticed by chance that none of the artifacts
Hi,
I just noticed by chance that none of the artifacts we are producing
are consumable as "automatic modules" in Java 9 speak.
The reason is: JPMS defines an algorithm how names for automatic modules
are derived from the jar file name. Unfortunately, the spec expects any
version to be