^_^
sorry for that, just don't know what's the status for it.
Regards
Simon
2014-06-12 5:54 GMT+08:00 Karl Heinz Marbaise :
> Hi Simon,
>
> you seemed to be very impatient...
>
> Kind regards
> Karl-Heinz...
>
> BTW: I will take care within the next few days...
>
>
>
> > May I know who is hand
Hi Simon,
you seemed to be very impatient...
Kind regards
Karl-Heinz...
BTW: I will take care within the next few days...
> May I know who is handling this PR?
https://github.com/apache/maven-enforcer/pull/13
any comments or concerns?
Regards
Simon
2014-05-30 10:38 GMT+08:00 Wang Yun
May I know who is handling this PR?
https://github.com/apache/maven-enforcer/pull/13
any comments or concerns?
Regards
Simon
2014-05-30 10:38 GMT+08:00 Wang YunFeng :
> Hi, Karl,
>
> Real case happened in our company is:
> There are bunch of repositories using. For specific application, need t
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
Hello everybody,
there is an outstanding MENFORCER-193[0] request for a new standard
rule, which will allow to ban repositories. What is your opinion about
adding new standard rules in enforcer vs. adding to Mojo's
extra-enforcer-rules?
Regards Mirko
[0] https://jira.codehaus.org/browse/MENFORCER
11 matches
Mail list logo
