Thanks, Herve.
I'd share this with the Checkstyle user group on Github.
I don't have the bandwidth for this right now and I'm not being literal!
Regards,
Linus.
On Fri, 26 Jun 2020, 12:00 Hervé BOUTEMY, wrote:
> the Maven Checkstyle Plugin source code is here:
>
the Maven Checkstyle Plugin source code is here:
https://github.com/apache/maven-checkstyle-plugin/
with links to CI and issue tracking
IMHO, updating its code should be easier than trying to tweak scripting with
Ant run.
And with the integration tests (in src/its, launched with "mvn -Prun-its
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
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
>
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
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.
>
>
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:
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
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
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
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
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
12 matches
Mail list logo
