You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is correct. The Maven plugin output defaults to a width of 79 characters. The command-line detects the width of the console and adjusts accordingly.
In Maven this isn't possible. So we're left with three choices:
Leave things as is (79 chars)
Increase to some other fixed limit (ex. 119 chars) and resize columns accordingly
Make it fully dynamic. Resize columns based on content with no truncating
I favor dynamic because that would be the end all fix. Everyone has different formats for their versions ranging from major.minor.patch to full dates with separators like mine so we cannot assume a maximum length. 20 something characters is not enough for a description either as it may contain "adding table blah_blah" which is on the cusp of being truncated. The current display of info is not expanding to the unused space in my console so it seems wasteful to have to truncate and hide information. Thanks!
Version and description are cut off when I run mvn flyway:info. I receive the following:
+----------------+----------------------------+---------------------+---------+
| Version | Description | Installed on | State |
+----------------+----------------------------+---------------------+---------+
| 1.0 | ddl | | PreInit |
| 1.1 | reference data | 2014-04-26 15:01:37 | Success |
| 2014.04.24.14. | new fields client asset va | 2014-04-26 15:04:03 | Success |
The full version should be:
+----------------+----------------------------+---------------------+---------+
| Version | Description | Installed on | State |
+----------------+----------------------------+---------------------+---------+
| 1.0 | ddl | | PreInit |
| 1.1 | reference data | 2014-04-26 15:01:37 | Success |
| 2014.04.24.14.29.19 | new fields client asset value | 2014-04-26 15:04:03 | Success |
The text was updated successfully, but these errors were encountered: