subject:"warning default invalid module name"

Re: warning default invalid module name Errors Replicated

2020-01-06 Thread Zahid Rahman

I am really please I pursued this issue and came across yourself.

This  ubuntu bug is causing fear and apprehension across many apache
frameworks.
It has caused a big IT giant  fear too.

Some people think it is jdk 11 issue so using or are recommending to use
jdk 8.

Now I am free to use any jdk including bleeding edge  for any framework. I
was just playing about with Javafx , I am using another framework.

On Sun, 5 Jan 2020, 22:38 Stuart McCulloch,  wrote:

> The Java 11 warning mentions that "/usr/share/maven/lib/guice.jar" has a
> class named "com.google.inject.internal.cglib.core.$ReflectUtils$1"
>
> This looks suspect because the official Maven distribution uses the
> "no-AOP" version of Guice which doesn't contain any CGLIB classes. It
> suggests that whoever provided that copy of Maven has replaced the "no-AOP"
> version with the "AOP" version, and this will cause warnings on Java 11.
> (The "AOP" version uses CGLIB which currently relies on certain reflective
> access that Java 11 warns about - whereas the "no-AOP" version doesn't.)
>
> If you install an official Maven distribution from Apache (and make sure
> that the MAVEN_HOME environment variable points to it) then you shouldn't
> see that warning.
>
> On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise 
> wrote:
>
>> Hi,
>>
>> On 05.01.20 22:54, zahid wrote:
>> > Thank you. These files has been generated by NETBEANS IDE.
>>
>> I have my doubts that plugins generated as dependencies by Netbeans if
>> so this is simply a bug 
>>
>>
>> >
>> > *Netbeans uses a very old version Apache Maven 3.3.9 and these warnings
>> > do not appear.
>>
>> This means you don't have defined all your used plugins correctly within
>> your pom.xml (pluginManagement as you already done with
>> maven-compiler-plugin) with their appropriate versions.
>>
>> Older plugins versions didn't even know something about Java Module
>> system (JPMS) names etc. (This is what you get with Maven 3.3.9..) That
>> looks like that those warnings have gone but they are still there
>> because older plugins didn't recogzined them...
>>
>>
>> > *
>> >
>> > *I still get these warnings with the revised pom.xml
>> > *
>> >
>> > kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
>> > WARNING: An illegal reflective access operation has occurred
>> > WARNING: Illegal reflective access by
>> > com.google.inject.internal.cglib.core.$ReflectUtils$1
>> > (file:/usr/share/maven/lib/guice.jar) to method
>> >
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
>> > WARNING: Please consider reporting this to the maintainers of
>> > com.google.inject.internal.cglib.core.$ReflectUtils$1
>> > WARNING: Use --illegal-access=warn to enable warnings of further
>> illegal
>> > reflective access operations
>> > WARNING: All illegal access operations will be denied in a future
>> release
>> > [INFO] Scanning for projects...
>> > [INFO]
>> > [INFO] --< co.uk.backbutton:HelloFX
>> >  >--
>> > [INFO] Building HelloFX 1.0-SNAPSHOT
>> > [INFO] [ jar
>> > ]-
>> > [INFO]
>> > [INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
>> > [INFO]
>> > 
>> > [INFO] BUILD SUCCESS
>> > [INFO]
>> > 
>> > [INFO] Total time:  3.934 s
>> > [INFO] Finished at: 2020-01-05T21:51:22Z
>> > [INFO]
>> > 
>>
>>
>> This is something completely different.
>>
>> If the pom is the one your are using than you should use Maven 3.6.3 and
>> correctly check your environment if it's pointing to the correct Maven
>> installation... (Do you use M2_HOME or MAVEN_HOME environment variables?
>> Only add the bin directory of the Maven installation to the PATH nothing
>> else).
>>
>> I suppose /usr/share/maven/lib/guice.jar) is from your Maven
>> installation on your system?
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>>
>>
>> >
>> > *REVISED pom.xml*
>> >
>> > kub18@UB18:~/javafx/helloapp$ cat pom.xml
>> > http://maven.apache.org/POM/4.0.0;
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>> >xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> > http://maven.apache.org/maven-v4_0_0.xsd;>
>> >
>> >  4.0.0
>> >  co.uk.backbutton
>> >  HelloFX
>> >  1.0-SNAPSHOT
>> >
>> >  
>> > UTF-8
>> >
>> UTF-8
>> > 11
>> > 11
>> >  
>> >
>> >  
>> >  
>> >  org.openjfx
>> >  javafx-controls
>> >  14-ea+6
>> >  
>> >  
>> >  org.openjfx
>> >  javafx-fxml
>> >  13
>> >  
>> >  
>> >
>> >  
>> >  
>> >   
>> >  
>> > org.apache.maven.plugins
>> > maven-compiler-plugin
>> >  3.8.0
>> >

Re: warning default invalid module name

2020-01-06 Thread zahid

*Running in NETBEANS IDE
*

*mvn error message* "you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter." ..

*I would like to see an example syntax setting in pom.xml file of **
*

*'includePathExceptionsInClasspath' **
*

*then I can fix it next time this happens.*

*
*

> Also do not change  on the top menu,

> Which menu? In Maven there is no menu? ...

*NETBEANS IDE menu at the top drop down list  below options Run Debug.**
*

*
*

**

The error was in NETBEANS IDE  when  running an archetype application.

NETBEANS IDE comes with mvn version Apache Maven 3.3.9

As you can see below I reverted back to system installation of mvn 3.3.9 
same as NETBEANS IDE.

I do not  now get warning when creating command line archetypes.

*Console output of mvn -version **
*

Apache Maven 3.3.9

Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build
Java home: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: "unix"

*NETBEANS ABOUT DIALOGUE*

Product Version: Apache NetBeans IDE 11.2

Java: 11.0.5; OpenJDK 64-Bit Server VM 11.0.5+10-post-Ubuntu-0ubuntu1.118.04
Runtime: OpenJDK Runtime Environment 11.0.5+10-post-Ubuntu-0ubuntu1.118.04
System: Linux version 5.0.0-37-generic running on amd64; UTF-8; en_GB (nb)
User directory: /home/kub18/.netbeans/11.2
Cache directory: /home/kub18/.cache/netbeans/11.2

openjdk version "11.0.5" 2019-10-15

*KUBUNTU KInfocentre**
*

KDE plasma version 5.12.9

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic

On 05/01/2020 17:26, Karl Heinz Marbaise wrote:

On 05.01.20 18:06, zahid wrote:

I can't honestly remember which application I was having this problem 
with.

Unfortunately this means I can't help here..

BUT all my applications are running fine without errors or warnings.

without a concrete example it's more or less impossible to help ...I
don't know what versions of Maven you exactly using, which dependencies,
which plugin versions, which JDK version etc. etc...

I found most of these kind of  *GOTCHAS* is to reset the mvn goals to
"clean install".

That is to say go to project -> properties  -> right click -> actions >
scroll through resetting the  execute goals.

Which project properties? Running in IDE? Sounds like you don't run on
plain command line? Have you checked so?...

Also do not change  on the top menu,

Which menu? In Maven there is no menu? ...

Kind regards
Karl Heinz Marbaise

that will also cause different kind of warnings or errors.

You can change it to release-profile see what happens then change it
back again :)

