Skip to content

How to use roaster in modularized project ? #315

@Rizen59

Description

@Rizen59

Hi, I'm trying to use roaster in a modularized project

<properties>
  <version.roaster>2.29.0.Final</version.roaster>
</properties>

<dependency>
  <groupId>org.jboss.forge.roaster</groupId>
  <artifactId>roaster-api</artifactId>
  <version>${version.roaster}</version>
</dependency>
<dependency>
  <groupId>org.jboss.forge.roaster</groupId>
  <artifactId>roaster-jdt</artifactId>
  <version>${version.roaster}</version>
  <scope>runtime</scope>
</dependency>

If roaster-jdt is used in scope runtime it cannot be added in module-info.java
In scope compile, add in module-info.java

requires roaster.api;
requires roaster.jdt;

The result will be:

[WARNING] Can't extract module name from roaster-jdt-2.29.0.Final.jar: Provider class org.jboss.forge.roaster._shade.org.eclipse.osgi.launch.EquinoxFactory not in JAR file roaster-jdt-2.29.0.Final.jar
[WARNING] ****************************************************************************************************************************************************
[WARNING] * Required filename-based automodules detected: [roaster-api-2.29.0.Final.jar]. Please don't publish this project to a public artifact repository! *
[WARNING] ****************************************************************************************************************************************************

Did I missed something?
Maybe the project could be modularized for a futur version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions