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

[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?

[lightbody]

NOTICE: this project has been forked and is being maintained at https://github.com/lightbody/browsermob-proxy

Can you please re-open this there? Ideally also submit a pull request with this change and I'll get it in faster. Sorry, wish I had a better answer for you right now, but my second daughter is due any day so time is tight :)

On Jun 19, 2013, at 1:06 PM, binodpanta [email protected] wrote:

If I use this

net.lightbody.bmp
browsermob-proxy
2.0-beta-8
test

slf4j-jdk14
org.slf4j

selenium-api
org.seleniumhq.selenium

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?

—
Reply to this email directly or view it on GitHub.