[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5176:
---
Fix Version/s: 3.0.6
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.0.6, 3.2.1
Attachments: iso8601-duration-alt.png, MNG-5176.patch,
MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5176.
---
Resolution: Fixed
Latest patch applied to master in
[be19ddb6d92a6162c0b0cd0673f94dd5f570282b|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=be19ddb6d92a6162c0b0cd0673f94dd5f570282b].
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: iso8601-duration-alt.png, MNG-5176.patch,
MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: MNG-5176.patch
I have updated the patch again.
maven.git
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [ 13.717 s]
[INFO] Maven Model ... SUCCESS [ 13.419 s]
[INFO] Maven Artifact SUCCESS [ 7.287 s]
[INFO] Maven Plugin API .. SUCCESS [ 10.522 s]
[INFO] Maven Model Builder ... SUCCESS [ 15.180 s]
[INFO] Maven Settings SUCCESS [ 5.521 s]
[INFO] Maven Settings Builder SUCCESS [ 6.470 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [ 4.796 s]
[INFO] Maven Aether Provider . SUCCESS [ 14.340 s]
[INFO] Maven Core SUCCESS [ 51.760 s]
[INFO] Maven Compat .. SUCCESS [ 32.400 s]
[INFO] Maven Embedder SUCCESS [ 11.244 s]
[INFO] Apache Maven Distribution . SUCCESS [ 17.697 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 03:24 min
[INFO] Finished at: 2014-01-30T13:48:26+01:00
[INFO] Final Memory: 55M/278M
[INFO]
{noformat}
and
maven-scm.git
{noformat}
[INFO] Applying mojo extractor for language: java
[INFO] Mojo extractor for language: java found 0 mojo descriptors.
[INFO] Applying mojo extractor for language: bsh
[INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Maven SCM . SUCCESS [01:37 min]
[INFO] Maven SCM API . SUCCESS [ 49.921 s]
[INFO] Maven SCM Managers SUCCESS [ 5.292 s]
[INFO] Maven SCM Manager for Plexus .. SUCCESS [ 19.543 s]
[INFO] Maven SCM Test SUCCESS [ 43.112 s]
[INFO] Maven SCM Providers ... SUCCESS [ 5.782 s]
[INFO] Maven SCM AccuRev Provider SUCCESS [ 46.710 s]
[INFO] Maven SCM Bazaar Provider . SUCCESS [ 31.212 s]
[INFO] Maven SCM Clearcase Provider .. SUCCESS [ 38.130 s]
[INFO] Maven SCM CVS Provider - Parent ... SUCCESS [ 5.618 s]
[INFO] Maven SCM CVS Provider TCK tests .. SUCCESS [ 26.636 s]
[INFO] Maven SCM CVS Provider - Common library ... SUCCESS [ 49.035 s]
[INFO] Maven SCM CVS Provider - CVS Executable Impl. . SUCCESS [ 28.367 s]
[INFO] Maven SCM CVS Provider - CVS Java Impl. ... SUCCESS [ 38.279 s]
[INFO] Maven SCM Mercurial (Hg) Provider . SUCCESS [ 37.785 s]
[INFO] Maven SCM Git Provider - Parent ... SUCCESS [ 5.479 s]
[INFO] Maven SCM Git Provider - Common library ... SUCCESS [ 30.737 s]
[INFO] Maven SCM Git Provider TCK Tests .. SUCCESS [ 29.046 s]
[INFO] Maven SCM Git Provider - Git Executable Impl. . SUCCESS [ 49.699 s]
[INFO] Maven SCM Git Provider - JGit Impl. ... SUCCESS [ 38.159 s]
[INFO] Maven SCM Local Provider .. SUCCESS [ 33.002 s]
[INFO] Maven SCM Perforce Provider ... SUCCESS [ 39.655 s]
[INFO] Maven SCM Starteam Provider ... SUCCESS [ 36.574 s]
[INFO] Maven SCM Subversion Provider - Parent SUCCESS [ 5.515 s]
[INFO] Maven SCM Subversion Provider - Common library SUCCESS [ 30.390 s]
[INFO] Maven SCM Subversion Provider TCK Tests ... SUCCESS [ 23.621 s]
[INFO] Maven SCM Subversion Provider - SVN Executable Impl. SUCCESS [ 50.651 s]
[INFO] Maven SCM Synergy Provider SUCCESS [ 34.258 s]
[INFO] Maven SCM Visual Source Safe Provider . SUCCESS [ 36.695 s]
[INFO] Maven SCM TFS Provider SUCCESS [ 31.799 s]
[INFO] Maven SCM MKS Integrity Provider .. SUCCESS [ 45.573 s]
[INFO] Maven SCM Jazz/Rational Team Concert Provider . SUCCESS [ 39.437 s]
[INFO] Maven SCM Standard Providers .. SUCCESS [ 10.255 s]
[INFO] Maven SCM Client .. SUCCESS [ 29.600 s]
[INFO] Maven SCM Plugin .. SUCCESS [01:23 min]
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: iso8601-duration-alt.png
Durations overview ISO 8601:2006
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: iso8601-duration-alt.png, MNG-5176.patch,
MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340329#comment-340329
]
Michael Osipov commented on MNG-5176:
-
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24 h+}}
or {{1.2 d}}, decimal day value.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340329#comment-340329
]
Michael Osipov edited comment on MNG-5176 at 1/29/14 3:04 AM:
--
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24
h+}}, {{1.2 d}}, decimal day value or reduce to {{ 1 d 1 h}} since who cares
for the minutes if you build runs longer than a day.
was (Author: michael-o):
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24 h+}}
or {{1.2 d}}, decimal day value.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340329#comment-340329
]
Michael Osipov edited comment on MNG-5176 at 1/29/14 3:04 AM:
--
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24
h+}}, {{1.2 d}}, decimal day value or reduce to {{1 d 1 h}} since who cares for
the minutes if you build runs longer than a day.
was (Author: michael-o):
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24
h+}}, {{1.2 d}}, decimal day value or reduce to {{ 1 d 1 h}} since who cares
for the minutes if you build runs longer than a day.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340329#comment-340329
]
Michael Osipov edited comment on MNG-5176 at 1/29/14 5:42 AM:
--
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24
h+}}, {{1.2 d}}, decimal day value or reduce to {{1 d 1 h}} since who cares for
the minutes if you build runs longer than a day. Alternatively, pad everyhing
to the max length w/o day duration:
{noformat}
[1 d 01:10 h]
[ 1 d 1 h] (alternative 1)
[24 h+] (alternative 2)
[ 01:02 h]
[01:49 min]
[ 22.345 s]
[ 0.912 s]
{noformat}
was (Author: michael-o):
Robert, the leading zero makes the minutes consistent. That was intentional and
reasonable. We could evaluate the following two options:
Make [] always same size and pad with whitespace
1.
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
2. Left-aligned
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min ]
[22.345 s ]
[0.912 s]
{noformat}
or even
3.
{noformat}
[1 d 01:10 h]
[01:02 h]
[01:49 min]
[22.345 s]
[0.912 s]
{noformat}
I'd prefer option one.
Though I strongly doubt that a duration longer than a day will occur very
option, it should be less than 3 %. In this case one could either say {{24
h+}}, {{1.2 d}}, decimal day value or reduce to {{1 d 1 h}} since who cares for
the minutes if you build runs longer than a day.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340372#comment-340372
]
Robert Scholte commented on MNG-5176:
-
The issue refers to [ISO 8601|http://en.wikipedia.org/wiki/ISO_8601#Durations],
but to me it has become a more readable pattern. Since it's not a standard
anymore, there's room for discussion ;)
I've been searching for the time-unit notation, but I couldn't find the reason
why minutes is {{min}}, while seconds, hours and days are {{s}}, {{h}} and
{{d}}.
My vote would go for same size of [] and right alignment. Also think of the
notation for
{noformat}
[9.953 s] or [09.953 s]
{noformat}
I'm also interested in others opinion, so maybe it's worth to start a
poll/discussion.
Also keep in mind there's this special property:
{{maven.build.timestamp.format}} (
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Available_Variables
)
Maybe this should be extended per timeunit, so users can decide the format for
themselves.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340374#comment-340374
]
Michael Osipov commented on MNG-5176:
-
Actually, it is and the primer of this issue was to improve the duration as
well as the readability of the build timestamp at the end of the build. The
Wikipedia article contains only a condensed view of the standard. I have full
access to the PDF file and it states that durations can be expressed like time
but with the according SI unit for time. I can add the reference if you would
like to see it. See [this BIPM
page|http://www.bipm.org/en/si/si_brochure/chapter4/table6.html] for SI units.
Padding with zeros is only necessary when you have multiple components. In the
case of seconds, you have only one.
So you would go for:
{noformat}
[1 d 01:10 h]
[01:02 h]
[ 01:49 min]
[ 22.345 s]
[0.912 s]
{noformat}
?
To space and take in account and build times above 24 h are rare, one could
align by the next big string:
{noformat}
[1 d 01:10 h]
[ 01:02 h]
[01:49 min]
[ 22.345 s]
[ 0.912 s]
{noformat}
I am aware of this property, it has one drawback: You cannot you set the
timezone for that. The latter issue exists with the buildnumber plugin too.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API ..
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: MNG-5176.patch
Robert, I have updated the patch and improved the format of the duration a lot.
This is how maven.git looks like
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [01:08 min]
[INFO] Maven Model ... SUCCESS [01:06 min]
[INFO] Maven Artifact SUCCESS [28.000 s]
[INFO] Maven Plugin API .. SUCCESS [38.781 s]
[INFO] Maven Model Builder ... SUCCESS [52.188 s]
[INFO] Maven Settings SUCCESS [10.312 s]
[INFO] Maven Settings Builder SUCCESS [11.969 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core SUCCESS [01:49 min]
[INFO] Maven Compat .. SUCCESS [01:01 min]
[INFO] Maven Embedder SUCCESS [24.969 s]
[INFO] Apache Maven Distribution . SUCCESS [38.875 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 09:10 min
[INFO] Finished at: 2014-01-28T22:51:30+01:00
[INFO] Final Memory: 39M/133M
[INFO]
{noformat}
and this is maven-scm.git
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven Wagon SUCCESS [43.265 s]
[INFO] Apache Maven Wagon :: API . SUCCESS [23.875 s]
[INFO] Apache Maven Wagon :: Provider Test ... SUCCESS [16.797 s]
[INFO] Apache Maven Wagon :: Providers ... SUCCESS [12.438 s]
[INFO] Apache Maven Wagon :: Providers :: File Provider .. SUCCESS [12.156 s]
[INFO] Apache Maven Wagon :: Providers :: FTP Provider ... SUCCESS [13.844 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Shared Library SUCCESS [11.718
s]
[INFO] Apache Maven Wagon :: Test Compatibility Kits . SUCCESS [7.047 s]
[INFO] Apache Maven Wagon :: HTTP Test Compatibility Kit . SUCCESS [11.016 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Provider .. SUCCESS [22.687 s]
[INFO] Apache Maven Wagon :: Providers :: Lightweight HTTP Provider SUCCESS
[16.828 s]
[INFO] Apache Maven Wagon :: Providers :: SCM Provider ... SUCCESS [31.094 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Library SUCCESS [37.110 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Tests SUCCESS [54.218 s]
[INFO] Apache Maven Wagon :: Providers :: SSH External Provider SUCCESS
[40.688 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Provider ... SUCCESS [56.000 s]
[INFO] Apache Maven Wagon :: Providers :: WebDav Provider SUCCESS [44.625 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 07:37 min
[INFO] Finished at: 2014-01-28T22:46:22+01:00
[INFO] Final Memory: 37M/107M
[INFO]
{noformat}
Formats are now:
= 1 d: d 'd': %d d hh:mm 'h'
= 1 h: hh:mm 'h'
= 1 min: mm:ss 'min'
else: ss.SSS 's'
This should be absolutely clear now.
If you have no objections, I will push the patch by the weekend. I have to have
it in 3.2.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340310#comment-340310
]
Michael Osipov edited comment on MNG-5176 at 1/28/14 3:53 PM:
--
Robert, I have updated the patch and improved the format of the duration a lot.
This is how maven.git looks like
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [01:08 min]
[INFO] Maven Model ... SUCCESS [01:06 min]
[INFO] Maven Artifact SUCCESS [28.000 s]
[INFO] Maven Plugin API .. SUCCESS [38.781 s]
[INFO] Maven Model Builder ... SUCCESS [52.188 s]
[INFO] Maven Settings SUCCESS [10.312 s]
[INFO] Maven Settings Builder SUCCESS [11.969 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core SUCCESS [01:49 min]
[INFO] Maven Compat .. SUCCESS [01:01 min]
[INFO] Maven Embedder SUCCESS [24.969 s]
[INFO] Apache Maven Distribution . SUCCESS [38.875 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 09:10 min
[INFO] Finished at: 2014-01-28T22:51:30+01:00
[INFO] Final Memory: 39M/133M
[INFO]
{noformat}
and this is maven-scm.git
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven Wagon SUCCESS [43.265 s]
[INFO] Apache Maven Wagon :: API . SUCCESS [23.875 s]
[INFO] Apache Maven Wagon :: Provider Test ... SUCCESS [16.797 s]
[INFO] Apache Maven Wagon :: Providers ... SUCCESS [12.438 s]
[INFO] Apache Maven Wagon :: Providers :: File Provider .. SUCCESS [12.156 s]
[INFO] Apache Maven Wagon :: Providers :: FTP Provider ... SUCCESS [13.844 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Shared Library SUCCESS [11.718
s]
[INFO] Apache Maven Wagon :: Test Compatibility Kits . SUCCESS [7.047 s]
[INFO] Apache Maven Wagon :: HTTP Test Compatibility Kit . SUCCESS [11.016 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Provider .. SUCCESS [22.687 s]
[INFO] Apache Maven Wagon :: Providers :: Lightweight HTTP Provider SUCCESS
[16.828 s]
[INFO] Apache Maven Wagon :: Providers :: SCM Provider ... SUCCESS [31.094 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Library SUCCESS [37.110 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Tests SUCCESS [54.218 s]
[INFO] Apache Maven Wagon :: Providers :: SSH External Provider SUCCESS
[40.688 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Provider ... SUCCESS [56.000 s]
[INFO] Apache Maven Wagon :: Providers :: WebDav Provider SUCCESS [44.625 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 07:37 min
[INFO] Finished at: 2014-01-28T22:46:22+01:00
[INFO] Final Memory: 37M/107M
[INFO]
{noformat}
Formats are now:
= 1 d: {{d 'd': %d d hh:mm 'h'}}
= 1 h: {{hh:mm 'h'}}
= 1 min: {{mm:ss 'min'}}
else: {{ss.SSS 's'}}
This should be absolutely clear now.
If you have no objections, I will push the patch by the weekend. I'd like to
have it in 3.2.
was (Author: michael-o):
Robert, I have updated the patch and improved the format of the duration a lot.
This is how maven.git looks like
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [01:08 min]
[INFO] Maven Model ... SUCCESS [01:06 min]
[INFO] Maven Artifact SUCCESS [28.000 s]
[INFO] Maven Plugin API .. SUCCESS [38.781 s]
[INFO] Maven Model Builder ... SUCCESS [52.188 s]
[INFO] Maven Settings SUCCESS [10.312 s]
[INFO] Maven Settings Builder SUCCESS [11.969 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340310#comment-340310
]
Michael Osipov edited comment on MNG-5176 at 1/28/14 3:56 PM:
--
Robert, I have updated the patch and improved the format of the duration a lot.
This is how maven.git looks like
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [01:08 min]
[INFO] Maven Model ... SUCCESS [01:06 min]
[INFO] Maven Artifact SUCCESS [28.000 s]
[INFO] Maven Plugin API .. SUCCESS [38.781 s]
[INFO] Maven Model Builder ... SUCCESS [52.188 s]
[INFO] Maven Settings SUCCESS [10.312 s]
[INFO] Maven Settings Builder SUCCESS [11.969 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core SUCCESS [01:49 min]
[INFO] Maven Compat .. SUCCESS [01:01 min]
[INFO] Maven Embedder SUCCESS [24.969 s]
[INFO] Apache Maven Distribution . SUCCESS [38.875 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 09:10 min
[INFO] Finished at: 2014-01-28T22:51:30+01:00
[INFO] Final Memory: 39M/133M
[INFO]
{noformat}
and this is maven-scm.git
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven Wagon SUCCESS [43.265 s]
[INFO] Apache Maven Wagon :: API . SUCCESS [23.875 s]
[INFO] Apache Maven Wagon :: Provider Test ... SUCCESS [16.797 s]
[INFO] Apache Maven Wagon :: Providers ... SUCCESS [12.438 s]
[INFO] Apache Maven Wagon :: Providers :: File Provider .. SUCCESS [12.156 s]
[INFO] Apache Maven Wagon :: Providers :: FTP Provider ... SUCCESS [13.844 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Shared Library SUCCESS [11.718
s]
[INFO] Apache Maven Wagon :: Test Compatibility Kits . SUCCESS [7.047 s]
[INFO] Apache Maven Wagon :: HTTP Test Compatibility Kit . SUCCESS [11.016 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Provider .. SUCCESS [22.687 s]
[INFO] Apache Maven Wagon :: Providers :: Lightweight HTTP Provider SUCCESS
[16.828 s]
[INFO] Apache Maven Wagon :: Providers :: SCM Provider ... SUCCESS [31.094 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Library SUCCESS [37.110 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Common Tests SUCCESS [54.218 s]
[INFO] Apache Maven Wagon :: Providers :: SSH External Provider SUCCESS
[40.688 s]
[INFO] Apache Maven Wagon :: Providers :: SSH Provider ... SUCCESS [56.000 s]
[INFO] Apache Maven Wagon :: Providers :: WebDav Provider SUCCESS [44.625 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 07:37 min
[INFO] Finished at: 2014-01-28T22:46:22+01:00
[INFO] Final Memory: 37M/107M
[INFO]
{noformat}
Formats are now:
= 1 d: {{d 'd' hh:mm 'h'}}
= 1 h: {{hh:mm 'h'}}
= 1 min: {{mm:ss 'min'}}
else {{ss.SSS 's'}}
This should be absolutely clear now.
If you have no objections, I will push the patch by the weekend. I'd like to
have it in 3.2.
was (Author: michael-o):
Robert, I have updated the patch and improved the format of the duration a lot.
This is how maven.git looks like
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [01:08 min]
[INFO] Maven Model ... SUCCESS [01:06 min]
[INFO] Maven Artifact SUCCESS [28.000 s]
[INFO] Maven Plugin API .. SUCCESS [38.781 s]
[INFO] Maven Model Builder ... SUCCESS [52.188 s]
[INFO] Maven Settings SUCCESS [10.312 s]
[INFO] Maven Settings Builder SUCCESS [11.969 s]
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core SUCCESS
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Fix Version/s: 3.2
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340312#comment-340312
]
Robert Scholte commented on MNG-5176:
-
Not bad, though I see some inconsequent styles:
{noformat}
[INFO] Maven Repository Metadata Model ... SUCCESS [9.953 s]
[INFO] Maven Aether Provider . SUCCESS [27.547 s]
[INFO] Maven Core SUCCESS [01:49 min]
[INFO] Maven Compat .. SUCCESS [01:01 min]
{noformat}
IMHO the {{9.953 s }} should be prefixed with a space. Maybe for the minutes as
well, instead of the zero. And doesn't right alignment look better? i.e. all
']' in the same column?
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.2
Attachments: MNG-5176.patch, MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338191#comment-338191
]
Michael Osipov commented on MNG-5176:
-
[~rfscholte], I did not strip the zero, I removed the fractional part from the
seconds because this module requires more than one hour to build. The fraction
part are irrelevant in such a scale.
I have already thought about right alignment but where? Align all times to the
right but what about the brackets? Leave spaces? Align with duration? The other
option would be use {{hh:mm:ss.fff}} throughout but that would be a waste of
space because only a little amount of modules really require more than one hour
to build. {{01h00:06}} isn't a good idea because the defined seperator is colon
and nothing else. The alternative is {{01:00:06 h}}, {{02:03.355 min}} but
again you are still wasting space because hour and day is only a small amount.
If you check the first example, you'll see that this looks quite nice. There is
not too much room with ISO 8601, the question simply is: What component does
one want to leave out? As you can see, I left out the least signifiact
component with every order of magnitude.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ...
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338192#comment-338192
]
Robert Scholte commented on MNG-5176:
-
The problem is that I didn't noticed the difference between '.' and ':' at
first sight. So I misinterpreted the duration, which is more critical then a
ISO based notation IMHO.
When we have to _learn_ users to look good for '.' and ':' then it is maybe not
so nice feature.
Here are some alignment options:
{noformat}
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Model ... SUCCESS [ 01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
{noformat}
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338194#comment-338194
]
Michael Osipov commented on MNG-5176:
-
Robert, yes I do agree now. The use needs a visual clue to see that this is a
different order. I would tend to third one (right alignment). Position of
separators differs to that of the minute scale, so a user should see the
difference right away.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338127#comment-338127
]
Robert Scholte commented on MNG-5176:
-
We probably need to discuss it a bit.
I had trouble reading the duration of Maven Model. At first I thought you only
stripped of a final '0'. Looking closer I noticed the two colons.
Some ideas: align them to the right and maybe 01h00:06
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-5176:
Assignee: Michael Osipov
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
Since most build
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338095#comment-338095
]
Michael Osipov commented on MNG-5176:
-
Robert, do you think further discussion is necessary on dev@? Otherwise I would
apply the patch to 3.2.x without further modification.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: MNG-5176.patch
Updated patch. The last ones were buggy and failed the tests. Patch applied
against Maven 3.1.1.
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Attachments: MNG-5176.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Summary: Print build times in an ISO 8601-style manner (was: Print build
times in an ISO8601-style manner)
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Attachments: 2.2.1.patch, 3.0.3.patch
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Description:
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the following
ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though this
should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not touch
the finish time in Maven 2.2.x because it is alphanumeric. I'd rather prefer
that as total time but this is maybe a matter of taste and harder to parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
Since most build are below an hour, they are way easier to read.
was:
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO8601-style
date/time formats.
My patches need less code compared to the current solution. I had the following
ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though this
should be a rare case.
3. remove the smallest component if a bigger
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: (was: 2.2.1.patch)
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
Since most build are below an hour, they are way easier to read.
--
This message
[jira] (MNG-5176) Print build times in an ISO 8601-style manner
[
https://jira.codehaus.org/browse/MNG-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5176:
Attachment: (was: 3.0.3.patch)
Print build times in an ISO 8601-style manner
-
Key: MNG-5176
URL: https://jira.codehaus.org/browse/MNG-5176
Project: Maven 2 3
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.1, 3.0.3
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
The current output of build times is hard to read and does not follow any
standard. I have patched branch 2.2.x and 3 trunk to follow ISO 8601-style
date/time formats.
My patches need less code compared to the current solution. I had the
following ideas in mind:
1. Display times in the same proportional format.
2. hour display is fixed to max 24 h as in ISO defined.
3. Days are directly integrated, not brain math necessary anymore. Though
this should be a rare case.
3. remove the smallest component if a bigger one is added.
4. Easier to parse, predictable output.
More over, I have changed the finish and total time to ISO too. I did not
touch the finish time in Maven 2.2.x because it is alphanumeric. I'd rather
prefer that as total time but this is maybe a matter of taste and harder to
parse.
This is a real output:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [00:04.732]
[INFO] Maven Model ... SUCCESS [00:06.332]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:52.618
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
A crafted output with all formats would look like this:
{noformat}
[INFO] Building tar :
/.amd_mnt/blnn728x/home/osipovmi/Projekte/maven-3/apache-maven/target/apache-maven-3.0.4-SNAPSHOT-bin.tar.gz
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Maven .. SUCCESS [1 d 03:04]
[INFO] Maven Model ... SUCCESS [01:00:06]
[INFO] Maven Artifact SUCCESS [00:02.551]
[INFO] Maven Plugin API .. SUCCESS [00:03.855]
[INFO] Maven Model Builder ... SUCCESS [00:06.708]
[INFO] Maven Settings SUCCESS [00:02.292]
[INFO] Maven Settings Builder SUCCESS [00:02.138]
[INFO] Maven Repository Metadata Model ... SUCCESS [00:01.931]
[INFO] Maven Aether Provider . SUCCESS [00:02.442]
[INFO] Maven Core SUCCESS [00:28.509]
[INFO] Maven Compat .. SUCCESS [00:20.260]
[INFO] Maven Embedder SUCCESS [00:03.478]
[INFO] Maven Distribution SUCCESS [00:26.715]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1 d 03:05
[INFO] Finished at: 2011-09-19 14:25:24
[INFO] Final Memory: 36M/144M
[INFO]
{noformat}
Since most build are below an hour, they are way easier to read.
--
This message
