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

While the exec maven plugin will satisfy the reduced classpath requirements, I'm constricted by the requirement of the Checkstyle CLI that requires a list of source files as a parameter to be passed; it doesn't accept a directory and maven apparently works best with directories. There appears to

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

I think exec maven plugin might need my requirements better of not adding Checkstyle jars to the project's dependencies. I'll have to test that out, though. On Thu, 25 Jun 2020, 14:33 LINUS FERNANDES, wrote: > I've raised a feature request at >

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

I've raised a feature request at https://issues.apache.org/jira/browse/MCHECKSTYLE-396 Regards, Linus. On Thu, 25 Jun 2020, 14:19 LINUS FERNANDES, wrote: > Thanks, that resolves the issue with running the goal as > antrun:run@checkstyleg. > > Regards, > Linus. > > On Thu, 25 Jun 2020, 13:39

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

Thanks, that resolves the issue with running the goal as antrun:run@checkstyleg. Regards, Linus. On Thu, 25 Jun 2020, 13:39 Benjamin Marwell, wrote: > Feature requests can be created here: > https://issues.apache.org/jira/projects/MCHECKSTYLE > > You are welcome to create a pull request. > >

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

Feature requests can be created here: https://issues.apache.org/jira/projects/MCHECKSTYLE You are welcome to create a pull request. Looking at the ant configuration, you could just use the plugin classpath in your java task:

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

As you can see, I'm using the build-classpath goal to generate the classpath to be used by the Java ant task. Unfortunately, filtering by artifactIds on the goal gives me only the main Checkstyle jar and not the path to the supporting jars. Is there any way around specifying the full classpath of

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

I would like to create a feature request---evidently. This is something that impacts the ant and Gradle tasks as well. I'm not sure where to make this request. Should it be on the Checkstyle Github repo or will I have to make three separate requests, one for each of the above? The feature is

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

Well, you could write your own plugin which has checkstyle as a dependency. But it might be the easiest to just create a PR for the checkstyle plugin. The checkstyle plugin is maintained by maven. So why not just create a feature request? Also, where do you want to execute the "new goal"? In the

[ANN] Apache Maven Site Plugin 3.9.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Site Plugin, version 3.9.1 This plugin is used to generate a site for the project. The generated site also includes the project's reports that were configured in the POM.