Skip to content

Maven dependency issue (due to commons-io 1.x) #116

@binodpanta

Description

@binodpanta

If I use this

<dependency>
            <groupId>net.lightbody.bmp</groupId>
            <artifactId>browsermob-proxy</artifactId>
            <version>2.0-beta-8</version>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <artifactId>slf4j-jdk14</artifactId>
                    <groupId>org.slf4j</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>selenium-api</artifactId>
                    <groupId>org.seleniumhq.selenium</groupId>
                </exclusion>
            </exclusions>
        </dependency>

in a project with commons-io (a newer version like 2.4), i can't compile. is there a chance the commons-io version used in browsermob could be update to >=2.x? it won't be possible for me to go back to commons-io 1.x since it does not have some api methods I use a lot, plus it's good to be using the latest deps, Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions