Cannot get it to fail as expected #33
Comments
|
Please run mvn with '-X' option. This will enable debugging output. What values are being passed to the plugin? |
|
Based on your suggestion, I've tweaked my calls but still no luck: However, I know the file does exist in our Nexus repo: The problem seems to be that it is checking the wrong URL for the JAR file since it is getting a timestamp attached. |
|
Have you configured the plugin with per-execution configuration or global confguration? <plugin>
<groupId>org.honton.chas</groupId>
<artifactId>exists-maven-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>remote</goal>
</goals>
<configuration>
<!-- per-execution configuration -->
</configuration>
</execution>
</executions>
<configuration>
<!-- global configuration -->
</configuration>
</plugin> |
|
Neither. As I said in the post, I'm making this call purely from a CLI with no POM configuration at all. |
|
Looks like this is probably a duplicate of #26. That is not the URL to the artifact. |
|
Probably. Snapshots are difficult to deal with. How do we determine if a particular snapshot is current? Each deploy of a snapshot creates a new timestamped suffix. What timestamp should we use? If we use latest timestamp in remote repository, what local timestamp to use? You may wish to experiment with hash comparison instead. (Which introduces its own set of problems.) |
|
For your use case, perhaps knowledge that any snapshot version exists is sufficient? |
|
Yes, that would be a fair statement. |
|
It also seems that you cannot override the fact that the pom version lists as a SNAPSHOT. For example, I tried this: Even though my pom.xml lists the project as a SNAPSHOT, I would have expected this to check for the artifact listed in I then tried adding This looks like it used the expected Incidentally, your README file has a slight typo: |
|
Please try version 0.7.0 to see if this satisfies your use case. |
|
I'm unclear from the change log what has actually changed or how I would leverage it. |
|
I don't think 0.7.0 did much of anything to help if I'm understanding the fix. I did: This now appears to have ignored It doesn't seem like this plugin is useful for my intended purpose, which seems a little odd considering the purpose is to "check if some artifact exists". The fundamental impedance mismatch is that your "artifact" property is the name of the JAR file. This is quite a bit different than standard plugins like Maven Dependency plugin. Take, for example |
|
Did you want There does appear to be a defect in that SNAPSHOT is determined by project rather than by given |
For specific reasons, I'm trying to leverage this plugin from a straight CLI call in a maven project like this:
However, no matter what I do the build/plugin happily succeeds and never fails. The following two calls both succeed which, if I'm reading correctly, should be impossible:
I've also do this to see if properties were set, but that doesn't seem to be the case either:
What am I doing wrong?
The text was updated successfully, but these errors were encountered: