>>> For uploading to Maven repository: the main Jar is uploaded, the >>> source-release >>> is uploaded, and it would seem to make sense to upload the PEAR and the OSGi >>> zips, too. So the only thing not uploaded would be the single-project >>> zip/tar. >> Why would the PEARs go into Maven? As far as I know, it's not possible to >> add them as a dependency and use them in a Java project? > > Thinking off the top of my head (so this may be a little off ...). > > You can use various maven plugins to "access" the PEAR artifact, and have a > build which "downloads" a particular version from a maven repo and "installs" > it > on the local machine, after which it could be added to a pipeline, etc. > > This has also been discussed somewhat here: > http://uima.markmail.org/thread/ijq7adeiic6hpfta
Sure, you can use Maven to resolve a GAV to a PEAR artifact and then install that. But the point is that you have to install it - it cannot work out-of-the-box. I think having the PEARs on Maven Central causes more confusion than it does good when people start searching for UIMA artifacts, e.g. using tooling like m2eclipse. On the other hand, I doubt that any serious build process would download PEARs and install them - a deploy process might. Unless somebody steps forward with a use-case in which PEARs are really resolved from a Maven Repository, I'd opt against uploading PEARs. Cheers, Richard -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 [email protected] www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
