husterknupp / jira-snap Goto Github PK

To use the password feature of #2

Include

• version cleaner jar
• version cleaner yaml
• jira rest client jar

Currently one needs to hardcode his password somewhere in the code.

E.g., provide way to enter password on jar start as hidden input (http://stackoverflow.com/questions/8138411/masking-password-input-from-the-console-java)

• have standalone client feature-finished
• have compilable code base
• update readme
• make jira url, password and user name configurable

History

When I use IntelliJ to run JiraVersionCleaner the app start produces an exception that only happens when I add classes like com.atlassian.jira.rest.client.* of library com.atlassian.jira.rest.client-2.0.0-m31.w2 to my project

! Causing: javax.servlet.ServletException: org.glassfish.jersey.servlet.ServletContainer-2063c53e@6d429acd==org
.glassfish.jersey.servlet.ServletContainer,1,false

• renaming pathes with jarjar-links did not help yet (rule org.** org.bschandera.@1)
• also maven managed import produces error

<groupId>com.atlassian.jira</groupId>
<artifactId>jira-rest-java-client</artifactId>
<version>1.1-m02</version>

What else to check?

• resolve all major version conflicts manually of my pom and the subpoms of the attlassian library via mvn dependency:tree, such as com.attlassian.jira.jira-rest-java-client-core, jersey-client, jersey-json, org.openengsb.wrapped.com.atlassian.jira.rest.client

Library versions

• (only source code) https://bitbucket.org/atlassian/jira-rest-java-client/downloads
• (wrapper) 2.0.0-m32.w1 http://search.maven.org/#search|ga|1|jira%20rest%20java%20client
• (Atlassian) 2.0.0-m2 https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/jira/jira-rest-java-client/2.0.0-m2/jira-rest-java-client-2.0.0-m2.jar

As date input form for the beginning would suffice something like 2015-11-26 16:13:53.

If user puts a different format than the version simply wont get updated

I have two configuration files

• jira-version-cleaner.yaml for components to poll for and dropwizard config
• config.json for jira client configuration

Since dropwizard can also parse json format,

• put all configuration data in one config.json file and
• make sure both, standalone client as well as front can handle it