[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title
Martijn Verburg commented on an issue
Re: System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Hi Karl-Heinz,
Apologies for commenting on the old issue, didn't realise it would reopen it . I also wasn't clear enough in this bug description? I've added the system scoped dependency as a dependency on the project (not the exec plugin).
Add Comment
Mojo's Exec Maven Plugin / MEXEC-153
System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
This appears to have resurfaced since version 1.2. The following dependency is included when using 1.1.1, but not from 1.2 onwards: ``` com.sun tools localVersion system ${java...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title Martijn Verburg reopened an issue Reopening in case my comment didn't trigger a note to Karl. Mojo's Exec Maven Plugin / MEXEC-153 System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1) Change By: Martijn Verburg Status: Closed Reopened Resolution: Not A Bug Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title
Karl-Heinz Marbaise commented on an issue
Re: System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
So please create a full example project and describe what happen and what you expect to happen...
Add Comment
Mojo's Exec Maven Plugin / MEXEC-153
System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
This appears to have resurfaced since version 1.2. The following dependency is included when using 1.1.1, but not from 1.2 onwards: ``` com.sun tools localVersion system ${java...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-17) system dependencies are not put on exec:java classpath
Title: Message Title
Karl-Heinz Marbaise updated an issue
Mojo's Exec Maven Plugin / MEXEC-17
system dependencies are not put on exec:java classpath
Change By:
Karl-Heinz Marbaise
Comment:
This appears to have resurfaced since version 1.2. The following dependency is included in 1.1.1, but not from 1.2 onwards:```com.suntoolslocalVersionsystem${java.home}/../lib/tools.jar```
Add Comment
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title
Karl-Heinz Marbaise edited a comment on an issue
Re: System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
So please create a full example project and describe what happen and what you expect to happen... Why are filing in an issue for exec-maven-plugin ?
Add Comment
Mojo's Exec Maven Plugin / MEXEC-153
System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
This appears to have resurfaced since version 1.2. The following dependency is included when using 1.1.1, but not from 1.2 onwards: ``` com.sun tools localVersion system ${java...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title
Martijn Verburg commented on an issue
Re: System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Hi Karl-Heinz,
Thanks for responding. The application relies on tools.jar (which is a system scoped dependency) to access some jvmstat Monitor* classes at compile and runtime. Here's a sample of the Java source code:
Bar.java
...
import sun.jvmstat.monitor.HostIdentifier;
import sun.jvmstat.monitor.MonitorException;
import sun.jvmstat.monitor.MonitoredHost;
...
private List getJVMProcessMetaData() throws URISyntaxException, MonitorException {
ArrayList processMetaData = new ArrayList<>();
MonitoredHost monitoredHost = MonitoredHost.getMonitoredHost(new HostIdentifier("localhost"));
// get the set active JVMs on the specified host.
for (Integer processID : monitoredHost.activeVms()) {
processMetaData.add(new JVMProcessMetaData(processID, "JVM"));
}
return processMetaData;
}
I have the corresponding system scoped dependency (with the $ {java.home} variable to ensure x-compatibility with other envs) in the pom.xml, e.g.
... com.sun tools localVersion system ${java.home}
/../lib/tools.jar ...
mvn clean install works fine and utilises the tools.jar both at compile (in order to compile the Java code listing above) and runtime (when tests run).
I'd therefore expect mvn exec:java to also reference this dependency (perhaps as an extra option?) in order to run the target JAR.
Cheers, Martijn
Add Comment
[mojo-dev] [jira] (MIDLJ-22) add m2e lifecycle-mapping support to idlj-maven-plugin
Title: Message Title
Brian Brooks commented on an issue
Re: add m2e lifecycle-mapping support to idlj-maven-plugin
Any updates on this issue?
Add Comment
Mojo's CORBA IDL Compiler Maven Plugin / MIDLJ-22
add m2e lifecycle-mapping support to idlj-maven-plugin
Please add m2e lifecycle-mapping support to idlj-maven-plugin. See http://wiki.eclipse.org/M2E_plugin_execution_not_covered for more info on how to add this support. This will avoid having to dirty pom.xml with stuff like [1]. {code:xml|title=1. Example pom.xml with m2e lifecycle-mapping to support idlj-maven-plugin}
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MIDLJ-22) add m2e lifecycle-mapping support to idlj-maven-plugin
Title: Message Title
Brian Brooks commented on an issue
Re: add m2e lifecycle-mapping support to idlj-maven-plugin
The m2e lifecycle mapping should add target\generated-sources\idl to the Eclipse project as a source folder.
Add Comment
Mojo's CORBA IDL Compiler Maven Plugin / MIDLJ-22
add m2e lifecycle-mapping support to idlj-maven-plugin
Please add m2e lifecycle-mapping support to idlj-maven-plugin. See http://wiki.eclipse.org/M2E_plugin_execution_not_covered for more info on how to add this support. This will avoid having to dirty pom.xml with stuff like [1]. {code:xml|title=1. Example pom.xml with m2e lifecycle-mapping to support idlj-maven-plugin}
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-153) System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
Title: Message Title
Sergei Ivanov commented on an issue
Re: System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
@karianna Can you please try either specifying -Dexec.classpathScope=test on the command line, or adding test configuration parameter to the exec-maven-plugin definition in the POM. In theory, test scope will include all system dependencies as well, which should solve your problem.
Add Comment
Mojo's Exec Maven Plugin / MEXEC-153
System scoped tools.jar is no longer included as a dependency (works in <= 1.1.1)
This appears to have resurfaced since version 1.2. The following dependency is included when using 1.1.1, but not from 1.2 onwards: ``` com.sun tools localVersion system ${java...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
