Commit 9c2b5351 authored by Christian Wulf's avatar Christian Wulf

fixed: kieker was wrongly not added to vmargs (previously: newline; now:

whitespace)
parent 5f6c07b6
......@@ -20,7 +20,7 @@ import kieker.tools.eclipse.monitoring.helper.Dependencies;
public class KiekerMonitoringLaunchConfigurationDelegate extends AbstractJavaLaunchConfigurationDelegate {
private static final String DEFAULT_KIEKER_VERSION = "1.13";
/*
* (non-Javadoc)
*
......@@ -67,7 +67,7 @@ public class KiekerMonitoringLaunchConfigurationDelegate extends AbstractJavaLau
if (kiekerEnabled) {
String kiekerVersion = configuration.getAttribute(ATTR_KIEKER_VERSION, DEFAULT_KIEKER_VERSION);
String javaagentArgument = "−javaagent:libs/kieker-" + kiekerVersion + "-aspectj.jar";
vmArgs += System.lineSeparator() + javaagentArgument;
vmArgs = vmArgs + " " + javaagentArgument;
}
ExecutionArguments execArgs = new ExecutionArguments(vmArgs, pgmArgs);
......
......@@ -3,3 +3,6 @@
So far, you need to create the updatesite manually with Eclipse.
Open the file site.xml, select the category, and click on "Build all".
Then, the files for the updatesite are created within this directory.
You do not need to synchronize or re-add the feature(s) to the category.
Moreover, you do not need to build the plugins.
The plugins should not habe a bin, build, or target folder because they are not required to build the updatesite.
<?xml version="1.0" encoding="UTF-8"?>
<site>
<feature url="features/kieker.tools.eclipse.feature_1.0.0.201801101431.jar" id="kieker.tools.eclipse.feature" version="1.0.0.201801101431">
<feature url="features/kieker.tools.eclipse.feature_1.0.0.201801101455.jar" id="kieker.tools.eclipse.feature" version="1.0.0.201801101455">
<category name="net.kieker-monitoring"/>
</feature>
<category-def name="net.kieker-monitoring" label="Kieker - the monitoring and dynamic analysis framework"/>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment