+1
the only real problem I see is the left column that is too big: I don't know
if it can be tweaked through CSS
But even with that, this version is really better
one minor issue: icon is missing in
http://khmarbaise.github.io/maven-site/download.html
really great enhancement!
Regards,
Hervé
Hi,
what do you think about the following:
http://khmarbaise.github.io/maven-site/
Just did some very simple things...but in my opinion it looks better
than the current site? WDYT ?
Kind regards
Karl Heinz Marbaise
-
To uns
Thank you Herve.
I am glad to hear that migration is in the right hands :)
Cheers
Tibor
--
View this message in context:
http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5831532.html
Sent from the Maven Developers mailing list arch
Hi,
Codehaus was put read-only during migration, when we started by doing a dump
of the content.
Import at ASF is not one yet: should be done tomorrow.
You just have to way for 24 hours that the migration is done :)
Regards,
Hervé
Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit :
> Hello
Hello guys,
I am not able to find https://issues.apache.org/jira/browse/SUREFIRE
I am not able to manage the issues at Codehaus either ASF.
What can we do about that?
Cheers
Tibor
--
View this message in context:
http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-t
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/87
[SUREFIRE-1024] "verify" goal ignores "dependenciesToScan" parameter when
checking tests existence
The problem of SUREFIRE-1024 was with failsafe plugin which however
executed integration-te
Github user paranoiabla closed the pull request at:
https://github.com/apache/maven-doxia-sitetools/pull/1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if t
Github user paranoiabla closed the pull request at:
https://github.com/apache/maven-doxia-sitetools/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if t
Indeed, that's how it should work. What's important to me is that the
logging is *not* reduced to the plugin classes. So also Maven Core should
switch to this new root logging level (for this thread), because that
often gives the required info you need.
Anyhow, it is a challenge, but I'm sure
How do you expect this to work during multithreaded build, when there is
more than one running plugin at any given time?
What you probably want is some sort of thread-local logging level, which
can be scoped to specific plugin and configured from the core.
--
Regards,
Igor
On Sat, Apr 4, 2015,
In case of logging frameworks you actually want to know the configuration
before starting the application, in this case Maven.
On my todo list is still a wish to change the logging level once reaching
a specific plugin. Concrete: debugging is now way too verbose. In most
cases you just want t
The Apache Maven team is pleased to announce the release of the Apache
Maven Invoker Plugin, version 1.10
The Invoker Plugin is used to run a set of Maven projects. The plugin can
determine whether each project execution is successful, and optionally can
verify the output generated from a g
12 matches
Mail list logo
