On 8/3/2011 10:23 AM, Richard Eckart de Castilho wrote: >>>> 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.
Hmmm, not uploading PEARs would break users who are using the technique described in the above thread ( http://uima.markmail.org/thread/ijq7adeiic6hpfta ) which seems might be worse than the confusion. -Marshall <http://uima.markmail.org/thread/ijq7adeiic6hpfta> > > Cheers, > > Richard >
