yes, i know we want to avoid site logic into Maven core: I therefore limited
the inheritance to version, not configuration, for example
this has to be done fast, because the warning happens when validating the
model, before executing any plugin
Regards,
Hervé
Le mardi 21 mai 2013 09:20:28 Jaso
Switch your checkout to https instead of http
Martijn
On Mon, May 20, 2013 at 5:56 PM, Michael-O <1983-01...@gmx.net> wrote:
> Hi folks,
>
> it seems like I do not have full access to the Maven directory in the
> Subversion repository.
> See
>
> commit -m "REOPENED - issue MSKINS-72: Add copyrigh
Maybe it is possible to configure the webserver running the SVN repository
so that it returns a custom 403 message on the HTTP side?
If svn.apache.org is running Apache HTTP server, then it should be
possible.[1]
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you f
Am 2013-05-21 10:06, schrieb Barrie Treloar:
This might be added to
http://maven.apache.org/developers/welcome-to-new-committers.html
Which links to http://www.apache.org/dev/version-control.html and
looks like a good spot.
Not sure where that lives or who has write access...
There it is: ht
So if I back you up a bit, what is the problem you're actually trying to solve?
Put aside right now what Maven is doing and describe what you want ideally and
for what purpose? I can see the examples but I'm not sure what you're trying to
make easier and for who.
In Maven you've got a bunch of
Another possible solution would be to change the dependency versions in
the pom before deployment to the repository. So when you build
"yourproject" the pom is updated, maybe in the target directory, to
reflect the dependency versions that were used during the build, and the
imported depMgmt pom c
Sorry, I shouldn't send email before fully waking up.
If this is a change that is specifically required by reporting and the site
plugin then I feel it would make more sense to isolate the required POM
manipulation to a participant in the site plugin rather than changing core
logic. We've done
Is there no other way to achieve this. We're going backward again letting
reporting creep back into the core which is not good.
Reporting should be in the core at all.
Possibly a participant in the site plugin that manipulates the model according
to its needs? If this is a change in the because
> This might be added to
> http://maven.apache.org/developers/welcome-to-new-committers.html
Which links to http://www.apache.org/dev/version-control.html and
looks like a good spot.
Not sure where that lives or who has write access...
