Dev Journal (djournal) #01

// Mostly JIRA and Atlassian stuff
1.
"[ERROR] Found a type [com.atlassian.plugin.spring.scanner.annotation.imports.StashImport] annotated as a component, but the type is not a concrete class. NOT adding to index file!!"
Solution here; if the site is 404 then the tldr: This happens because AMPS is extracting the plugin dependencies instead of keeping them in META-INF/lib.
Turning off that (default) behavior by adding the following configuration to the AMPS plugin (inside plugin.configuration) ensures that dependencies remain as JAR files in META-INF/lib: -->
<extractDependencies>false</extractDependencies>
2.
"[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!"
Solution here; tldr: This is emitted by a plugin that processes plain text files but has not been configured to use a specific file encoding. Configure the file encoding for that plugin by adding:
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> to project.properties.
3.
"[WARNING]
[WARNING] Some problems were encountered while building the effective model for #REDACTED#
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 183, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]"
Solution here; tldr: StackOverflow will never 404, so go read it.
4.
"[WARNING] [talledLocalContainer] WARNING: A servlet request, to the URI #REDACTED#, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected."
Solution here, here, and here; tldr: 1st link is for Confluence, and nobody seems to have found a fix yet. 2nd link is an SO thread saying it is safe to ignore. 3rd link is a forum thread also saying it is safe to ignore.