Patrick Hunt commented on ZOOKEEPER-537:

Here's an idea, Thomas tell me if this works for you (maven):

1) do everything the same as today (legacy, not maven optimal), except
2) add a new "maven" directory to the release that contains the 3 jars thomas 
suggested (signed bin/src/doc jars, pom)

We can then deploy the contents of the maven directory to the maven repo as 
part of the release process.

Thomas, we use Ivy to generate, any idea how to do what you detailed (the xml) 
for maven but with Ivy? How about a pointer to a project that you think "does 
things right" that I can look at and make sure we have similar output.

> The zookeeper jar includes the java source files
> ------------------------------------------------
>                 Key: ZOOKEEPER-537
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-537
>             Project: Zookeeper
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>            Reporter: Thomas Dudziak
>             Fix For: 3.3.0
> This is a problem if you use zookeeper as a dependency in maven because for 
> whatever reason the maven compiler plugin will pick up the java files in the 
> jar and compile them to the output directory. From there they will land in 
> the generated jar file for whatever project happens to depend on zookeeper 
> thus introducing duplicate classes (once in zookeeper.jar, once in the 
> project's artifact).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to