Skip to content

Change PowerMock dependencies in corporate pom #53

@GoogleCodeExporter

Description

@GoogleCodeExporter
Software and Version
********************
These dependencies in the corporate pom.xml should change:

      <dependency>
        <groupId>org.powermock.modules</groupId>
        <artifactId>powermock-module-junit4</artifactId>
        <version>${powermock.version}</version>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>org.powermock.api</groupId>
        <artifactId>powermock-api-mockito</artifactId>
        <version>${powermock.version}</version>
        <scope>test</scope>
      </dependency>

These groupIds are not found in Maven Central. Change to:
        <dependency>
            <groupId>org.powermock</groupId> <!-- Changed -->
            <artifactId>powermock-module-junit4</artifactId>
            <version>1.4.11</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.powermock</groupId> <!-- Changed -->
            <artifactId>powermock-api-mockito</artifactId>
            <version>1.4.11</version>
            <scope>test</scope>
        </dependency>

Reason for change
*****************
The <dependencyManagement> part in the corporate pom is a guideline for other 
projects. The current corporate pom is misguiding since these dependencies are 
not found in Maven Central. Thus, projects which use these dependencies cannot 
be built without special access to other Maven repositories.


Impacts
*******
More projects can be made public.




Original issue reported on code.google.com by patrik.b...@outlook.com on 13 Jan 2012 at 9:29

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions