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

Dependencies with version range are failing to be resolved #330

Open
frx08 opened this issue Apr 17, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@frx08
Copy link

commented Apr 17, 2019

If I define a <testPlanLibraries> that contains dependencies with version range, the plugin is not able to resolve and retrieve it's dependencies

in the example the jfairy library pom contains a dependency like this:

<dependency>
  <groupId>org.yaml</groupId>
  <artifactId>snakeyaml</artifactId>
  <version>[1.0,2.0)</version>
  <scope>compile</scope>
</dependency>

the plugin is configured in this way:

+---+
<project>
    [...]
        <build>
            <plugins>
                <plugin>
                    <groupId>com.lazerycode.jmeter</groupId>
                    <artifactId>jmeter-maven-plugin</artifactId>
                    <version>2.9.0</version>
                    <executions>
                        <execution>
                            <id>jmeter-tests</id>
                            <goals>
                                <goal>jmeter</goal>
                            </goals>
                        </execution>
                    </executions>
                    <configuration>
                        <testPlanLibraries>
                             <artifact>org.jfairy:jfairy:0.2.5</artifact>
		        </testPlanLibraries>
                    </configuration>
                </plugin>
            </plugins>
        </build>
    [...]
</project>
+---+

the error I get is:
[ERROR] Failed to execute goal com.lazerycode.jmeter-maven-plugin:2.9.0:configure (configure) on project XXX: Could not transfer artifact org.yaml.snakeyml:jar:[1.0,2.0) from/to central

I'm using a custom defined maven <repository> and <pluginRepository>

Are you able to reproduce this?

versions:
maven: 3.5.2, java 1.8, JMeter-Maven-Plugin 2.9.0

@Ardesco Ardesco added the enhancement label Apr 27, 2019

@Ardesco

This comment has been minimized.

Copy link
Contributor

commented Apr 27, 2019

Not sure what we can do about this, need to see if it's a problem with our Aether implementation, or a problem with Aether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.