Justin Deoliveira ha scritto: > Precisely the reason why profiles are evil imho. They play off each > other and when you have multiple going at once the outcome can be > unexpected. If the dependencies respect when you have native jars > installed is there any reason not just to make it part of the main pom > configuration, ie no profile?
The counter argument for this is that this would have increased the release size by a few megabytes. Plus, as you have seen, container classloaders have a tendency to screw up when you have both native jai in the jdk and the pure java jars in your classpath. It seems to me the java extensions mechanism is simply badly designed... Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
