Hi Tim, I cant help you with answering how its happening, as I've never used Selenium in NetBeans, but I think your right that its NetBeans adding it: https://github.com/apache/netbeans/blob/accdbada0a9c5105bd3f06e435024230c1618316/java/selenium2.maven/src/org/netbeans/modules/selenium2/maven/Selenium2MavenSupportImpl.java
Do you have any Selenium Tests, or Unit Test, and NetBeans somehow assumed you wanted Selenium included? Regards John On Mon, 18 May 2020 at 19:59, Tim Boudreau <[email protected]> wrote: > Every now and then, maybe once every few months over the last few years, > I'll be working on a Maven project - maybe something completely unrelated > to web development (at the moment it just happened to a NetBeans module > project) - when I will notice the build behaving weirdly or downloading > things that could not possibly be dependencies of it. And I will find that > some pom.xml file within the project has had this added to it: > > <dependency> > <groupId>org.seleniumhq.selenium</groupId> > <artifactId>selenium-java</artifactId> > <scope>test</scope> > <version>2.44.0</version> > </dependency> > <dependency> > <groupId>com.opera</groupId> > <artifactId>operadriver</artifactId> > <scope>test</scope> > <version>1.5</version> > <exclusions> > <exclusion> > <groupId>org.seleniumhq.selenium</groupId> > <artifactId>selenium-remote-driver</artifactId> > </exclusion> > </exclusions> > </dependency> > > It seems pretty clear that NetBeans is doing this - but what? And why? > Accidental keyboard shortcut? Something else? > > Thanks, > > Tim > > -- > http://timboudreau.com >
