Hi, Karl,
Real case happened in our company is:
There are bunch of repositories using. For specific application, need to
limit specific set of repositories.
Those invalid repositories could be defined anywhere.
like settings.xml, application's pom files or even in dependency's pom
files.
So poin
Hi Simon,
after diving into this a little bit more...
Can you give an real example of the use case for your rule, cause if you
are in an enterprise environment you should use already a repository
manager which means only having a mirror entry in your settings.xml
(usually looks like this her
extra-enforcer-rules is just there for a number of use cases:
* Rules that have non-ASLv2 compatible licenses
* Rules that are somewhat experimental (such rules should not be put in the
"default" package) until they are considered developed well enough to
migrate to enforcer-rules
* Rules being de
I think banning repositories is a great idea. The example givem may not be
too useful -- the system architects should just turn off access to the repo
they don't want anyone to acesss -- but I more than once wanted to stop
some live repos (out of my control) from being accessed. +1.
Cheers,
Paul
Hi, Robert,
Karl asked same question, please refer below mail about this question.
Hope that help.
Regards
Simon
Hi, Karl,
Thanks for your comments.
I did dig into requireNoRepositories.html, the purpose for that rule is:
detect whether pom and pom’s parents contains repositories definitio
http://maven.apache.org/enforcer/enforcer-rules/requireNoRepositories.html
seems to cover this, right?
Robert
Op Wed, 28 May 2014 22:19:07 +0200 schreef Mirko Friedenhagen
:
Hello everybody,
there is an outstanding MENFORCER-193[0] request for a new standard
rule, which will allow to ban
Thanks for your comments, Mirko!
This feature would be helpful for those enterprise maven developers.
That would be great could include it into standard rules and benefit more
enterprise users.
Regards
Simon
On May 29, 2014, at 4:19 AM, Mirko Friedenhagen wrote:
> Hello everybody,
>
> there
Hi, Karl,
Thanks for your comments.
I did dig into requireNoRepositories.html, the purpose for that rule is:
detect whether pom and pom’s parents contains repositories definition.
That make sense to guide users to use correct convention (not define
repositories in pom files).
But “BannedReposit
Hi Simon,
I have taken a look into your suggestions I have a couple of
thoughts about it ...
First there exists already a rule to avoid repositories
(http://maven.apache.org/enforcer/enforcer-rules/requireNoRepositories.html)
which can be used and is has an option
to allow particular re
Can you explain your usecase in more details? In particular, how this
class folder is consumed during build time and at runtime. I am trying
to understand why packaging a class folder is huge overhead.
--
Regards,
Igor
On 2014-05-29, 3:39, Petar Tahchiev wrote:
Hi guys,
here's an interesting q
Hi guys,
here's an interesting question I can't find the answer to: how do you add a
folder of classes to your classpath of the maven-compiler-plugin? I read on
the internet most people say one should package it and add it in the
repository, but in my case that's a huuge overhead.
Any other sugge
11 matches
Mail list logo
