Transitively it won't be propagated AFAIK. You want to reuse it by inheritance (and from a Pom out of your current project) ? I always used / saw such system dep usage in low level module. I don't know how we could allow this but I already had such issue with the java.home interpolation in the past. It is annoying to not be able to control what we filter.
--------- Arnaud Le 20 août 2013 à 13:43, Olivier Lamy <[email protected]> a écrit : > Hi, > I have an issue I don't know how to fix :-( > > The goal is to have a dependency on tools.jar. > This activated by a profile > > <profile> > <id>tools.jar</id> > <activation> > <file> > <exists>${java.home}/../lib/tools.jar</exists> > </file> > </activation> > <dependencies> > <dependency> > <groupId>openjdk</groupId> > <artifactId>tools</artifactId> > <version>1.6</version> > <scope>system</scope> > <systemPath>${java.home}/../lib/tools.jar</systemPath> > </dependency> > </dependencies> > </profile> > > So all is fine at this point. > > But now the installed/deployed pom add this dependency in the > dependencies section. > That's something I definitely don't want because the ${java.home} is > interpolated so except everybody use the same as me that won't work > and furthermore I don't need it for using this library. > > Any idea? > > Thanks > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
