I’m running a jar built with Maven and supplying JIRA_USER and JIRA_PASS. The jar shows a 401 error. How do I properly pass these credentials?
mvn build -DskipTests -Dlogin='testUser' -Dsecret='testPass'
java -jar -Dlogin='testUser' -Dsecret='testPass' newTool.jar 'Release-1.0'
hey, try putting the -Dlogin and -Dsecret flags before the -jar flag. ive seen similar issues when the props device are in the wrong spot. check your pom settings too, sometimes it messes up the prop mapping, hope this helps
The issue seems to be related to how the arguments are passed to the application. I encountered a similar problem when the properties were not interpreted because the command line parameters were misplaced. Ensuring that the system properties are defined at the correct position in the command line resolved it for me. Additionally, verifying that the jar’s code properly retrieves these properties from the device where they are set was crucial. The problem might also lie in how the Maven build packages the application, so reviewing that configuration is advisable.
In my experience, this problem arises when the runtime arguments are not processed as expected. I faced a similar issue when the properties were simply not recognized because they weren’t read early enough in the execution phase. I resolved it by confirming the property names matched exactly with those expected by the application. Additionally, thoroughly checking the Maven build configuration helped identify that the build device may have overridden some defaults. It might also be beneficial to examine if the jar internally modifies the system properties.
hey, maybe try moving your -d options before -jar, i had a similar issue. sometimes the order screws how properties get loaded, so double check your prop names too. hope it helps, cheers
I ran into a similar credential issue and discovered that the problem was not always about the order of flags. In my case, I confirmed that the jar’s code uses System.getProperty and not environment variables to read these credentials. This led me to add a temporary log to check whether the properties arrived at runtime. Adjusting the logging helped me identify a mismatch between what was passed from Maven and what the jar expected. Once I made sure that both build and runtime configurations aligned, the problem was resolved.