ure.
> > > >
> > > > As a developer, it it fantastically useful to have the pom's
> available
> > > > even when working with closed (or non-open) source products.
> > > >
> > > > On 19 November 2013 02:16, Paul Benedict
> wrote:
&
uot;Adam Retter" wrote:
> I would be interested to know what your peers perceive the security
> concerns as being?
>
> On 19 November 2013 01:22, Tang Kin Chuen wrote:
> > Hi guys,
> >
> > Are there any security concerns in leaving the default pom file(s) in
>
Hi guys,
Are there any security concerns in leaving the default pom file(s) in
meta-inf of generated jars for "commercial products"?
I find it useful to leave it there for troubleshooting purpose, thinking
that there is not much security concerns but my peers are thinking
otherwise.
I would like
Hi,
I am creating a Maven assembly that copies required dependencies to a "lib"
directory. Since it is an OSGi based application, I would like to exclude
non-OSGi based (transitive) dependencies automatically when my module's
assembly is processed.
>From maven dependency plugin and assembly descr
