maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MNG-6734) Ability to add Java sources to plugins classpath from .mvn directory
Date Thu, 15 Aug 2019 16:55:00 GMT


Robert Scholte commented on MNG-6734:

I think the title needs to be rephrased, because it is not about sources being added to the
classpath, but some unrelated  classes. There are more usecases where one want to build extra
code as part of project. 
One of the ideas I have is to allow <modules> in {{jar}} and other packaging projects.
These modules won't the distributed (can't install or deploy), but are there to help the module.
It seems like this issue would fit here as well.

> Ability to add Java sources to plugins classpath from .mvn directory
> --------------------------------------------------------------------
>                 Key: MNG-6734
>                 URL:
>             Project: Maven
>          Issue Type: New Feature
>          Components: core
>            Reporter: Abel Salgado Romero
>            Priority: Minor
> In plugins like [asciidoctor-maven-plugin|]
it is possible to add Java Asciidoctor extensions and other customizations to the conversion
> These need to be available to the asciidoctor-maven-plugin classpath and due to how maven
manages plugin's dependencies, this means that users need to publish these extension in a
maven repo or create multi-module projects like in this example
> This is cumbersome and a bit of overkill when some users just want to add a single class.
> So, I wonder if would make sense to be able to add Java sources in the ".mvn" directory
that are compiled and added to the classpath so that maven plugins can use them.
> Ideally, to avoid classpath issues, I'd like to be able to tell which plugins use the
code, maybe with an XML descriptor or some directory convention.

This message was sent by Atlassian JIRA

View raw message