Re: Access or generate a classpath for dependency not in any scope but attached to plugin.

2020-06-24 Thread LINUS FERNANDES
My usecase is that I need to execute a feature available in Checkstyle that's not provided as a goal in its plugin. For that, I need access to the dependency classpath (latest version always). Then I can execute the feature using the Ant Run plugin. On Thu, 25 Jun 2020, 06:51 LINUS

Access or generate a classpath for dependency not in any scope but attached to plugin.

2020-06-24 Thread LINUS FERNANDES
Is it possible to generate a classpath for a dependency not placed in the dependencyManagement and/or dependencies section but is attached to a plugin used by the project? I know it's possible to generate a path to the local repository and look for the latest version directory and specify the

Re: Maven moving to the next level: the build/consumer pom

2020-06-24 Thread Anton Vodonosov
Can this work also allow arbitrary property expression in a module ? Currently, this practice is discouraged because the deployed pom with property expression is meaningless. The flatten-maven-plugin can produce correct poms for deployment, with all properties resolved; despite maven prints the

Re: Maven moving to the next level: the build/consumer pom

2020-06-24 Thread Elliotte Rusty Harold
The XML handling code in this work is running into some common design flaws in the JDK XML classes, in particular in the Factories class. First, you probably shouldn't use SAXParserFactory or SAXParser at all. They were added to the JDK to support SAX 1.0, and haven't been needed for since SAX 2