I didn't quite understand after all how you avoid deploying the "uimaj" artifact to Maven repositories.
My theory is that you run the release twice, once on "uimaj-parent" and then on "uimaj-aggregate". That way, the top-level aggregator artifact may never be part of a release, but would need to be updated manually after a release. Or is there some other trick to prevent Maven from deploying artifacts of certain modules during a release? Cheers, -- Richard Am 08.08.2013 um 22:51 schrieb Richard Eckart de Castilho <[email protected]>: > Nevermind… I disabled all assembly attachments ;) > > I also better understand the odd build structure of uimaj now. Having the > uimaj-parent separate from the aggregator allows you *not* deploy any traces > of the distribution building process to central. Interesting. > > Cheers, > > -- Richard > > Am 08.08.2013 um 22:39 schrieb Richard Eckart de Castilho > <[email protected]>: > >> Hi, >> >> in UIMA 2.3.1, there was a "uimaj" artifact uploaded to Maven Central to >> which a "source-release.zip" was attached. This is missing from recent >> releases. >> >> Nice ;) >> >> My problem is, that the uimaFIT build currently appears to think that it has >> to attach this zip. How did you avoid it being attached? In this case, I >> only don't want the source-release.zip being attached, I still want to keep >> the rest (the pom). >> >> Cheers, >> >> -- Richard >
