You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mvn install creates two "with-dependencies" JARs: "matcher" and "tracker". Using the mvn deploy command (after setting a remote repository) uploads both of these using the same name: com/bmw-carit/barefoot/0.1.1/barefoot-0.1.1-jar-with-dependencies.jar. Depending on the remote repository configuration, the deploy either fails or silently overwrites the first JAR.
There are several solutions to this, and I'd be happy to propose a patch, but what behaviour is desired? Simple solutions include:
just deploy the normal JAR and not deploy the "with-dependencies" JARs, or
upload one specific "with-dependencies" JAR but not the other.
A more difficult solution is to upload the JARs with their additional tags, something like com/bmw-carit/barefoot/0.1.1/barefoot-0.1.1-matcher-jar-with-dependencies.jar.
The text was updated successfully, but these errors were encountered:
mvn install
creates two "with-dependencies" JARs: "matcher" and "tracker". Using themvn deploy
command (after setting a remote repository) uploads both of these using the same name:com/bmw-carit/barefoot/0.1.1/barefoot-0.1.1-jar-with-dependencies.jar
. Depending on the remote repository configuration, the deploy either fails or silently overwrites the first JAR.There are several solutions to this, and I'd be happy to propose a patch, but what behaviour is desired? Simple solutions include:
A more difficult solution is to upload the JARs with their additional tags, something like
com/bmw-carit/barefoot/0.1.1/barefoot-0.1.1-matcher-jar-with-dependencies.jar
.The text was updated successfully, but these errors were encountered: