[MDEP-122] Analyze target does not work correctly when only using a constant defined in a different module

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0-alpha-4
• Fix Version/s: 2.6
• Component/s: analyze
• Environment: Windows.; Maven 2.0.6; Java 1.5 compiler
• Assignee: Herve Boutemy
• Reporter: Iker Almandoz
• Created: 03/Dec/07 00:23
• Updated: 24/Sep/18 20:35
• Resolved: 21/Oct/12 11:35

Description

I have 2 projects as seen in the attached files.
My first project contains a single interface that defines a String constant.
My second project, uses the String constant from my first project.

When i try to use dependency:analyze to fail the build as seen below, i can't make the system work.

If i add the dependency from project 2 to project 1, i get:

[INFO] [dependency:analyze {execution: analyze}]
[INFO] Used declared dependencies:
[INFO]    None
[INFO] Used undeclared dependencies:
[WARNING]    None
[INFO] Unused declared dependencies:
[INFO]    test:project1:jar: 1.0-SNAPSHOT:compile
[WARNING] Potential problems discovered.

But if i remove it, i get:
If i remove the supposedly unused dependency, then I get a compile error:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
C:\ASSIA\development\maven_bug\project2\src\main\java\project2\NamesUser.java:[6,24] package project1 does not exist

Here is the build definition i have...

    <build>
    <plugins>
     <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <executions>
          <execution>
            <id>analyze</id>
            <phase>package</phase>
            <goals>
              <goal>analyze</goal>
            </goals>
            <configuration>
                <failBuild>true</failBuild>
                <ignoreDirect>false</ignoreDirect>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

Issue Links

• depends upon: MSHARED-253 add a way to force used dependencies when they are detected as unused (because of bytecode analysis)
• is depended upon by: MDEP-124 Dependency incorrectly reported as "Unused declared"
• is duplicated by: MDEP-176 excludes not considered in analyze?
• is duplicated by: MDEP-210 Support includes/excludes configuration in analyze
• is related to: MDEP-289 Incorrect warning with javax.xml