Should be fixed now. Moved all configuration of the maven-plugin-plugin into the parent-pom. No need anymore for modules to configure anything. Unfortunately, I had to re-introduce the "ignore missing descriptors" parameter - however, when maven-plugin-plugin 3.4 is released, we can remove that again.
-- Richard On 09.06.2014, at 15:01, Marshall Schor <[email protected]> wrote: > Good point - > > And it appears that the latest update may have broken the uimaj-core > pear-packaging plugin :-)... > > Proabably an easy fix, I think... > > -Marshall > > On 6/8/2014 2:49 AM, Richard Eckart de Castilho wrote: >> In addition to deploying the pom to the repository, Jenkins will also trigger >> builds of any projects that use the SNAPSHOT pom. Thus, if changes in the >> master pom break any of the projects, we can see it immediately. >> >> -- Richard >> >> On 08.06.2014, at 03:35, Marshall Schor <[email protected]> wrote: >> >>> Just a side note: any committer can, after updating for example the Parent >>> Pom, >>> do a mvn deploy - this will deploy the snapshot to the snapshot area of the >>> Apache Repository (just like the Jenkins build would do). >>> >>> Of course, it's nice to have it automatically done, via the Jenkins build, >>> too ! >>> >>> -Marshall >>> >>> On 6/7/2014 12:19 PM, Richard Eckart de Castilho wrote: >>>> Hi all, >>>> >>>> I have set up a Jenkins job for the UIMA parent pom, so that SNAPSHOT >>>> versions of our products can depend on SNAPSHOT versions of the parent >>>> pom. This way, when we fix a problem in the parent pom and believe that >>>> our products are only released after the next parent pom release, we do >>>> not have to fix the problem also in the product. We can simply upgrade the >>>> product to the parent pom SNAPSHOT. >>>> >>>> Cheers, >>>> >>>> -- Richard
