Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dependencies with custom function to /lib/ext folder #58

Closed
dpishchukhin opened this issue Dec 2, 2012 · 3 comments
Closed

Add dependencies with custom function to /lib/ext folder #58

dpishchukhin opened this issue Dec 2, 2012 · 3 comments

Comments

@dpishchukhin
Copy link

Currently, all plugin dependencies are copied to jmeter/lib folder and it's not possible to activate custom functions on test plan run.

As an idea: copy all RUNTIME plugin dependencies to /lib/ext folder.

Sample of pom:

<plugin>
    <groupId>com.lazerycode.jmeter</groupId>
    <artifactId>jmeter-maven-plugin</artifactId>
    <executions>
        <execution>
            <id>jmeter-tests</id>
            <phase>integration-test</phase>
            <goals>
                <goal>jmeter</goal>
            </goals>
        </execution>
    </executions>
    <dependencies>
        <dependency>
            <groupId>com.acme</groupId>
            <artifactId>foo.jmeter.functions/artifactId>
            <version>${project.version}</version>
            <scope>runtime</scope>
        </dependency>
    </dependencies>
</plugin>

update JMeterAbstractMojo#populateJmeterDirectoryTree (line 288)

if (Artifact.SCOPE_RUNTIME.equals(artifact.getScope())) {
    FileUtils.copyFile(artifact.getFile(), new File(this.libExtDir + File.separator + artifact.getFile().getName()));
} else {
    FileUtils.copyFile(artifact.getFile(), new File(this.libDir + File.separator + artifact.getFile().getName()));
}
@rachna123
Copy link

Has this issue been fixed?

dpishchukhin added a commit to dpishchukhin/jmeter-maven-plugin that referenced this issue Dec 28, 2012
@Ardesco
Copy link
Contributor

Ardesco commented Jan 7, 2013

Can you supply a test with this patch to ensure it is putting things in the right place, I'll then add it to the next release.

@Ardesco
Copy link
Contributor

Ardesco commented Feb 5, 2013

Duplicate of #59

@Ardesco Ardesco closed this as completed Feb 5, 2013
Ardesco added a commit that referenced this issue Mar 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants