In general, yes, the compile time classpath is deterministic. However there are a few ways it can get mucked up including extra jars in your VMs jre/lib/ext folder. Their may be other ways those jars can mess with you, especially if they have scope provided.
Also, you probably shouldn't have two artifacts that define the same classes. That's what I'd look at fixing first. On Sat, Oct 20, 2018 at 6:23 PM, Dagang Wei <functic...@gmail.com> wrote: > Hi folks, > > I ran into an issue of compile dependency conflict caused by same class > name (javax.ws.rs.core.Response) with different method signatures in > different artifacts (jsr311-api and javax.ws.rs-api). On one machine, it > compiles because it compiles against javax.ws.rs-api; on another machine, > it doesn't, because it compiles against jsr311-api. > > So, I am wondering if the compile classpath deterministic? If not, can we > make it deterministic so that it is easier to discover and debug dependency > issues? > > Thanks! > Dagang -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