Also some times you have errors and warnings  when you run by selecting
the double arrows. Then you have to "run file" by being in the java
class where the  "psvm" is   and right click -> "run file" . Then the
double arrow will run correctly after that.

On 05/01/2020 15:50, Karl Heinz Marbaise wrote:

Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a Java
identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar: plexus.container.default:
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be 
resolved as

modules and will not be included in the classpath; you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter.

Do you have a full working example of this? Best would be a GitHub
project?

Kind regards
Karl Heinz Marbaise

-

b/r

Zahid

--
www.backbutton.co.uk
¯\_(ツ)_/¯
Marriage between loose
and tight coupling
= healthy applications

Re: warning default invalid module name

2020-01-06 Thread zahid

Sorry , thanks for your response. I shall replicate the error and send 
the information you mentioned.

> Java version: 11.0.5, vendor: Private Build

> is very interesting..Have you build your own JDK ? ...

No sir , it is a result of installation using the command

*sudo apt-get install openjdk-11-jdk*

*
*

kub18@UB18:~/struts2/archetypes$ *update-alternatives --config java*
There are 2 choices for the alternative java (providing /usr/bin/java).

  Selection    Path Priority   Status

* 0    /usr/lib/jvm/java-11-openjdk-amd64/bin/java   
auto mode
  1    /usr/lib/jvm/java-11-openjdk-amd64/bin/java   
manual mode
  2    /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081  
manual mode

Press  to keep the current choice[*], or type selection number:

On 05/01/2020 18:36, Karl Heinz Marbaise wrote:

Hi,

sorry but you seemed not to read my questions:

without a full pom and it's dependencies it's impossible to see where
the warning is comming from cause it looked like there is a dependency
(plexus--...) extreme old one which does not has a module information
and can't be used as it...that means there is a dependency somewhere in
your project? or maybe in the used plugin javafx ?

Furthermore the output:

Java version: 11.0.5, vendor: Private Build

is very interesting..Have you build your own JDK ? ...

As I already mentioned. It would be helpful to have a full example
project as GitHub project ...

Kind regards
Karl Heinz Marbaise
On 05.01.20 19:08, zahid wrote:

*Running in NETBEANS IDE
*

*mvn error message* "you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter." ..

*I would like to see an example syntax setting in pom.xml file of **
*

*'includePathExceptionsInClasspath' **
*

*then I can fix it next time this happens.*

*
*

 > Also do not change  on the top menu,

 > Which menu? In Maven there is no menu? ...

*NETBEANS IDE menu at the top drop down list  below options Run Debug.**
*

*
*

**

The error was in NETBEANS IDE  when  running an archetype application.

NETBEANS IDE comes with mvn version Apache Maven 3.3.9

As you can see below I reverted back to system installation of mvn 3.3.9
same as NETBEANS IDE.

I do not  now get warning when creating command line archetypes.

*Console output of mvn -version **
*

Apache Maven 3.3.9

Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build
Java home: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: 
"unix"

*NETBEANS ABOUT DIALOGUE*

Product Version: Apache NetBeans IDE 11.2

Java: 11.0.5; OpenJDK 64-Bit Server VM 
11.0.5+10-post-Ubuntu-0ubuntu1.118.04
Runtime: OpenJDK Runtime Environment 
11.0.5+10-post-Ubuntu-0ubuntu1.118.04
System: Linux version 5.0.0-37-generic running on amd64; UTF-8; en_GB 
(nb)

User directory: /home/kub18/.netbeans/11.2
Cache directory: /home/kub18/.cache/netbeans/11.2

openjdk version "11.0.5" 2019-10-15

*KUBUNTU KInfocentre**
*

KDE plasma version 5.12.9

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic

On 05/01/2020 17:26, Karl Heinz Marbaise wrote:

On 05.01.20 18:06, zahid wrote:

I can't honestly remember which application I was having this problem
with.

Unfortunately this means I can't help here..

BUT all my applications are running fine without errors or warnings.

without a concrete example it's more or less impossible to help ...I
don't know what versions of Maven you exactly using, which 
dependencies,

which plugin versions, which JDK version etc. etc...

I found most of these kind of  *GOTCHAS* is to reset the mvn goals to
"clean install".

That is to say go to project -> properties  -> right click -> 
actions >

scroll through resetting the  execute goals.

Which project properties? Running in IDE? Sounds like you don't run on
plain command line? Have you checked so?...

Also do not change  on the top menu,

Which menu? In Maven there is no menu? ...

Kind regards
Karl Heinz Marbaise

that will also cause different kind of warnings or errors.

You can change it to release-profile see what happens then change it
back again :)

Also some times you have errors and warnings  when you run by 
selecting

the double arrows. Then you have to "run file" by being in the java
class where the  "psvm" is   and right click -> "run file" . Then the
double arrow will run correctly after that.

On 05/01/2020 15:50, Karl Heinz Marbaise wrote:

Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a 
Java

identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar:

Re: warning default invalid module name Errors Replicated

2020-01-06 Thread zahid


Thank you. These files has been generated by NETBEANS IDE.

*Netbeans uses a very old version Apache Maven 3.3.9 and these warnings 
do not appear.

*

*I still get these warnings with the revised pom.xml
*

kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
>--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 


[INFO] Total time:  3.934 s
[INFO] Finished at: 2020-01-05T21:51:22Z
[INFO] 



*REVISED pom.xml*

kub18@UB18:~/javafx/helloapp$ cat pom.xml
http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>


    4.0.0
    co.uk.backbutton
    HelloFX
    1.0-SNAPSHOT

    
UTF-8
UTF-8
11
11
    

    
    
    org.openjfx
    javafx-controls
    14-ea+6
    
    
    org.openjfx
    javafx-fxml
    13
    
    

    
    
 
    
org.apache.maven.plugins
maven-compiler-plugin
    3.8.0
    
${maven.compiler.source}
    
    

    
    org.openjfx
javafx-maven-plugin
    0.0.3
    
    HelloFX
    
    
    
 
    



On 05/01/2020 20:53, Karl Heinz Marbaise wrote:

Hi,


On 05.01.20 21:31, zahid wrote:


mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: 
"unix"


*ls -l
*total 24
-rw-rw-r-- 1 kub18 kub18 4770 Jan  3 15:02 nbactions.xml
-rw-rw-r-- 1 kub18 kub18  455 Jan  1 21:58 pom_old.xml
-rwxrwxrwx 1 kub18 kub18 2520 Jan  3 15:17 pom.xml
drwxrwxr-x 3 kub18 kub18 4096 Jan  1 21:45 src
drwxrwxr-x 7 kub18 kub18 4096 Jan  5 09:24 target

*
*

*consol output**
*

kub18@UB18:~/javafx/helloapp$ mvn javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further 
illegal reflective access operations
WARNING: All illegal access operations will be denied in a future 
release

[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
 >--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-6.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-30.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Some dependencies encountered issues while attempting to be 
resolved as modules and will not be included in the classpath; you 
can change this behavior via the 'includePathExceptionsInClasspath' 
configuration parameter.
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 


[INFO] Total time:  15.673 s
[INFO] Finished at: 2020-01-05T20:20:17Z
[INFO] 


*
*

*kub18@UB18:~/javafx/helloapp$ cat pom.xml*

Re: warning default invalid module name Errors Replicated

2020-01-06 Thread zahid



mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: 
"unix"


*ls -l
*total 24
-rw-rw-r-- 1 kub18 kub18 4770 Jan  3 15:02 nbactions.xml
-rw-rw-r-- 1 kub18 kub18  455 Jan  1 21:58 pom_old.xml
-rwxrwxrwx 1 kub18 kub18 2520 Jan  3 15:17 pom.xml
drwxrwxr-x 3 kub18 kub18 4096 Jan  1 21:45 src
drwxrwxr-x 7 kub18 kub18 4096 Jan  5 09:24 target

*
*

*consol output**
*

kub18@UB18:~/javafx/helloapp$ mvn javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
>--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-6.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-30.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Some dependencies encountered issues while attempting to be 
resolved as modules and will not be included in the classpath; you can 
change this behavior via the 'includePathExceptionsInClasspath' 
configuration parameter.
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 


[INFO] Total time:  15.673 s
[INFO] Finished at: 2020-01-05T20:20:17Z
[INFO] 


*
*

*kub18@UB18:~/javafx/helloapp$ cat pom.xml*

http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>

    4.0.0
    co.uk.backbutton
    HelloFX
    1.0-SNAPSHOT
    
UTF-8
UTF-8

11
11
    
    

    
    org.openjfx
    javafx-controls
    14-ea+6
    
    
    org.openjfx
    javafx-fxml
    13
    
    
    plexus
    plexus-container-default
    1.0-alpha-6

    
org.apache.maven.plugins
maven-source-plugin
    3.2.1
    
    
org.apache.maven.plugins
maven-javadoc-plugin
    3.1.1
    

    
org.apache.maven.plugins
maven-deploy-plugin
    3.0.0-M1
    

    
    
    
    
org.apache.maven.plugins
maven-compiler-plugin
    3.8.0
    
    11
    
    

    
    org.openjfx
javafx-maven-plugin
    0.0.3
    
    HelloFX
    
    
    
    

*kub18@UB18:~/javafx/helloapp$ cat nbactions.xml
*

    
    rebuild
    
    *
    
    
    clean
    install
    javafx:run
    
    
    
    build
    
    *
    
    
    install
    javafx:run
    
    
    
build-with-dependencies
    also-make
    
    *
    
    
    clean
    install
    javafx:run
    
    
    
    run
    
    jar
    
    
    clean
    install
    javafx:run
    
    
    -classpath %classpath 
${packageClassName}

java
    
    
    
    run.single.main
    
    *
    
    
    clean
    install
    javafx:run
    
    
    -classpath %classpath 
${packageClassName}

java
${classPathScope}
    
    
    
    debug
    
    jar
    
    
    clean
    build
    install
    javafx:run

Re: warning default invalid module name Errors Replicated

2020-01-06 Thread zahid

I installed maven using *sudo apt-get install  maven**
*

I even got this message at the end.

*update-alternatives: using /usr/share/maven/bin/mvn to provide 
/usr/bin/mvn (mvn) in auto mode**

*

from the console output showing my current system settings, what do you 
say should be the  exact settings  for env. variable(s) ? I don't want 
to screw up anything. From the information I received I thought if  mvn 
-version works, that means maven setup is complete. Anyway I think the  
"sudo apt-get install maven"  people need to be notified of this bug.

kub18@UB18:~/javafx/helloapp$ *echo $M2_HOME**
**
*kub18@UB18:~/javafx/helloapp$ *echo $MAVEN_HOME**
*
kub18@UB18:~/javafx/helloapp$ *whereis maven*
*maven: /etc/maven /usr/share/maven*

kub18@UB18:~/javafx/helloapp$ *whereis mvn**
**mvn: /usr/bin/mvn /usr/share/man/man1/mvn.1.gz*

kub18@UB18:~/javafx/helloapp$ mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: "unix"

On 05/01/2020 22:38, Stuart McCulloch wrote:
The Java 11 warning mentions that "/usr/share/maven/lib/guice.jar" has 
a class named "com.google.inject.internal.cglib.core.$ReflectUtils$1"

This looks suspect because the official Maven distribution uses the 
"no-AOP" version of Guice which doesn't contain any CGLIB classes. It 
suggests that whoever provided that copy of Maven has replaced the 
"no-AOP" version with the "AOP" version, and this will cause warnings 
on Java 11. (The "AOP" version uses CGLIB which currently relies on 
certain reflective access that Java 11 warns about - whereas the 
"no-AOP" version doesn't.)

If you install an official Maven distribution from Apache (and make 
sure that the MAVEN_HOME environment variable points to it) then you 
shouldn't see that warning.

On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise > wrote:

Hi,

On 05.01.20 22:54, zahid wrote:
> Thank you. These files has been generated by NETBEANS IDE.

I have my doubts that plugins generated as dependencies by
Netbeans if
so this is simply a bug 

>
> *Netbeans uses a very old version Apache Maven 3.3.9 and these
warnings
> do not appear.

This means you don't have defined all your used plugins correctly
within
your pom.xml (pluginManagement as you already done with
maven-compiler-plugin) with their appropriate versions.

Older plugins versions didn't even know something about Java Module
system (JPMS) names etc. (This is what you get with Maven 3.3.9..)
That
looks like that those warnings have gone but they are still there
because older plugins didn't recogzined them...

> *
>
> *I still get these warnings with the revised pom.xml
> *
>
> kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/usr/share/maven/lib/guice.jar) to method
>

java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further
illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a
future release
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< co.uk.backbutton:HelloFX
>  >--
> [INFO] Building HelloFX 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
> [INFO]
>

> [INFO] BUILD SUCCESS
> [INFO]
>

> [INFO] Total time:  3.934 s
> [INFO] Finished at: 2020-01-05T21:51:22Z
> [INFO]
>

This is something completely different.

If the pom is the one your are using than you should use Maven
3.6.3 and
correctly check your environment if it's pointing to the correct
Maven
installation... (Do you use M2_HOME or MAVEN_HOME environment
variables?
Only add the bin directory of the Maven installation to the PATH
nothing
else).

I suppose /usr/share/maven/lib/guice.jar) is from your Maven
installation on your system?

