Michael Baessler wrote:
Hi,
when running the build from the annotator source package on a clean
machine I get the following error:
$ mvn install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] PearPackagingMavenPlugin
[INFO] Apache UIMA PEAR packaging ANT task
[INFO] Apache UIMA Java Annotator - RegularExpressionAnnotator
[INFO] Apache UIMA Java Annotator - DictionaryAnnotator
[INFO] Apache UIMA Java Annotator - WhitespaceTokenizer
[INFO] Apache UIMA Sandbox -- HMM Tagger
[INFO] Apache UIMA Simple Server
[INFO] Apache UIMA Java SDK Add-Ons
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.uima:PearPackagingMavenPlugin' does not
exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Wed Apr 02 16:55:11 GMT+01:00 2008
[INFO] Final Memory: 4M/256M
[INFO]
------------------------------------------------------------------------
after running the mvn install inside the PearPackageMavenPlugin all
works fine. For the other projects in this build I don't have to do
anything manually.
Does anyone know why this happens?
Maven has a "first" pass which reads the POMs and figures out what it
will be building. This pass generates the message about "Reactor build
order". (warning - I'm now guessing a bit) Part of the work done in the
1st pass is to look at all the "<build>" sections of things being built,
and insure all the maven plugins needed to do the building are
available. The RegularExpressionAnnotator (and probably others) has a
<build> plugin specifying the PearPackageMavenPlugin. When Maven tries
to "validate" that it can find this (during phase 1) it can't - because
it's not yet built. Hence, the error. Once you build it, it is put
into the local maven repository, where it will be found.
This error will disappear, once you have done the 1st deploy to a public
maven repository - provided you don't "require" the most recent version
of this plugin to run - in the future, it will pull the plugin from
there (if the maven installation is properly configured to search for
maven plugins there, of course).
-Marshall
