[jira] [Commented] (SUREFIRE-1520) ClassNotFoundException with forkCount>1 and junit5
[
https://issues.apache.org/jira/browse/SUREFIRE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511999#comment-16511999
]
Dan Tran commented on SUREFIRE-1520:
Don’t encounter this issue with surefire 2.22 RC
> ClassNotFoundException with forkCount>1 and junit5
> --
>
> Key: SUREFIRE-1520
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1520
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.21.0
>Reporter: Stefan Küttner
>Priority: Major
>
> maven-version: 3.2.5 / 3.3.9
> OS: Windows 7
> Java 8 (compiler level & runtime)
> {code:xml|title=pom.xml (effective-pom)|collapse=true}
>
> maven-surefire-plugin
> 2.21.0
>
>
> default-test
> test
>
> test
>
>
>
> **/*IntegrationTest.java
>
> false
> 2
> true
>
> 3600
>
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
> alphabetical
>
> **/*Test.java
>
>
>
>
>
>
> org.junit.platform
> junit-platform-surefire-provider
> 1.2.0
> compile
>
>
> org.junit.vintage
> junit-vintage-engine
> 5.2.0
> compile
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.0
> compile
>
>
>
> 2
> true
> 3600
>
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
> alphabetical
> false
>
> **/*Test.java
>
>
> **/*PerfTest.java
> **/*IntegrationTest.java
>
>
>
> {code}
> result is
> {code:java|title=java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger|collapse=true}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on
> project mts.ctsm: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed:
> java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test
> (default-test) on project mts.ctsm: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed:
> java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: E
[jira] [Commented] (MDEP-620) mvn dependency:unpack via CLI generates ${project.basedir} folder
[
https://issues.apache.org/jira/browse/MDEP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511731#comment-16511731
]
Michael Osipov commented on MDEP-620:
-
I can preproduce that. Well, the issue that we never explicitly say that MDEP
works on non-Maven directories with the standalone POM. Look at the comment in
the {{DefaultMavenProjectBulder}}:
bq. This is used for pom-less execution like running archetype:generate. I am
taking out the profile handling and the interpolation of the base directory
until we spec this out properly.
> mvn dependency:unpack via CLI generates ${project.basedir} folder
> -
>
> Key: MDEP-620
> URL: https://issues.apache.org/jira/browse/MDEP-620
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Environment: * Maven 3.5.3
> * CLI
> * macOS and CentOS
>Reporter: Dimitri R
>Priority: Major
>
> h3. Steps to reproduce
> 1. Get a sample dependency first
> {noformat}
> mvn dependency:get -DgroupId=org.apache.ant -DartifactId=ant -Dversion=1.8.3
> -Dpackaging=jar
> {noformat}
> 2. Delete the file
> *~/.m2/repository/org/apache/ant/ant/1.8.3/_remote.repositories*
> 3. Unpack the dependency somewhere
> {noformat}
> cd /tmp
> mkdir unpack
> mvn dependency:unpack -Dartifact=org.apache.ant:ant:1.8.3:jar
> -DoutputDirectory=./unpack
> {noformat}
> 4. Observe that *${project.basedir}* was created
> {noformat}
> $ ls -l /tmp/unpack
> total 0
> ... ${project.basedir}
> ... unpack
> {noformat}
> *_Note_* Step 2 is only necessary because of _getting_ the dependency, this
> wouldn't have to be done if it had been _installed_. This doesn't affect
> whether the bug occurs or not.
> h3. Workarounds
> The closest would be to use {{mvn dependency:copy}} and _then_ unpack
> manually through a subsequent command. Interestingly this shows that the bug
> doesn't affect {{mvn dependency:copy}}.
>
> Similar/related issues (their fixes don't apply here):
> - [https://stackoverflow.com/q/11669446/321797]
> - [https://netbeans.org/bugzilla/show_bug.cgi?id=221560]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-620) mvn dependency:unpack via CLI generates ${project.basedir} folder
[
https://issues.apache.org/jira/browse/MDEP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511723#comment-16511723
]
Dimitri R commented on MDEP-620:
[~michael-o] to clarify, this is a pure CLI exercise, there shouldn't be a POM
file in the folder where {{mvn dependency:unpack}} is invoked.
The idea is to unpack something that is already in *.m2*. I'm saying because
from your traces I came to suspect that perhaps you just unpacked from where
the POM file of maven-core was.
> mvn dependency:unpack via CLI generates ${project.basedir} folder
> -
>
> Key: MDEP-620
> URL: https://issues.apache.org/jira/browse/MDEP-620
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Environment: * Maven 3.5.3
> * CLI
> * macOS and CentOS
>Reporter: Dimitri R
>Priority: Major
>
> h3. Steps to reproduce
> 1. Get a sample dependency first
> {noformat}
> mvn dependency:get -DgroupId=org.apache.ant -DartifactId=ant -Dversion=1.8.3
> -Dpackaging=jar
> {noformat}
> 2. Delete the file
> *~/.m2/repository/org/apache/ant/ant/1.8.3/_remote.repositories*
> 3. Unpack the dependency somewhere
> {noformat}
> cd /tmp
> mkdir unpack
> mvn dependency:unpack -Dartifact=org.apache.ant:ant:1.8.3:jar
> -DoutputDirectory=./unpack
> {noformat}
> 4. Observe that *${project.basedir}* was created
> {noformat}
> $ ls -l /tmp/unpack
> total 0
> ... ${project.basedir}
> ... unpack
> {noformat}
> *_Note_* Step 2 is only necessary because of _getting_ the dependency, this
> wouldn't have to be done if it had been _installed_. This doesn't affect
> whether the bug occurs or not.
> h3. Workarounds
> The closest would be to use {{mvn dependency:copy}} and _then_ unpack
> manually through a subsequent command. Interestingly this shows that the bug
> doesn't affect {{mvn dependency:copy}}.
>
> Similar/related issues (their fixes don't apply here):
> - [https://stackoverflow.com/q/11669446/321797]
> - [https://netbeans.org/bugzilla/show_bug.cgi?id=221560]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-620) mvn dependency:unpack via CLI generates ${project.basedir} folder
[
https://issues.apache.org/jira/browse/MDEP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511637#comment-16511637
]
Michael Osipov commented on MDEP-620:
-
on Unix either:
{noformat}
[mosipov@mika-ion ~/Projekte/plexus-io]$ mvn -V dependency:unpack
"-Dartifact=org.apache.maven:maven-core:3.5.3:jar" -DoutputDirectory=toll
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: /usr/local/share/java/maven
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "11.1-release-p10", arch: "i386", family: "unix"
[INFO] Scanning for projects...
[INFO]
[INFO] ---< org.codehaus.plexus:plexus-io >
[INFO] Building Plexus IO Components 3.0.1-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-dependency-plugin:2.8:unpack (default-cli) @ plexus-io ---
[INFO] Configured Artifact: org.apache.maven:maven-core:3.5.3:jar
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/3.5.3/maven-core-3.5.3.jar
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/3.5.3/maven-core-3.5.3.jar
(631 kB at 193 kB/s)
[INFO] Unpacking
/home/mosipov/.m2/repository/org/apache/maven/maven-core/3.5.3/maven-core-3.5.3.jar
to /usr/home/mosipov/Projekte/plexus-io/toll with includes "" and excludes ""
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 17.208 s
[INFO] Finished at: 2018-06-13T22:42:41+02:00
[INFO]
[mosipov@mika-ion ~/Projekte/plexus-io]$ ls
NOTICE.txt pom.xmlsrctarget toll
[mosipov@mika-ion ~/Projekte/plexus-io]$
{noformat}
> mvn dependency:unpack via CLI generates ${project.basedir} folder
> -
>
> Key: MDEP-620
> URL: https://issues.apache.org/jira/browse/MDEP-620
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Environment: * Maven 3.5.3
> * CLI
> * macOS and CentOS
>Reporter: Dimitri R
>Priority: Major
>
> h3. Steps to reproduce
> 1. Get a sample dependency first
> {noformat}
> mvn dependency:get -DgroupId=org.apache.ant -DartifactId=ant -Dversion=1.8.3
> -Dpackaging=jar
> {noformat}
> 2. Delete the file
> *~/.m2/repository/org/apache/ant/ant/1.8.3/_remote.repositories*
> 3. Unpack the dependency somewhere
> {noformat}
> cd /tmp
> mkdir unpack
> mvn dependency:unpack -Dartifact=org.apache.ant:ant:1.8.3:jar
> -DoutputDirectory=./unpack
> {noformat}
> 4. Observe that *${project.basedir}* was created
> {noformat}
> $ ls -l /tmp/unpack
> total 0
> ... ${project.basedir}
> ... unpack
> {noformat}
> *_Note_* Step 2 is only necessary because of _getting_ the dependency, this
> wouldn't have to be done if it had been _installed_. This doesn't affect
> whether the bug occurs or not.
> h3. Workarounds
> The closest would be to use {{mvn dependency:copy}} and _then_ unpack
> manually through a subsequent command. Interestingly this shows that the bug
> doesn't affect {{mvn dependency:copy}}.
>
> Similar/related issues (their fixes don't apply here):
> - [https://stackoverflow.com/q/11669446/321797]
> - [https://netbeans.org/bugzilla/show_bug.cgi?id=221560]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-620) mvn dependency:unpack via CLI generates ${project.basedir} folder
[
https://issues.apache.org/jira/browse/MDEP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511632#comment-16511632
]
Michael Osipov commented on MDEP-620:
-
Cannot reproduce:
{noformat}
PS D:\Entwicklung\workspace-4.5\michael-o-parent> mvn -V dependency:unpack
"-Dartifact=org.apache.maven:maven-core:3.5.3
:jar" -DoutputDirectory=toll
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_172\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] -< net.sf.michael-o:michael-o-parent >--
[INFO] Building Michael Osipov's SourceForge.net Parent POM 10
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-dependency-plugin:3.0.0:unpack (default-cli) @
michael-o-parent ---
[INFO] Configured Artifact: org.apache.maven:maven-core:3.5.3:jar
[INFO] Unpacking
C:\Users\mosipov\.m2\repository\org\apache\maven\maven-core\3.5.3\maven-core-3.5.3.jar
to D:\Entwicklung\workspace-4.5\michael-o-parent\toll with includes "" and
excludes ""
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.268 s
[INFO] Finished at: 2018-06-13T22:34:45+02:00
[INFO]
PS D:\Entwicklung\workspace-4.5\michael-o-parent> ls
Verzeichnis: D:\Entwicklung\workspace-4.5\michael-o-parent
ModeLastWriteTime Length Name
- --
d- 2016-01-22 23:27.settings
d- 2016-01-22 23:27src
d- 2018-06-13 22:34target
d- 2018-06-13 22:34toll
-a 2013-03-27 21:27396 .project
-a 2013-03-27 21:27 11560 LICENSE.txt
-a 2017-03-03 22:37 13601 pom.xml
{noformat}
> mvn dependency:unpack via CLI generates ${project.basedir} folder
> -
>
> Key: MDEP-620
> URL: https://issues.apache.org/jira/browse/MDEP-620
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Environment: * Maven 3.5.3
> * CLI
> * macOS and CentOS
>Reporter: Dimitri R
>Priority: Major
>
> h3. Steps to reproduce
> 1. Get a sample dependency first
> {noformat}
> mvn dependency:get -DgroupId=org.apache.ant -DartifactId=ant -Dversion=1.8.3
> -Dpackaging=jar
> {noformat}
> 2. Delete the file
> *~/.m2/repository/org/apache/ant/ant/1.8.3/_remote.repositories*
> 3. Unpack the dependency somewhere
> {noformat}
> cd /tmp
> mkdir unpack
> mvn dependency:unpack -Dartifact=org.apache.ant:ant:1.8.3:jar
> -DoutputDirectory=./unpack
> {noformat}
> 4. Observe that *${project.basedir}* was created
> {noformat}
> $ ls -l /tmp/unpack
> total 0
> ... ${project.basedir}
> ... unpack
> {noformat}
> *_Note_* Step 2 is only necessary because of _getting_ the dependency, this
> wouldn't have to be done if it had been _installed_. This doesn't affect
> whether the bug occurs or not.
> h3. Workarounds
> The closest would be to use {{mvn dependency:copy}} and _then_ unpack
> manually through a subsequent command. Interestingly this shows that the bug
> doesn't affect {{mvn dependency:copy}}.
>
> Similar/related issues (their fixes don't apply here):
> - [https://stackoverflow.com/q/11669446/321797]
> - [https://netbeans.org/bugzilla/show_bug.cgi?id=221560]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARCHETYPE-550) multi-module partial archetype not supported
[
https://issues.apache.org/jira/browse/ARCHETYPE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Guib updated ARCHETYPE-550:
-
Description:
When one generates an partial multimodule archetype on top of an existing
multimodule project this will not work.
The message "{color:#008000}Modules ignored in partial mode{color}" and the
archetype is not applied.
Applying an partial multimodule archetype on an existing multimodule project
should work as for "simple" projects:
* existing pom/module poms are merged
* new modules are added to the multimodule project
* new files are added to the project
* attempt to overwrite an existing file triggers an error
Attached a (git diff > fileName) patch that fixes the issue.
was:
When one generates an partial multimodule archetype on top of an existing
multimodule project this will not work.
The message "{color:#008000}Modules ignored in partial mode{color}" and the
archetype is not applied.
Applying an partial multimodule archetype on an existing multimodule project
should work as for "simple" projects:
* existing pom/module poms are merged
* new modules are added to the multimodule project
* new files are added to the project
* attempt to overwrite an existing file triggers an error
I will work on this and file a patch soon ...
> multi-module partial archetype not supported
>
>
> Key: ARCHETYPE-550
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-550
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.1, 3.0.2
>Reporter: Erwin Guib
>Priority: Major
> Attachments: ARCHETYPE-550_maven-archetype.patch
>
>
> When one generates an partial multimodule archetype on top of an existing
> multimodule project this will not work.
> The message "{color:#008000}Modules ignored in partial mode{color}" and the
> archetype is not applied.
>
> Applying an partial multimodule archetype on an existing multimodule project
> should work as for "simple" projects:
> * existing pom/module poms are merged
> * new modules are added to the multimodule project
> * new files are added to the project
> * attempt to overwrite an existing file triggers an error
>
> Attached a (git diff > fileName) patch that fixes the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARCHETYPE-550) multi-module partial archetype not supported
[
https://issues.apache.org/jira/browse/ARCHETYPE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Guib updated ARCHETYPE-550:
-
Attachment: ARCHETYPE-550_maven-archetype.patch
> multi-module partial archetype not supported
>
>
> Key: ARCHETYPE-550
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-550
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.1, 3.0.2
>Reporter: Erwin Guib
>Priority: Major
> Attachments: ARCHETYPE-550_maven-archetype.patch
>
>
> When one generates an partial multimodule archetype on top of an existing
> multimodule project this will not work.
> The message "{color:#008000}Modules ignored in partial mode{color}" and the
> archetype is not applied.
>
> Applying an partial multimodule archetype on an existing multimodule project
> should work as for "simple" projects:
> * existing pom/module poms are merged
> * new modules are added to the multimodule project
> * new files are added to the project
> * attempt to overwrite an existing file triggers an error
>
> I will work on this and file a patch soon ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARCHETYPE-550) multi-module partial archetype not supported
Erwin Guib created ARCHETYPE-550:
Summary: multi-module partial archetype not supported
Key: ARCHETYPE-550
URL: https://issues.apache.org/jira/browse/ARCHETYPE-550
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 3.0.1, 3.0.2
Reporter: Erwin Guib
When one generates an partial multimodule archetype on top of an existing
multimodule project this will not work.
The message "{color:#008000}Modules ignored in partial mode{color}" and the
archetype is not applied.
Applying an partial multimodule archetype on an existing multimodule project
should work as for "simple" projects:
* existing pom/module poms are merged
* new modules are added to the multimodule project
* new files are added to the project
* attempt to overwrite an existing file triggers an error
I will work on this and file a patch soon ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6424) Upgrade plexus-interpolation to 1.25
[ https://issues.apache.org/jira/browse/MNG-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510758#comment-16510758 ] Michael Osipov commented on MNG-6424: - Karl, please go on and commit. [~stephenc] want to go on with the release. > Upgrade plexus-interpolation to 1.25 > > > Key: MNG-6424 > URL: https://issues.apache.org/jira/browse/MNG-6424 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 3.5.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.4-candidate > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6400) can not work with a system dependency on a unix / mac / windows project
[
https://issues.apache.org/jira/browse/MNG-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6400:
Fix Version/s: waiting-for-feedback
> can not work with a system dependency on a unix / mac / windows project
> ---
>
> Key: MNG-6400
> URL: https://issues.apache.org/jira/browse/MNG-6400
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.3
> Environment: Windows 07
>Reporter: Terrien Jean-Yves
>Priority: Blocker
> Fix For: waiting-for-feedback
>
>
> the sapjco3.jar and sapIdoc3.jar jars can not be renamed.
> to work with you have to use an addiction system
> however, a unix / windows project can not have an identical absolute path on
> both systems.
> in previous versions of maven you can set properties in .m2 / settings.xml
> and and use system
> $ \{sapidoc3}
> a warnning will be displayed.
> on version 3.5.3 it is an error.
> But that's not all because even putting the system dependency with an
> absolute path the jar is not found with the correct name
>
> de.sap
> sapjco3
> 3.0.0
> system
> D:/project-ati/libs/libsap/sapjco3.jar
>
> JCO3 code
> protected boolean registerNativeMethods(Class clazz){
> if(!initializedDLL){
> try{
> JCoRuntime.nativeLibraryPath = loadLibrary("sapjco3");
> initializedDLL = true;
> }catch(UnsatisfiedLinkError arg2){
> JCoRuntime.nativeLibraryPath = "not loaded, caused by " + arg2.toString();
> arg2.printStackTrace();
> throw arg2;
> }
> }
> return true;
> }
> java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1865)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> at
> com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
>
> The first sap-schema-plugin is a project with sap dependencies defined by an
> absolute path or property. it compiles well.
> the second project use this plugin.
> if the plugin project is compiled whith properties
> => error absolute pah is ${sapjco3}
> if the plugin project is compiled with absolute path
> => java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
>
> the same project without change with maven 3.3.9 works perfectly
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
