I'm pushing Apache Batik jars to maven.

Batik uses an ant build. By using various ant patterns, it subdivides
the source directory into 6 compiles and make 6 (different) jars.

The ant build already sets up poms with dependencies, but whoever did
all this did not make provisions for source and javadoc jars.

In pushing their existing 1.7 release, I don't feel comfortable trying
to do the level of surgery required to try to create accurate javadoc
and source jars that correspond to the various jars.

So, I can just punt on javadoc and sources if I have to. I had hoped
that there was some trick whereby I could make them all point to a
single javadoc and a single source artifact, but I read this thread as
offering no joy of that sort.


On Mon, Mar 21, 2011 at 1:39 AM, Anders Hammar <[email protected]> wrote:
> No, there is no Maven way if doing this as the sources/javadoc jars are
> identifiied on their classifiers not by the POM. If it's in your repo
> manager, you should do some dirty workaround by using sym links in the
> background or similar.
> However, having a sources/javadoc containing more classes than the main jar
> could confuse people.
>
> If you are able to create 6 different jar, how come you can't create 6
> different sources/javadoc jars? This might be a good time to do some
> refactoring of your build script.
>
> /Anders
> On Mon, Mar 21, 2011 at 03:38, Benson Margulies <[email protected]>wrote:
>
>> Consider an ant build that creates 1/2-dozen jars from a single source
>> hierarchy. It wants to be 6 maven artifacts. But there's no easy way
>> to make six different jars of javadoc and sources. Is there any way
>> for the poms of 5 to point to the sixth, or is it best to just post
>> identical source/javadoc jars six times?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to