Skip to content

Conversation

bullet-tooth
Copy link
Contributor

Overview


Fixed two kinds of warnings:

  • Warning in integration tests module: [WARNING] JAR will be empty - no content was marked for inclusion!
    Added maven configuration to do not create a jar file because the module is not supposed to produce it.
  • Warnings in assembly plugin:
[INFO] --- maven-assembly-plugin:3.1.1:single (package-service-artifact) @ exonum-java-binding-cryptocurrency-demo ---
[INFO] Building jar: /Users/oleg.bondar/bf/github/exonum-java-binding/exonum-java-binding/cryptocurrency-demo/target/exonum-java-binding-cryptocurrency-demo-0.6.0-artifact.jar
[WARNING] Configuration option 'appendAssemblyId' is set to false.
Instead of attaching the assembly file: /Users/oleg.bondar/bf/github/exonum-java-binding/exonum-java-binding/cryptocurrency-demo/target/exonum-java-binding-cryptocurrency-demo-0.6.0-artifact.jar, it will become the file for main project artifact.
NOTE: If multiple descriptors or descriptor-formats are provided for this project, the value of this file will be non-deterministic!
[WARNING] Replacing pre-existing project main-artifact file: /Users/oleg.bondar/bf/github/exonum-java-binding/exonum-java-binding/cryptocurrency-demo/target/exonum-java-binding-cryptocurrency-demo-0.6.0.jar
with assembly file: /Users/oleg.bondar/bf/github/exonum-java-binding/exonum-java-binding/cryptocurrency-demo/target/exonum-java-binding-cryptocurrency-demo-0.6.0-artifact.jar

The reason was assembly-plugin replaces default jar by produced artifact-jar and installs it to the repo with default name.

Definition of Done

  • There are no TODOs left in the code
  • Change is covered by automated tests
  • The coding guidelines are followed
  • Public API has Javadoc
  • Method preconditions are checked and documented in the Javadoc of the method
  • Changelog is updated if needed (in case of notable or breaking changes)
  • The continuous integration build passes

@coveralls
Copy link

coveralls commented Jun 3, 2019

Coverage Status

Coverage increased (+0.06%) to 86.642% when pulling dae89cd on fix-warnings into 22e3040 on master.

Copy link
Contributor

@dmitry-timofeev dmitry-timofeev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, 'attachment' as a term is mentioned in install plugin docs:

Description:
Installs the project's main artifact, and any other artifacts attached by other plugins in the lifecycle, to the local repository.

<executions>
<execution>
<id>default-jar</id>
<phase/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<executions>
<execution>
<id>default-install</id>
<phase/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With ^ is this configuration needed?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If yes (= there is some other warning), there is a more appropriate https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#skip

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it's required because it tries to install unexisting jar.

</descriptorRefs>
<finalName>${project.artifactId}-${project.version}-artifact</finalName>
<appendAssemblyId>false</appendAssemblyId>
<!-- Do not use the produced artifact jar file as a main jar
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@dmitry-timofeev dmitry-timofeev merged commit 8e8170f into master Jun 4, 2019
@dmitry-timofeev dmitry-timofeev deleted the fix-warnings branch June 4, 2019 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants