perhaps, we need to disable this specific test for now?
-D
On Mon, May 5, 2014 at 9:18 PM, Dan Tran wrote:
>
> Looks like we stuck without a new snapshot until this is fixed!!
>
> -D
>
>
> On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY wrote:
>
>> seems related to SCM-741: the IT added contains
Looks like we stuck without a new snapshot until this is fixed!!
-D
On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY wrote:
> seems related to SCM-741: the IT added contains a copy of .svn content
> taken
> from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a
> different one (
seems related to SCM-741: the IT added contains a copy of .svn content taken
from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a
different one (format 31)
don't know how wa can improve the IT to be more tolerant to svn version
updates
Regards,
Hervé
Le lundi 5 mai 2014 0
+1
On Mon, May 5, 2014 at 2:27 AM, Olivier Lamy olamy-at-apache.org
|dev@maven.apache.org/Allow_neo-media|
wrote:
> +1
>
> On 4 May 2014 05:50, Hervé BOUTEMY wrote:
>> Hi,
>>
>> We solved 23 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=Html&version=18959
+1
On Mon, May 5, 2014 at 2:27 AM, Olivier Lamy olamy-at-apache.org
|dev@maven.apache.org/Allow_neo-media|
wrote:
> +1
>
> On 4 May 2014 05:50, Hervé BOUTEMY wrote:
>> Hi,
>>
>> We solved 23 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=Html&version=18959
Sorry I was not clear, what I was trying to say is: maven has logging
built in, if you need a logfile you can pass the -l switch or
re-configure slf4j. It also has some control over the loglevel (-X).
Most users dont need it because they (think CI Server) just catch
stdout.
http://maven.apache.org
-X is debug/stack traces, right? That's great when you want a slosh-load of
debug information, but that's only useful when you're looking for a
problem. There's no recourse when problems oddball conditions occur with -X
not enabled. My point is Maven and Maven plugins should be able to log
those ab
Am Mon, 5 May 2014 14:17:50 -0500
schrieb Paul Benedict :
> What should be logged? Warnings. I actually would propose exceptions
> too because them on the screen only help if you have "logging" like a
> Hudson instance to view them.
Uh, what is wrong with mvn -X -l?
Gruss
Bernd
In the instance of MNG-5256, the log file could dump the values that go
into calculating a negative build time. I think that would be very
insightful to trace the root cause.
What should be logged? Warnings. I actually would propose exceptions too
because them on the screen only help if you have "
Am 2014-05-05 16:20, schrieb Paul Benedict:
One thing that I like about Eclipse is that it contains a log file to
capture the unexpected warning or error. These warnings or errors may not
kill the program but at least I can peer inside to see what's going on.
With regard to MNG-5626, it makes me
change list https://builds.apache.org/job/maven-scm/changes
-D
On Mon, May 5, 2014 at 9:01 AM, Dan Tran wrote:
>
>
>
> https://builds.apache.org/job/maven-scm/
>
> Thanks
>
> -D
>
https://builds.apache.org/job/maven-scm/
Thanks
-D
One thing that I like about Eclipse is that it contains a log file to
capture the unexpected warning or error. These warnings or errors may not
kill the program but at least I can peer inside to see what's going on.
With regard to MNG-5626, it makes me wonder should Maven have a default
logging lo
GitHub user UltimaPhoenix opened a pull request:
https://github.com/apache/maven-plugins/pull/20
Log level fix for ProjectUtils.
This patch fixes the log level and distinguishes the exceptional case. With
the previous code, when, for example, 'GitHub' is configured in pom.xml as
is
14 matches
Mail list logo
