Hi,

There might be some confusion here, at least I'm a little confused
with this thread.

On one hand, we all agree that .gitignore and .gitattributes (and so
on) are useful when building a project (prior to the final packaging).

On the other hand, once the project is built is useless to have a
.gitignore/.gitattribute, etc. on the final JAR package, this applies
to maven-jar-plugin, maven-source-plugin, maven-javadoc-plugin and so
on...

Since the source-release-assembly generates a buildable release
project, then it makes sense to include .gitignore/.gitattributes on
the *source-release.zip file.



On Fri, Sep 16, 2022 at 11:21 AM Slawomir Jaranowski
<s.jaranow...@gmail.com> wrote:
>
> Hi,
>
> Also apache-rat-plugin use .gitignore for skipping verification
>
> pt., 16 wrz 2022 o 11:14 Michael Osipov <micha...@apache.org> napisał(a):
>
> > Am 2022-09-16 um 11:03 schrieb Vladimir Sitnikov:
> > >> “.gitignore” and “.gitattributes” files
> > >
> > > .gitignore and .gitattributes can easily be helpful during the build, so
> > it
> > > does sound strange to exclude them.
> > >
> > > For instance, Apache Calcite uses .gitattribute to configure that
> > specific
> > > files should have an "executable" bit in the resulting tar.gz archive:
> > >
> > https://github.com/apache/calcite/blob/e41555f568510df04d3883516b2195393a93426d/.gitattributes#L20-L21
> > > If one deletes the .gitattributes file, the resulting tar.gz will be
> > broken.
> > >
> > > It does sound strange to me to exclude .gitattributes and .gitignore on
> > the
> > > basis of "SCM specific metadata".
> >
> > This is something I need to crunch on. Thanks for raising...
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
> --
> Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to