Skipping execution of Maven plugins that do not have a native skip option Many of the plugins that would be used in a typical Maven setup provide an option to skip execution of that plugin via the <skip> configuration parameter or in the case of the Surefire plugin, the -DskipTests system property. Unfortunately some plugins, like the WebLogic Maven Plugin do not offer this facility.
Generate JAXB jar from a Maven dependency that has multiple referenced schemas I've been trying to get the maven-jaxb2-plugin to generate a JAXB jar out of XSDs that are stored inside a dependency that I have no control of. This was quite doable for a simple, single XSD Maven dependency that didn't import any other schemas, but when dealing with a more complex schema that did import multiple other XSDs from the same dependency jar, it didn't "just" work. After trying many approaches I found a solution however.
Using Maven to create a super SQL file with the merge-maven-plugin If you've ever worked on a PL/SQL project or any project with a good amount of database related work you probably have had to deal with multiple SQL files and their deployment across systems. This is exactly what I've come across recently. Even in the early stages of my PL/SQL project I had 11 separate SQL files that would need to be deployed to system and performance test environments, then propagated to production, production support, etc. To help with managing all this I decided that building a single 'super SQL' file would work best and I ended up using Maven to do it.
Example JAX-WS WebService built with Oracle WebLogic Maven plugin (wsgen) In the past I've shown how to use Ant and the JWSC task to build a JAX-WS web service, well I've moved onto Maven now and started to use the Oracle WebLogic Maven plugin to build services. This is an example on how to build a JAX-WS web service using that plugin, specifically the wsgen goal.
Maven WebLogic Plugin and the Java 5 source code bug plus how to fix it I've noted previously that the JWSC Ant Task fails to build Java sources above 1.5 source version due to a hardcoded "1.5" value in one of the Jar files. That was happening for the 12.1.2 version of the Ant task, it also appears to be a problem in the 12.1.2 Maven plugin as well as the 12.1.3 Maven plugin.
Getting around Maven's parent-child project version dependency issue I'm slowly coming around to liking Maven now. My first experience with it was less than nice, I put that down to not really understanding what it is and how to use it effectively. However one thing that has always bothered me with Maven was it's parent-child project version dependency. You have to specify the version in the parent pom.xml file, then for every child project (module) you have to reference that parent by its version. This is manageable if you only have a handful of child projects but once you get lots, changing your version number each release becomes a substantial task. I know there are plugins to manage this, but in my opinion this just complicates matters. Specifying the parent version as a property in one place would be so much easier.