[jira] [Updated] (NETBEANS-1397) NetBeans ignores Automatic-Module-Name when java modules are used
[
https://issues.apache.org/jira/browse/NETBEANS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel_K updated NETBEANS-1397:
--
Attachment: java-11-d.png
java-11-c.png
java-11-b.png
java-11-a.png
> NetBeans ignores Automatic-Module-Name when java modules are used
> -
>
> Key: NETBEANS-1397
> URL: https://issues.apache.org/jira/browse/NETBEANS-1397
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0
>Reporter: Pavel_K
>Priority: Major
> Attachments: NETBEANS-1397.png, java-11-a.png, java-11-b.png,
> java-11-c.png, java-11-d.png, mavenproject22.zip
>
>
> According to JPMS specs the name of automatic module can be set via
> MANIFEST.MF by Automatic-Module-Name entry. However, NetBeans doesn't read
> this entry and it gives problem. For example, there is a module which file
> name is `foo-boo-1.0.jar` with Automatic-Module-Name as `super.foo`. In my
> module I must use automatic module set in manifest otherwise JVM won't find
> this module. That's why I do
> {code:java}
> module my.module {
> requires super.foo;//LINE X
> }
> {code}
> At line X NetBeans shows me an error as it can't find this module! However,
> compiler compiles module without problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1397) NetBeans ignores Automatic-Module-Name when java modules are used
[
https://issues.apache.org/jira/browse/NETBEANS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lahoda updated NETBEANS-1397:
-
Attachment: NETBEANS-1397.png
> NetBeans ignores Automatic-Module-Name when java modules are used
> -
>
> Key: NETBEANS-1397
> URL: https://issues.apache.org/jira/browse/NETBEANS-1397
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0
>Reporter: Pavel_K
>Priority: Major
> Attachments: NETBEANS-1397.png, mavenproject22.zip
>
>
> According to JPMS specs the name of automatic module can be set via
> MANIFEST.MF by Automatic-Module-Name entry. However, NetBeans doesn't read
> this entry and it gives problem. For example, there is a module which file
> name is `foo-boo-1.0.jar` with Automatic-Module-Name as `super.foo`. In my
> module I must use automatic module set in manifest otherwise JVM won't find
> this module. That's why I do
> {code:java}
> module my.module {
> requires super.foo;//LINE X
> }
> {code}
> At line X NetBeans shows me an error as it can't find this module! However,
> compiler compiles module without problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1397) NetBeans ignores Automatic-Module-Name when java modules are used
[
https://issues.apache.org/jira/browse/NETBEANS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel_K updated NETBEANS-1397:
--
Description:
According to JPMS specs the name of automatic module can be set via MANIFEST.MF
by Automatic-Module-Name entry. However, NetBeans doesn't read this entry and
it gives problem. For example, there is a module which file name is
`foo-boo-1.0.jar` with Automatic-Module-Name as `super.foo`. In my module I
must use automatic module set in manifest otherwise JVM won't find this module.
That's why I do
{code:java}
module my.module {
requires super.foo;//LINE X
}
{code}
At line X NetBeans shows me an error as it can't find this module! However,
compiler compiles module without problem.
was:
According to JPMS specs the name of automatic module can be set via MANIFEST.MF
by Automatic-Module-Name entry. However, netbeans doesn't read this entry and
it gives problem. For example, there is module which file name is
`foo-boo-1.0.jar` with Automatic-Module-Name as `super.foo`. In my module I
must use automatic module set in manifest otherwise JVM won't find this module.
That's why I do
module my.module {
requires super.foo;//LINE X
}
At line X NetBeans shows me an error and it can't find this module! However,
compiler compiles module without problem.
> NetBeans ignores Automatic-Module-Name when java modules are used
> -
>
> Key: NETBEANS-1397
> URL: https://issues.apache.org/jira/browse/NETBEANS-1397
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0
>Reporter: Pavel_K
>Priority: Major
>
> According to JPMS specs the name of automatic module can be set via
> MANIFEST.MF by Automatic-Module-Name entry. However, NetBeans doesn't read
> this entry and it gives problem. For example, there is a module which file
> name is `foo-boo-1.0.jar` with Automatic-Module-Name as `super.foo`. In my
> module I must use automatic module set in manifest otherwise JVM won't find
> this module. That's why I do
> {code:java}
> module my.module {
> requires super.foo;//LINE X
> }
> {code}
> At line X NetBeans shows me an error as it can't find this module! However,
> compiler compiles module without problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
