Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an automatic module name for JPMS/Jigsaw #46

Closed
glassfishrobot opened this issue Feb 15, 2018 · 3 comments
Closed

Provide an automatic module name for JPMS/Jigsaw #46

glassfishrobot opened this issue Feb 15, 2018 · 3 comments
Assignees

Comments

@glassfishrobot
Copy link

Hi,

Could the EL jars provide an automatic module name for JPMS/Jigsaw?

It's just a matter of adding an Automatic-Module-Name entry for the maven-bundle-plugin.

From the discussions we had with the Jigsaw folks for Bean Validation, the module name should probably be java.el (not javax.el).

Not sure about you having an API jar and an API + impl jar though.

It would be nice if it could be added in a quick release as all of our Hibernate Validator dependencies now have one, except for EL, and we would like to make progress on this subject.

Thanks!

@glassfishrobot
Copy link
Author

@arjantijms arjantijms self-assigned this Jul 28, 2019
@MikeEdgar
Copy link

@arjantijms - is there any change in direction in the naming of the EL module for Jakarta EE? I.e., jakarta.el rather than java.el? A 3.0.x release with either a module-info or an automatic module name in the manifest would be helpful. I am happy to do a PR depending on the answer.

@markt-asf
Copy link
Contributor

The current plan for EL is to take the OSGi bundle name, convert any "-" to "." and use that as the module name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants