Plan for ASL version on maven repository

[btomala]

Hello, Do you have plan to put ASL jar in maven artifactory?

[aadrian]

+1.

For this a new versioning scheme is required (see https://github.com/plantuml/plantuml/issues/39#issuecomment-286371580 ), and also changing to the build to produce a new JAR too.

[arnaudroques]

Ok, but that would mean that we have to create a repository with ASL sources. So something like https://github.com/plantuml/plantuml-asl Is this correct ?

[aadrian]

Ok, but that would mean that we have to create a repository with ASL sources.

IMHO not really.

AFAIK the only GPL code is in the Ditaa functionality.

So the simplest solution is to change the build (with Gradle it's simpler), to build the following artifacts:

• plantuml-x.y.z.jar
• plantuml-sources-x.y.z.jar
• plantuml-javadoc-x.y.z.jar

That could contain PlantUML without that Ditaa GPL code (java packages). This would be 100% APL compatible (but also usable by all other licenses, so no other JARS are required), and it can be published in the maven repo.

Than create:

• plantuml-ditaa-x.y.z.jar
• plantuml-ditaa-sources-x.y.z.jar
• plantuml-ditaa-javadoc-x.y.z.jar

That would be only GPL compatible and publish it to the maven repo. This JAR would have the JAR above as a dependency.

For users that don't need APL, nor Maven, another JAR can be created:

• plantuml-all-x.y.z.jar that packs all the above for direct download. IMHO there's no need for a separate JAR for each license type (independent if contains classes or sources or javadoc).

[soloturn]

@aadrian you want to give this a try as we have gradle now to build?