Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Fri, 6 Oct 2017 09:50:35 +0200
Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cross-project-issues-dev>
List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>

"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?

Or even a Simrel requirement with an automated check?

Or if this is a general good practice for OSGi at large (and not just Eclipse.org projects), a Tycho validation rule showing warning or error for new builds?

Follow-Ups:
- Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?
  - From: Ed Willink

References:
- [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?
  - From: Stephan Herrmann
- Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?
  - From: Ed Willink

Prev by Date: Re: [cross-project-issues-dev] Confusing org.apache.batik versions
Next by Date: [cross-project-issues-dev] MySQL down?
Previous by thread: Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?
Next by thread: Re: [cross-project-issues-dev] Eclipse plug-ins as automatic modules in Java 9?
Index(es):
- Date
- Thread

Breadcrumbs