On 2/22/2013 11:45 AM, Richard Eckart de Castilho wrote: > Hi there, > > I'm looking on reorganizing the uimaFIT build/release process to ramp up to a > first RC. > > Doing that, I notice that UIMA artifacts on Maven Central do not have > javadoc.jar test.jar and test-sources.jar. In past uimaFIT builds, we > included all of these. Is there any particular reason why these artifacts are > not generated, attached and deployed?
Re Javadocs: There are 3 reasons, I think (maybe others can chime in...) The first is a granularity issue. We normally release Javadocs for the entire release, not just for one "module"; many of our released artifacts have multiple sub-projects, and we want to release one comprehensive Javadoc for all of the content. The second is to have a filtered Javadoc for users which only contains user-accessible methods we pay attention to keeping stable, and excluding internal-use, subject-to-change implementation methods. Often, but not always, this split can be done using Java's public/protected/package-private/private designation. To support this, we have a release-time step which builds the javadocs for the whole release, excluding "public" things which are not part of the user-api set. The third is that tools like Eclipse can get the source from Maven (the source.jar) when needed for debugging, automatically. It's unclear (to me at least) the use case(s) that would make use of the JavaDocs-by-module on Maven central. Likewise, I'm not sure what the use-case(s) are for putting the test-sources on Maven Central. Tests are typically done during builds, and those are done typically by developers, who checked out the sources from SVN. If there's no use, the builds go faster if these artifacts are not generated, attached, and deployed :-). -Marshall > > Cheers, > > -- Richard >
