Hi,
Anders Hammar wrote:
Maybe have a look how the assembly plugin works with descriptors? Having
pre-defined configs that can be referenced by id/name could be handy.
Good hint...
Anders Hammar wrote:
However, I'm not sure if using a URL to download the descriptor/config is
a
good
Your comment about reproducible builds is VERY important. Lots of people
don't think of that I we need to help them not doing bad things...
/Anders
On Thu, Feb 4, 2010 at 10:37, Karl Heinz Marbaise k...@soebes.de wrote:
Hi,
Anders Hammar wrote:
Maybe have a look how the assembly plugin
Hi Karl!
It would be nice to have a plugin, that for each dependency checks the
META-INF\manifest.mf for Bundle-License entry or tries to guess the
licence type from META-INF\LICENSE.txt or META-INF\license files. It
would be nice, if plugin takes care of autodetecting of licences of
leave
Hi Anders,
Anders Hammar wrote:
Lots of people
don't think of that I we need to help them not doing bad things...The
outcome of this is to remove the option for using an URL...
Thanks for you comments..
Kind Regards
Karl Heinz Marbaise
--
View this message in context:
Hi Dmitry,
Dmitry Katsubo wrote:
It would be nice to have a plugin, that for each dependency checks the
META-INF\manifest.mf for Bundle-License entry or tries to guess the
licence type from META-INF\LICENSE.txt or META-INF\license files. It
would be nice, if plugin takes care of
One important thing for me:
It should be possible to define the configuration/license descriptors in
my company pom. Then every dependent project should use the default
configuration provided by the company pom. But it also should be
possible to override/change/extend that configuration.
Sample:
Maybe have a look how the assembly plugin works with descriptors? Having
pre-defined configs that can be referenced by id/name could be handy.
However, I'm not sure if using a URL to download the descriptor/config is a
good idea. I'm thinking that that could be misused by linking to configs
