-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add JDK9 Module name #32
Comments
Why is this stil open? |
Not sure? Is it done properly?
…-----
Important Notice
This communication contains information that is considered
confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and
delete the original
On 22 Nov 2018, at 09:10, Martin Diphoorn ***@***.***> wrote:
Why is this stil open?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
We should probably also add a module-info.java See below site for a tutorial: |
In middle of Brexit (multiple) deliveries right now...if you could handle
it, it would be great.
Thanks
B
…On Wed, 5 Dec 2018 at 08:47, Martin Diphoorn ***@***.***> wrote:
We should probably also add a module-info.java
See below site for a tutorial:
https://blog.codefx.org/java/java-module-system-tutorial/
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPeaUX2Yw1vVm3QfTp6IKig7uM5oIIiks5u14gugaJpZM4RDPOd>
.
|
I did have a quicklook, but if i try to compile with java 11 i receive an error with osgi. And i don't have the time to look into that.
Also i don't know if i make it a java 11 module it will still work in osgi. I think it would also be a good thing to cleanup our pom's a little bit. Make sure that the parent contains all the versions in properties. And the modules are using those. Now java version is defined in more then one place. An other thing i don't know is this parent: <parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent> And if it will be a problem with java 11. |
That parent Pom allows us to deploy on Maven Central.
Agreed, I’d like to re-.org all our poms for FlatPack, ObjectlabUtil, JTreeMap and nachocalendar....
Every release is painful 😖...
…-----
Important Notice
This communication contains information that is considered
confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and
delete the original
On 6 Dec 2018, at 19:20, Martin Diphoorn ***@***.***> wrote:
I did have a quicklook, but if i try to compile with java 11 i receive an error with osgi. And i don't have the time to look into that.
java.lang.NullPointerException
at aQute.bnd.header.OSGiHeader.quote(OSGiHeader.java:150)
Also i don't know if i make it a java 11 module it will still work in osgi.
I think it would also be a good thing to cleanup our pom's a little bit. Make sure that the parent contains all the versions in properties. And the modules are using those. Now java version is defined in more then one place.
An other thing i don't know is this parent:
<parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent>
And if it will be a problem with java 11.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Using method described in
https://dzone.com/articles/automatic-module-name-calling-all-java-library-maintainers
The text was updated successfully, but these errors were encountered: