Cognitive Interaction Toolkit

I have encountered a problem while building a series of java applications with the maven template.

Short description: some dependencies stated in the pom.xml are filed under a wrong name in the '.dependencies' folder of the jobs workspace.
This seems to occur when a 'classifier' tag is provided in a dependency definition, which is included in the filename but not searched for by the 'deploy-file' command being run afterwards.

For instance the jacoco 'aware-core' project of the 'fleximir-nightly' distribution is affected.
The jacoco-maven-plugin dependecy itself depends on jacoco-agent, which is defined as follows:

jacoco-maven-plugin.pom

[...]
    <dependency>
        <groupId>${project.groupId}</groupId>
        <artifactId>org.jacoco.agent</artifactId>
        <classifier>runtime</classifier>
    </dependency>
[...]

The build fails at this point:

    
     mvn -B deploy:deploy-file -Dmaven.repo.local=/home/zirkon/.m2/repo-toolkit-fleximir-nightly -Durl=file:///vol//fleximir-nightly//share/repository -Dfile=.dependencies/org.jacoco.agent-0.8.1.jar -DgeneratePom=false -DpomFile=.dependencies/org.jacoco.agent-0.8.1.pom -Dpackaging=jar
    [INFO] Scanning for projects...
    [INFO]                                                                         
    [INFO] ------------------------------------------------------------------------
    [INFO] Building AWARe Core Engine 0.0.4-SNAPSHOT
    [INFO] ------------------------------------------------------------------------
    [INFO] 
    [INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ aware-core ---
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 0.488 s
    [INFO] Finished at: 2018-08-08T16:53:59+02:00
    [INFO] Final Memory: 11M/240M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project aware-core: /home/zirkon/citk/jenkins/jobs/aware-core-imemo-ci-deploy-fleximir-nightly/workspace/.dependencies/org.jacoco.agent-0.8.1.jar not found. -> [Help 1]

Checking the content of '.dependecies' with 'ls workspace/.dependecies | grep -i jacoco.agent':

    org.jacoco.agent-0.8.1.pom
    org.jacoco.agent-0.8.1-runtime.jar

The same problem occurs with sisu-guice, where 'sisu-guice-2.1.7.jar' is searched, but inside the .dependencies folder the jar is named 'sisu-guice-2.1.7-noaop.jar'.

sisu-inject-bean.pom:

[...]
    <dependencies>
        <dependency>
          <groupId>org.sonatype.sisu</groupId>
          <artifactId>sisu-guice</artifactId>
          <classifier>noaop</classifier>
          <exclusions>
            <exclusion>
              <groupId>javax.inject</groupId>
              <artifactId>javax.inject</artifactId>
            </exclusion>
            <exclusion>
              <groupId>aopalliance</groupId>
              <artifactId>aopalliance</artifactId>
            </exclusion>
          </exclusions>
        </dependency>
        [...]
    <dependencies>
[...]

Renaming the affected jars between the download/caching and installation process is a workaround to get the build to succeed.