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 <default config> 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 <default-config> 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
