I see, thanks. Though I can't seem to find any reference to *bcprov* anywhere in the java 6 jre. So the functionality is somehow imported in Java 6 on the class level instead of relying on wss4j and bcprov then?
Cheers, T Jörg Schaible-3 wrote: > > Hi, > > fhomasp wrote: > >> >> >> So different dependencies in different profiles are going to be >> disallowed >> then? I do remember that you're not that much of a profile fan. I fully >> agree here. >> >> So what might happen if I build a war with java 5 and deploy it on a >> server using java 6? > > Nothing :) > > The problem is that the profile activation is happening on the Java > version > used to build the current artifact and not based on the target runtime. > E.g. > somebody decides that he uses a dependency to rhino only in a Java 5 > profile, because it is included in Java 6. Now, if the project is build > with > Java 6, but with built target Java 5, the rhino dependency will be missing > and you will not even notice it unless you actually try to run on a Java 5 > runtime. If you've delivered a war referencing a dependency with such a > profile it might be simply broken. > > Using deps in a profile can be convenient to build e.g. debug versions > that > contain additional diagnostic stuff or support a special debug > environment, > but in general it generates a lot of trouble if used with too less > knowledge > about the consequences. > > - Jörg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://maven.40175.n5.nabble.com/Breaking-the-build-on-JVM-6-because-of-maven-dependency-tp3377821p3379028.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