Kind regards
Karl Heinz Marbaise

>
> *REVISED pom.xml*
>
>

Re: warning default invalid module name Errors Replicated :SUCCESS

2020-01-06 Thread zahid

*mvn -v**
*Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: "unix"

kub18@UB18:~/javafx/helloapp$ *mvn javafx:run*
[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
>--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time:  4.488 s
[INFO] Finished at: 2020-01-06T00:30:59Z
[INFO] 

On 06/01/2020 00:26, Stuart McCulloch wrote:
Is this Ubuntu?  I seem to remember they have their own build of Maven 
which differs from the Apache source.

( https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1754602 
suggests it's a known bug in their packaging/build? )

If you download Maven from http://maven.apache.org/download.cgi and 
follow the instructions in http://maven.apache.org/install.html then 
you shouldn't see those warnings.

On Mon, 6 Jan 2020 at 00:02, zahid > wrote:

I installed maven using *sudo apt-get install  maven**
*

I even got this message at the end.

*update-alternatives: using /usr/share/maven/bin/mvn to provide
/usr/bin/mvn (mvn) in auto mode**
*

from the console output showing my current system settings, what 
do you say should be the  exact settings for env. variable(s) ? I
don't want to screw up anything. From the information I received I
thought if  mvn -version works, that means maven setup is
complete. Anyway I think the  "sudo apt-get install maven"  people
need to be notified of this bug.

kub18@UB18:~/javafx/helloapp$ *echo $M2_HOME**
**
*kub18@UB18:~/javafx/helloapp$ *echo $MAVEN_HOME**
*
kub18@UB18:~/javafx/helloapp$ *whereis maven*
*maven: /etc/maven /usr/share/maven*

kub18@UB18:~/javafx/helloapp$ *whereis mvn**
**mvn: /usr/bin/mvn /usr/share/man/man1/mvn.1.gz*

kub18@UB18:~/javafx/helloapp$ mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64",
family: "unix"

On 05/01/2020 22:38, Stuart McCulloch wrote:

The Java 11 warning mentions that
"/usr/share/maven/lib/guice.jar" has a class named
"com.google.inject.internal.cglib.core.$ReflectUtils$1"

This looks suspect because the official Maven distribution uses
the "no-AOP" version of Guice which doesn't contain any CGLIB
classes. It suggests that whoever provided that copy of Maven has
replaced the "no-AOP" version with the "AOP" version, and this
will cause warnings on Java 11. (The "AOP" version uses CGLIB
which currently relies on certain reflective access that Java 11
warns about - whereas the "no-AOP" version doesn't.)

If you install an official Maven distribution from Apache (and
make sure that the MAVEN_HOME environment variable points to it)
then you shouldn't see that warning.

On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise
mailto:khmarba...@gmx.de>> wrote:

Hi,

On 05.01.20 22:54, zahid wrote:
> Thank you. These files has been generated by NETBEANS IDE.

I have my doubts that plugins generated as dependencies by
Netbeans if
so this is simply a bug 

>
> *Netbeans uses a very old version Apache Maven 3.3.9 and
these warnings
> do not appear.

This means you don't have defined all your used plugins
correctly within
your pom.xml (pluginManagement as you already done with
maven-compiler-plugin) with their appropriate versions.

Older plugins versions didn't even know something about Java
Module
system (JPMS) names etc. (This is what you get with Maven
3.3.9..) That
looks like that those warnings have gone but they are still
there
because older plugins didn't recogzined them...

> *
>
> *I still get these warnings with the revised pom.xml
> *
>
> kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1

Re: warning default invalid module name Errors Replicated

2020-01-06 Thread zahid

yes, KUBUNTU 18.04  on UBUNTU 18.04

*kub18@UB18: $**
*

*
*

On 06/01/2020 00:26, Stuart McCulloch wrote:

Is this Ubuntu?  I seem to remember they have their own build of Maven 
which differs from the Apache source.

( https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1754602 
suggests it's a known bug in their packaging/build? )

If you download Maven from http://maven.apache.org/download.cgi and 
follow the instructions in http://maven.apache.org/install.html then 
you shouldn't see those warnings.

On Mon, 6 Jan 2020 at 00:02, zahid > wrote:

I installed maven using *sudo apt-get install  maven**
*

I even got this message at the end.

*update-alternatives: using /usr/share/maven/bin/mvn to provide
/usr/bin/mvn (mvn) in auto mode**
*

from the console output showing my current system settings, what 
do you say should be the  exact settings for env. variable(s) ? I
don't want to screw up anything. From the information I received I
thought if  mvn -version works, that means maven setup is
complete. Anyway I think the  "sudo apt-get install maven"  people
need to be notified of this bug.

kub18@UB18:~/javafx/helloapp$ *echo $M2_HOME**
**
*kub18@UB18:~/javafx/helloapp$ *echo $MAVEN_HOME**
*
kub18@UB18:~/javafx/helloapp$ *whereis maven*
*maven: /etc/maven /usr/share/maven*

kub18@UB18:~/javafx/helloapp$ *whereis mvn**
**mvn: /usr/bin/mvn /usr/share/man/man1/mvn.1.gz*

kub18@UB18:~/javafx/helloapp$ mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64",
family: "unix"

On 05/01/2020 22:38, Stuart McCulloch wrote:

The Java 11 warning mentions that
"/usr/share/maven/lib/guice.jar" has a class named
"com.google.inject.internal.cglib.core.$ReflectUtils$1"

This looks suspect because the official Maven distribution uses
the "no-AOP" version of Guice which doesn't contain any CGLIB
classes. It suggests that whoever provided that copy of Maven has
replaced the "no-AOP" version with the "AOP" version, and this
will cause warnings on Java 11. (The "AOP" version uses CGLIB
which currently relies on certain reflective access that Java 11
warns about - whereas the "no-AOP" version doesn't.)

If you install an official Maven distribution from Apache (and
make sure that the MAVEN_HOME environment variable points to it)
then you shouldn't see that warning.

On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise
mailto:khmarba...@gmx.de>> wrote:

Hi,

On 05.01.20 22:54, zahid wrote:
> Thank you. These files has been generated by NETBEANS IDE.

I have my doubts that plugins generated as dependencies by
Netbeans if
so this is simply a bug 

>
> *Netbeans uses a very old version Apache Maven 3.3.9 and
these warnings
> do not appear.

This means you don't have defined all your used plugins
correctly within
your pom.xml (pluginManagement as you already done with
maven-compiler-plugin) with their appropriate versions.

Older plugins versions didn't even know something about Java
Module
system (JPMS) names etc. (This is what you get with Maven
3.3.9..) That
looks like that those warnings have gone but they are still
there
because older plugins didn't recogzined them...

> *
>
> *I still get these warnings with the revised pom.xml
> *
>
> kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/usr/share/maven/lib/guice.jar) to method
>

java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of
further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a
future release
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< co.uk.backbutton:HelloFX
>  >--
> [INFO] Building HelloFX 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @
HelloFX ---
> [INFO]

Re: warning default invalid module name Errors Replicated

2020-01-05 Thread Stuart McCulloch

Is this Ubuntu?  I seem to remember they have their own build of Maven
which differs from the Apache source.

( https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1754602  suggests
it's a known bug in their packaging/build? )

If you download Maven from http://maven.apache.org/download.cgi and follow
the instructions in http://maven.apache.org/install.html then you shouldn't
see those warnings.

On Mon, 6 Jan 2020 at 00:02, zahid  wrote:

> I installed maven using *sudo apt-get install  maven*
>
> I even got this message at the end.
>
> *update-alternatives: using /usr/share/maven/bin/mvn to provide
> /usr/bin/mvn (mvn) in auto mode*
>
> from the console output showing my current system settings, what  do you
> say should be the  exact settings  for env. variable(s) ? I don't want to
> screw up anything. From the information I received I thought if  mvn
> -version works, that means maven setup is complete. Anyway I think the
> "sudo apt-get install maven"  people need to be notified of this bug.
>
> kub18@UB18:~/javafx/helloapp$ *echo $M2_HOME*
>
> kub18@UB18:~/javafx/helloapp$ *echo $MAVEN_HOME*
>
> kub18@UB18:~/javafx/helloapp$ *whereis maven*
> *maven: /etc/maven /usr/share/maven*
>
> kub18@UB18:~/javafx/helloapp$ *whereis mvn*
> *mvn: /usr/bin/mvn /usr/share/man/man1/mvn.1.gz*
>
> kub18@UB18:~/javafx/helloapp$ mvn -version
> Apache Maven 3.6.0
> Maven home: /usr/share/maven
> Java version: 11.0.5, vendor: Private Build, runtime:
> /usr/lib/jvm/java-11-openjdk-amd64
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family:
> "unix"
>
>
> On 05/01/2020 22:38, Stuart McCulloch wrote:
>
> The Java 11 warning mentions that "/usr/share/maven/lib/guice.jar" has a
> class named "com.google.inject.internal.cglib.core.$ReflectUtils$1"
>
> This looks suspect because the official Maven distribution uses the
> "no-AOP" version of Guice which doesn't contain any CGLIB classes. It
> suggests that whoever provided that copy of Maven has replaced the "no-AOP"
> version with the "AOP" version, and this will cause warnings on Java 11.
> (The "AOP" version uses CGLIB which currently relies on certain reflective
> access that Java 11 warns about - whereas the "no-AOP" version doesn't.)
>
> If you install an official Maven distribution from Apache (and make sure
> that the MAVEN_HOME environment variable points to it) then you shouldn't
> see that warning.
>
> On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise 
> wrote:
>
>> Hi,
>>
>> On 05.01.20 22:54, zahid wrote:
>> > Thank you. These files has been generated by NETBEANS IDE.
>>
>> I have my doubts that plugins generated as dependencies by Netbeans if
>> so this is simply a bug 
>>
>>
>> >
>> > *Netbeans uses a very old version Apache Maven 3.3.9 and these warnings
>> > do not appear.
>>
>> This means you don't have defined all your used plugins correctly within
>> your pom.xml (pluginManagement as you already done with
>> maven-compiler-plugin) with their appropriate versions.
>>
>> Older plugins versions didn't even know something about Java Module
>> system (JPMS) names etc. (This is what you get with Maven 3.3.9..) That
>> looks like that those warnings have gone but they are still there
>> because older plugins didn't recogzined them...
>>
>>
>> > *
>> >
>> > *I still get these warnings with the revised pom.xml
>> > *
>> >
>> > kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
>> > WARNING: An illegal reflective access operation has occurred
>> > WARNING: Illegal reflective access by
>> > com.google.inject.internal.cglib.core.$ReflectUtils$1
>> > (file:/usr/share/maven/lib/guice.jar) to method
>> >
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
>> > WARNING: Please consider reporting this to the maintainers of
>> > com.google.inject.internal.cglib.core.$ReflectUtils$1
>> > WARNING: Use --illegal-access=warn to enable warnings of further
>> illegal
>> > reflective access operations
>> > WARNING: All illegal access operations will be denied in a future
>> release
>> > [INFO] Scanning for projects...
>> > [INFO]
>> > [INFO] --< co.uk.backbutton:HelloFX
>> >  >--
>> > [INFO] Building HelloFX 1.0-SNAPSHOT
>> > [INFO] [ jar
>> > ]-
>> > [INFO]
>> > [INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
>> > [INFO]
>> > 
>> > [INFO] BUILD SUCCESS
>> > [INFO]
>> > 
>> > [INFO] Total time:  3.934 s
>> > [INFO] Finished at: 2020-01-05T21:51:22Z
>> > [INFO]
>> > 
>>
>>
>> This is something completely different.
>>
>> If the pom is the one your are using than you should use Maven 3.6.3 and
>> correctly check your environment if it's

Re: warning default invalid module name Errors Replicated

2020-01-05 Thread Stuart McCulloch

The Java 11 warning mentions that "/usr/share/maven/lib/guice.jar" has a
class named "com.google.inject.internal.cglib.core.$ReflectUtils$1"

This looks suspect because the official Maven distribution uses the
"no-AOP" version of Guice which doesn't contain any CGLIB classes. It
suggests that whoever provided that copy of Maven has replaced the "no-AOP"
version with the "AOP" version, and this will cause warnings on Java 11.
(The "AOP" version uses CGLIB which currently relies on certain reflective
access that Java 11 warns about - whereas the "no-AOP" version doesn't.)

If you install an official Maven distribution from Apache (and make sure
that the MAVEN_HOME environment variable points to it) then you shouldn't
see that warning.

On Sun, 5 Jan 2020 at 22:24, Karl Heinz Marbaise  wrote:

> Hi,
>
> On 05.01.20 22:54, zahid wrote:
> > Thank you. These files has been generated by NETBEANS IDE.
>
> I have my doubts that plugins generated as dependencies by Netbeans if
> so this is simply a bug 
>
>
> >
> > *Netbeans uses a very old version Apache Maven 3.3.9 and these warnings
> > do not appear.
>
> This means you don't have defined all your used plugins correctly within
> your pom.xml (pluginManagement as you already done with
> maven-compiler-plugin) with their appropriate versions.
>
> Older plugins versions didn't even know something about Java Module
> system (JPMS) names etc. (This is what you get with Maven 3.3.9..) That
> looks like that those warnings have gone but they are still there
> because older plugins didn't recogzined them...
>
>
> > *
> >
> > *I still get these warnings with the revised pom.xml
> > *
> >
> > kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > com.google.inject.internal.cglib.core.$ReflectUtils$1
> > (file:/usr/share/maven/lib/guice.jar) to method
> >
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> > WARNING: Please consider reporting this to the maintainers of
> > com.google.inject.internal.cglib.core.$ReflectUtils$1
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > [INFO] Scanning for projects...
> > [INFO]
> > [INFO] --< co.uk.backbutton:HelloFX
> >  >--
> > [INFO] Building HelloFX 1.0-SNAPSHOT
> > [INFO] [ jar
> > ]-
> > [INFO]
> > [INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
> > [INFO]
> > 
> > [INFO] BUILD SUCCESS
> > [INFO]
> > 
> > [INFO] Total time:  3.934 s
> > [INFO] Finished at: 2020-01-05T21:51:22Z
> > [INFO]
> > 
>
>
> This is something completely different.
>
> If the pom is the one your are using than you should use Maven 3.6.3 and
> correctly check your environment if it's pointing to the correct Maven
> installation... (Do you use M2_HOME or MAVEN_HOME environment variables?
> Only add the bin directory of the Maven installation to the PATH nothing
> else).
>
> I suppose /usr/share/maven/lib/guice.jar) is from your Maven
> installation on your system?
>
> Kind regards
> Karl Heinz Marbaise
>
>
>
> >
> > *REVISED pom.xml*
> >
> > kub18@UB18:~/javafx/helloapp$ cat pom.xml
> > http://maven.apache.org/POM/4.0.0;
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> >xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > http://maven.apache.org/maven-v4_0_0.xsd;>
> >
> >  4.0.0
> >  co.uk.backbutton
> >  HelloFX
> >  1.0-SNAPSHOT
> >
> >  
> > UTF-8
> >
> UTF-8
> > 11
> > 11
> >  
> >
> >  
> >  
> >  org.openjfx
> >  javafx-controls
> >  14-ea+6
> >  
> >  
> >  org.openjfx
> >  javafx-fxml
> >  13
> >  
> >  
> >
> >  
> >  
> >   
> >  
> > org.apache.maven.plugins
> > maven-compiler-plugin
> >  3.8.0
> >  
> > ${maven.compiler.source}
> >  
> >  
> >
> >  
> >  org.openjfx
> > javafx-maven-plugin
> >  0.0.3
> >  
> >  HelloFX
> >  
> >  
> >  
> >   
> >  
> > 
> >
> >
> > On 05/01/2020 20:53, Karl Heinz Marbaise wrote:
> >> Hi,
> >>
> >>
> >> On 05.01.20 21:31, zahid wrote:
> >>>
> >>> mvn -version
> >>> Apache Maven 3.6.0
> >>> Maven home: /usr/share/maven
> >>> Java version: 11.0.5, vendor: Private Build, runtime:
> >>> /usr/lib/jvm/java-11-openjdk-amd64
>

Re: warning default invalid module name Errors Replicated

2020-01-05 Thread Karl Heinz Marbaise


Hi,

On 05.01.20 22:54, zahid wrote:

Thank you. These files has been generated by NETBEANS IDE.


I have my doubts that plugins generated as dependencies by Netbeans if 
so this is simply a bug 





*Netbeans uses a very old version Apache Maven 3.3.9 and these warnings 
do not appear.


This means you don't have defined all your used plugins correctly within 
your pom.xml (pluginManagement as you already done with 
maven-compiler-plugin) with their appropriate versions.


Older plugins versions didn't even know something about Java Module 
system (JPMS) names etc. (This is what you get with Maven 3.3.9..) That 
looks like that those warnings have gone but they are still there 
because older plugins didn't recogzined them...




*

*I still get these warnings with the revised pom.xml
*

kub18@UB18:~/javafx/helloapp$ mvn  javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
 >--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 


[INFO] Total time:  3.934 s
[INFO] Finished at: 2020-01-05T21:51:22Z
[INFO] 




This is something completely different.

If the pom is the one your are using than you should use Maven 3.6.3 and 
correctly check your environment if it's pointing to the correct Maven 
installation... (Do you use M2_HOME or MAVEN_HOME environment variables? 
Only add the bin directory of the Maven installation to the PATH nothing 
else).


I suppose /usr/share/maven/lib/guice.jar) is from your Maven 
installation on your system?


Kind regards
Karl Heinz Marbaise





*REVISED pom.xml*

kub18@UB18:~/javafx/helloapp$ cat pom.xml
http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>


     4.0.0
     co.uk.backbutton
     HelloFX
     1.0-SNAPSHOT

     
UTF-8
UTF-8
11
11
     

     
     
     org.openjfx
     javafx-controls
     14-ea+6
     
     
     org.openjfx
     javafx-fxml
     13
     
     

     
     
  
     
org.apache.maven.plugins
maven-compiler-plugin
     3.8.0
     
${maven.compiler.source}
     
     

     
     org.openjfx
javafx-maven-plugin
     0.0.3
     
     HelloFX
     
     
     
  
     



On 05/01/2020 20:53, Karl Heinz Marbaise wrote:

Hi,


On 05.01.20 21:31, zahid wrote:


mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: 
"unix"


*ls -l
*total 24
-rw-rw-r-- 1 kub18 kub18 4770 Jan  3 15:02 nbactions.xml
-rw-rw-r-- 1 kub18 kub18  455 Jan  1 21:58 pom_old.xml
-rwxrwxrwx 1 kub18 kub18 2520 Jan  3 15:17 pom.xml
drwxrwxr-x 3 kub18 kub18 4096 Jan  1 21:45 src
drwxrwxr-x 7 kub18 kub18 4096 Jan  5 09:24 target

*
*

*consol output**
*

kub18@UB18:~/javafx/helloapp$ mvn javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further 
illegal reflective access operations
WARNING: All illegal access operations will be denied in a future 
release

[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
 >--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO]

Re: warning default invalid module name Errors Replicated

2020-01-05 Thread Karl Heinz Marbaise


Hi,


On 05.01.20 21:31, zahid wrote:


mvn -version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build, runtime: 
/usr/lib/jvm/java-11-openjdk-amd64

Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: 
"unix"


*ls -l
*total 24
-rw-rw-r-- 1 kub18 kub18 4770 Jan  3 15:02 nbactions.xml
-rw-rw-r-- 1 kub18 kub18  455 Jan  1 21:58 pom_old.xml
-rwxrwxrwx 1 kub18 kub18 2520 Jan  3 15:17 pom.xml
drwxrwxr-x 3 kub18 kub18 4096 Jan  1 21:45 src
drwxrwxr-x 7 kub18 kub18 4096 Jan  5 09:24 target

*
*

*consol output**
*

kub18@UB18:~/javafx/helloapp$ mvn javafx:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO] --< co.uk.backbutton:HelloFX 
 >--

[INFO] Building HelloFX 1.0-SNAPSHOT
[INFO] [ jar 
]-

[INFO]
[INFO] --- javafx-maven-plugin:0.0.3:run (default-cli) @ HelloFX ---
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-6.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Can't extract module name from 
plexus-container-default-1.0-alpha-30.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
[WARNING] Some dependencies encountered issues while attempting to be 
resolved as modules and will not be included in the classpath; you can 
change this behavior via the 'includePathExceptionsInClasspath' 
configuration parameter.
[INFO] 


[INFO] BUILD SUCCESS
[INFO] 


[INFO] Total time:  15.673 s
[INFO] Finished at: 2020-01-05T20:20:17Z
[INFO] 


*
*

*kub18@UB18:~/javafx/helloapp$ cat pom.xml*

http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>

     4.0.0
     co.uk.backbutton
     HelloFX
     1.0-SNAPSHOT
     
UTF-8
UTF-8

11
11
     
     

     
     org.openjfx
     javafx-controls
     14-ea+6
     
     
     org.openjfx
     javafx-fxml
     13
     
     
     plexus
     plexus-container-default
     1.0-alpha-6

     
org.apache.maven.plugins
maven-source-plugin
     3.2.1
     
     
org.apache.maven.plugins
maven-javadoc-plugin
     3.1.1
     

     
org.apache.maven.plugins
maven-deploy-plugin
     3.0.0-M1
     

     
     
     
     
org.apache.maven.plugins
maven-compiler-plugin
     3.8.0
     
     11
     
     

     
     org.openjfx
javafx-maven-plugin
     0.0.3
     
     HelloFX
     
     
     
     





Never use maven plugins as dependencies
also do not use plexus-container-default as a dependency.


So remove the dependency definition:

maven-source-plugin
maven-javadoc-plugin
maven-deploy-plugin

also remove the dependency:

plexus-container-default from your pom file...

If you want to define your plugins in your pom which is a good idea you 
should use pluginManagement instead ...


This will remove the warnings you have gotten

The issue had been the wrong dependencies..


Kind regards
Karl Heinz Marbaise





*kub18@UB18:~/javafx/helloapp$ cat nbactions.xml
*

     
     rebuild
     
     *
     
     
     clean
     install
     javafx:run
     
     
     
     build
     
     *
     
     
     install
     javafx:run
     
     
     
build-with-dependencies
     also-make
     
     *
     
     
     clean
     install
     javafx:run
     
     
     
     run
     
     jar
     
     
     clean

Re: warning default invalid module name

2020-01-05 Thread Karl Heinz Marbaise

Hi,

sorry but you seemed not to read my questions:

without a full pom and it's dependencies it's impossible to see where
the warning is comming from cause it looked like there is a dependency
(plexus--...) extreme old one which does not has a module information
and can't be used as it...that means there is a dependency somewhere in
your project? or maybe in the used plugin javafx ?

Furthermore the output:

Java version: 11.0.5, vendor: Private Build

is very interesting..Have you build your own JDK ? ...

As I already mentioned. It would be helpful to have a full example
project as GitHub project ...

Kind regards
Karl Heinz Marbaise
On 05.01.20 19:08, zahid wrote:

*Running in NETBEANS IDE
*

*mvn error message* "you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter." ..

*I would like to see an example syntax setting in pom.xml file of **
*

*'includePathExceptionsInClasspath' **
*

*then I can fix it next time this happens.*

*
*

 > Also do not change  on the top menu,

 > Which menu? In Maven there is no menu? ...

*NETBEANS IDE menu at the top drop down list  below options Run Debug.**
*

*
*

**

The error was in NETBEANS IDE  when  running an archetype application.

NETBEANS IDE comes with mvn version Apache Maven 3.3.9

As you can see below I reverted back to system installation of mvn 3.3.9
same as NETBEANS IDE.

I do not  now get warning when creating command line archetypes.

*Console output of mvn -version **
*

Apache Maven 3.3.9

Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Private Build
Java home: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-37-generic", arch: "amd64", family: "unix"

*NETBEANS ABOUT DIALOGUE*

Product Version: Apache NetBeans IDE 11.2

Java: 11.0.5; OpenJDK 64-Bit Server VM 11.0.5+10-post-Ubuntu-0ubuntu1.118.04
Runtime: OpenJDK Runtime Environment 11.0.5+10-post-Ubuntu-0ubuntu1.118.04
System: Linux version 5.0.0-37-generic running on amd64; UTF-8; en_GB (nb)
User directory: /home/kub18/.netbeans/11.2
Cache directory: /home/kub18/.cache/netbeans/11.2

openjdk version "11.0.5" 2019-10-15

*KUBUNTU KInfocentre**
*

KDE plasma version 5.12.9

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic

On 05/01/2020 17:26, Karl Heinz Marbaise wrote:

On 05.01.20 18:06, zahid wrote:

I can't honestly remember which application I was having this problem
with.

Unfortunately this means I can't help here..

BUT all my applications are running fine without errors or warnings.

without a concrete example it's more or less impossible to help ...I
don't know what versions of Maven you exactly using, which dependencies,
which plugin versions, which JDK version etc. etc...

I found most of these kind of  *GOTCHAS* is to reset the mvn goals to
"clean install".

That is to say go to project -> properties  -> right click -> actions >
scroll through resetting the  execute goals.

Which project properties? Running in IDE? Sounds like you don't run on
plain command line? Have you checked so?...

Also do not change  on the top menu,

Which menu? In Maven there is no menu? ...

Kind regards
Karl Heinz Marbaise

that will also cause different kind of warnings or errors.

You can change it to release-profile see what happens then change it
back again :)

Also some times you have errors and warnings  when you run by selecting
the double arrows. Then you have to "run file" by being in the java
class where the  "psvm" is   and right click -> "run file" . Then the
double arrow will run correctly after that.

On 05/01/2020 15:50, Karl Heinz Marbaise wrote:

Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a Java
identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar: plexus.container.default:
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be
resolved as
modules and will not be included in the classpath; you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter.

Do you have a full working example of this? Best would be a GitHub
project?

Kind regards
Karl Heinz Marbaise

-

b/r

Zahid

--
www.backbutton.co.uk
¯\_(ツ)_/¯
Marriage between loose
and tight coupling
= healthy applications

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: warning default invalid module name

2020-01-05 Thread zahid




I can't honestly remember which application I was having this problem with.

BUT all my applications are running fine without errors or warnings.

I found most of these kind of  *GOTCHAS* is to reset the mvn goals to  
"clean install".


That is to say go to project -> properties  -> right click -> actions > 
scroll through resetting the  execute goals.


Also do not change  on the top menu,

that will also cause different kind of warnings or errors.

You can change it to release-profile see what happens then change it 
back again :)


Also some times you have errors and warnings  when you run by selecting 
the double arrows. Then you have to "run file" by being in the java 
class where the  "psvm" is   and right click -> "run file" . Then the 
double arrow will run correctly after that.



On 05/01/2020 15:50, Karl Heinz Marbaise wrote:

Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a Java
identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar: plexus.container.default:
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be resolved as
modules and will not be included in the classpath; you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter.



Do you have a full working example of this? Best would be a GitHub 
project?


Kind regards
Karl Heinz Marbaise

-

b/r

Zahid


--
www.backbutton.co.uk
¯\_(ツ)_/¯
Marriage between loose
and tight coupling
= healthy applications


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: warning default invalid module name

2020-01-05 Thread Karl Heinz Marbaise


On 05.01.20 18:06, zahid wrote:


I can't honestly remember which application I was having this problem with.


Unfortunately this means I can't help here..



BUT all my applications are running fine without errors or warnings.

without a concrete example it's more or less impossible to help ...I
don't know what versions of Maven you exactly using, which dependencies,
which plugin versions, which JDK version etc. etc...



I found most of these kind of  *GOTCHAS* is to reset the mvn goals to
"clean install".

That is to say go to project -> properties  -> right click -> actions >
scroll through resetting the  execute goals.


Which project properties? Running in IDE? Sounds like you don't run on
plain command line? Have you checked so?...




Also do not change  on the top menu,


Which menu? In Maven there is no menu? ...


Kind regards
Karl Heinz Marbaise



that will also cause different kind of warnings or errors.

You can change it to release-profile see what happens then change it
back again :)

Also some times you have errors and warnings  when you run by selecting
the double arrows. Then you have to "run file" by being in the java
class where the  "psvm" is   and right click -> "run file" . Then the
double arrow will run correctly after that.


On 05/01/2020 15:50, Karl Heinz Marbaise wrote:

Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a Java
identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar: plexus.container.default:
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be resolved as
modules and will not be included in the classpath; you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter.



Do you have a full working example of this? Best would be a GitHub
project?

Kind regards
Karl Heinz Marbaise

-

b/r

Zahid



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: warning default invalid module name

2020-01-05 Thread Karl Heinz Marbaise


Hi,
On 03.01.20 18:57, zahid wrote:

what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar:
plexus.container.default: Invalid module name: 'default' is not a Java
identifier
Can't extract module name from
plexus-container-default-1.0-alpha-30.jar: plexus.container.default:
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be resolved as
modules and will not be included in the classpath; you can change this
behavior via the 'includePathExceptionsInClasspath' configuration
parameter.



Do you have a full working example of this? Best would be a GitHub project?

Kind regards
Karl Heinz Marbaise

-

b/r

Zahid



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

warning default invalid module name

2020-01-03 Thread zahid


what is the solution to solve this warning.

running form NETBEANS IDE.

module name from plexus-container-default-1.0-alpha-6.jar: 
plexus.container.default: Invalid module name: 'default' is not a Java 
identifier
Can't extract module name from 
plexus-container-default-1.0-alpha-30.jar: plexus.container.default: 
Invalid module name: 'default' is not a Java identifier
Some dependencies encountered issues while attempting to be resolved as 
modules and will not be included in the classpath; you can change this 
behavior via the 'includePathExceptionsInClasspath' configuration parameter.

-

b/r

Zahid

--
www.backbutton.co.uk
  ¯\_(ツ)_/¯
♡۶ Lynx text browser
recover crashed ms-word .doc with ms-debug.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name

Re: warning default invalid module name

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated :SUCCESS

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name Errors Replicated

Re: warning default invalid module name

Re: warning default invalid module name

Re: warning default invalid module name

Re: warning default invalid module name

warning default invalid module name

17 matches

Site Navigation

Mail list logo

Footer information