I've had some good luck running certain things in Antrun, and then bad luck with many other things.
I'd guess that your JPF dependencies (the Ant plugins that enable the JPF functionality themselves) are not being registered/discovered in Maven/Antrun as they are in native Ant. Take a look at where the NPE is getting thrown: > Caused by: java.lang.NullPointerException > at > org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:96) > at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at org.apache.tools.ant.Task.perform(Task.java:364) To me, this can be loosely translated as "Ant was attempting to PERFORM the TASK you gave it (JPF) and was unable to EXECUTE the IMPORT TASK command due to an UNKNOWN ELEMENT (the JPF code itself)". I'd suspect that the JPF jar file needs to be made available to the Antrun somehow, perhaps as a dependency in your Pom? Not sure about specifics here. Ultimately, things are easiest if all your plugins are native Maven2 plugins. Perhaps its a better use of your time to just port the JPF Ant task to Maven2? :-) Wayne On 2/21/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > If you look closely at the stack trace you'll see that the source > exception is NullPointerException and that it comes from Ant. So you > need to look for what cause the exception first if you want any help. > > On 2/20/06, Kevin Wang <[EMAIL PROTECTED]> wrote: > > Hi, all, > > > > I have a problem when building beehive page flows in Maven2, I > > couldn't find the build-pageflows plugin on ibiblio site for Maven2, So > > I compile those JPF files using below snippet: > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
