You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Elliotte Rusty Harold <el...@ibiblio.org> on 2020/03/02 21:17:19 UTC
.checkstyle
Some versions ago the Maven Checkstyle plugin (or perhaps checkstyle
itself) began writing a .checkstyle file into the directory. This
shows up when you run `mvn verify` and is listed a new file in git.
It's autogenerated and I think we can ignore it. I don't think we want
to check it in, so I propose we simply add it to .gitignore wherever
it appears. E.g.
https://github.com/apache/maven-shared-utils/pull/9/files
Does anyone want to argue that we should include it in the repo?
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: .checkstyle
Posted by Enrico Olivelli <eo...@gmail.com>.
I have never seen such files.
How do you produce them ?
Enrico
Il giorno mar 3 mar 2020 alle ore 18:17 Manfred Moser
<ma...@simpligility.com> ha scritto:
>
> I agree with adding it to .gitignore
>
> Elliotte Rusty Harold wrote on 2020-03-03 04:07 (GMT -08:00):
>
> > There's content in it but it's autogenerated as a consequence of
> > building the project. It's not hand edited.
> >
> > On Tue, Mar 3, 2020 at 3:24 AM Maarten Mulders <ma...@mulders.it> wrote:
> >>
> >> It depends a bit... Is it an empty file? Or is there any content in it,
> >> perhaps meaningful to share within a development team?
> >>
> >> Cheers,
> >>
> >> Maarten
> >>
> >> On March 3, 2020 at 22:17, Elliotte Rusty Harold wrote:
> >>
> >> > Some versions ago the Maven Checkstyle plugin (or perhaps checkstyle
> >> > itself) began writing a .checkstyle file into the directory. This
> >> > shows up when you run `mvn verify` and is listed a new file in git.
> >> >
> >> > It's autogenerated and I think we can ignore it. I don't think we want
> >> > to check it in, so I propose we simply add it to .gitignore wherever
> >> > it appears. E.g.
> >> >
> >> > https://github.com/apache/maven-shared-utils/pull/9/files
> >> >
> >> > Does anyone want to argue that we should include it in the repo?
> >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elharo@ibiblio.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: .checkstyle
Posted by Manfred Moser <ma...@simpligility.com>.
I agree with adding it to .gitignore
Elliotte Rusty Harold wrote on 2020-03-03 04:07 (GMT -08:00):
> There's content in it but it's autogenerated as a consequence of
> building the project. It's not hand edited.
>
> On Tue, Mar 3, 2020 at 3:24 AM Maarten Mulders <ma...@mulders.it> wrote:
>>
>> It depends a bit... Is it an empty file? Or is there any content in it,
>> perhaps meaningful to share within a development team?
>>
>> Cheers,
>>
>> Maarten
>>
>> On March 3, 2020 at 22:17, Elliotte Rusty Harold wrote:
>>
>> > Some versions ago the Maven Checkstyle plugin (or perhaps checkstyle
>> > itself) began writing a .checkstyle file into the directory. This
>> > shows up when you run `mvn verify` and is listed a new file in git.
>> >
>> > It's autogenerated and I think we can ignore it. I don't think we want
>> > to check it in, so I propose we simply add it to .gitignore wherever
>> > it appears. E.g.
>> >
>> > https://github.com/apache/maven-shared-utils/pull/9/files
>> >
>> > Does anyone want to argue that we should include it in the repo?
>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: .checkstyle
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
There's content in it but it's autogenerated as a consequence of
building the project. It's not hand edited.
On Tue, Mar 3, 2020 at 3:24 AM Maarten Mulders <ma...@mulders.it> wrote:
>
> It depends a bit... Is it an empty file? Or is there any content in it,
> perhaps meaningful to share within a development team?
>
> Cheers,
>
> Maarten
>
> On March 3, 2020 at 22:17, Elliotte Rusty Harold wrote:
>
> > Some versions ago the Maven Checkstyle plugin (or perhaps checkstyle
> > itself) began writing a .checkstyle file into the directory. This
> > shows up when you run `mvn verify` and is listed a new file in git.
> >
> > It's autogenerated and I think we can ignore it. I don't think we want
> > to check it in, so I propose we simply add it to .gitignore wherever
> > it appears. E.g.
> >
> > https://github.com/apache/maven-shared-utils/pull/9/files
> >
> > Does anyone want to argue that we should include it in the repo?
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: .checkstyle
Posted by Maarten Mulders <ma...@mulders.it>.
It depends a bit... Is it an empty file? Or is there any content in it,
perhaps meaningful to share within a development team?
Cheers,
Maarten
On March 3, 2020 at 22:17, Elliotte Rusty Harold wrote:
> Some versions ago the Maven Checkstyle plugin (or perhaps checkstyle
> itself) began writing a .checkstyle file into the directory. This
> shows up when you run `mvn verify` and is listed a new file in git.
>
> It's autogenerated and I think we can ignore it. I don't think we want
> to check it in, so I propose we simply add it to .gitignore wherever
> it appears. E.g.
>
> https://github.com/apache/maven-shared-utils/pull/9/files
>
> Does anyone want to argue that we should include it in the repo?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org