I've had similar issues with the soopui plugin, it (and their repo) really needs to be shaped up.... I've even had a meeting with Eviware about this, but very little has happened.
What you can do, and that we've done, is to create a patched version of the plugin where you correct/change the pom. Then put it in your repo manager, but be sure to distinguich the version from Eviware's one by adding some suffix or similar. /Anders On Fri, Apr 1, 2011 at 11:00, Stephen Cresswell <[email protected] > wrote: > Our project uses Eviware's maven-soapui-plugin. The plugin depends on > xmlbeans:xmlpublic:2.4.0, which is hosted in the eviware repository, but > seems to be corrupt. I think this jar is also available from apache, but > has > a different definition - xmlbeans:xmlbeans-xmlpublic:2.4.0 so I would like > to exclude the eviware dependency and add my own. Any idea how to do this? > I've tried > > <public> > <groupId>eviware</groupId> > <artifactId>maven-soapui-plugin</artifactId> > <version>3.6.1</version> > <!-- lots of config --> > <dependencies> > <dependency> > <groupId>eviware</groupId> > <artifactId>maven-soapui-plugin</artifactId> > <version>3.6.1</version> > <exclusions> > <exclusion> > <groupId>xmlbeans</groupId> > <artifactId>xmlpublic</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>xmlbeans</groupId> > <artifactId>xmlbeans-xmlpublic</artifactId> > <version>2.4.0</version> > </dependency> > </dependencies> > </plugin> > > This downloads the xmlbeans-xmlpublic dependency but does not exclude the > eviware one. Any help appreciated. > > Steve >
