@Lennart: is it a coincidence that your email signature follows the same
format pattern? ;)
Anyway, I agree with Anders: instead of dumping a huge multi line message into
the log, can you please split it into one log statement per line?
The advantages are:
1) you don't need to take care of emitting the correct line endings: the
logging framework will take care of it,
2) each line will have a proper prefix and consistent indentation and
3) in case of a nested maven execution (eg when release or invoker plugin runs)
all lines will also be correctly prefixed and consistently indented
I do not mind it if the plugin uses additional visual separators or extra
indentation/prefixing for the sake of better log readability.
Kind regards,
--
Sergei
>
>Tuesday, 10 February 2015 09:10 +0000 from Anders Hammar <and...@hammar.net>:
>Sure, I see your point. However, there is nothing that forces you to have
>everything logged in one line but you can always separate it on multiple rows.
>But then with the standard format with log level info in the beginning (of
>every row). For example, this is what is done in the maven-compiler-plugin
>debug log that you pasted (see source roots for example).
>Having a completely new logging format bothers me. As well as all the
>unnecessary empty rows and separator lines. There is nothing unique with this
>info that makes it more important than debug info logged by Maven core or
>other plugins.
>/Anders
>On Tue, Feb 10, 2015 at 9:12 AM, Lennart Jörelid < lennart.jore...@gmail.com
>> wrote:
>>The difference is one of accessibility and usability.
>>Terse logs which contain statements on the form seen below are rather
>>difficult to browse, if you want to find some kind of grouped information.
>>I would stretch as far as to say they are rather unreadable; the last
>>statement, for example, stretches over several rows.
>>It more or less requires developers to paste the line into a text editor and
>>split each argument onto a separate line to even begin to be user-friendly
>>enough for tracking down any errors.
>>
>>[DEBUG] Using compiler 'javac'.
>>[DEBUG] Source directories:
>>[/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb]
>>[DEBUG] Classpath:
>>[/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes]
>>[DEBUG] Output directory:
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes
>>[DEBUG] CompilerReuseStrategy: reuseCreated
>>[DEBUG] Classpath:
>>[DEBUG]
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes
>>[DEBUG] Source roots:
>>[DEBUG]
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/src/main/java
>>[DEBUG]
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb
>>[DEBUG] Command line options:
>>[DEBUG] -d
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes
>> -classpath
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes:
>> -sourcepath
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb:
>>
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb/com/example/myschema/ObjectFactory.java
>>
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb/com/example/myschema/AddressType.java
>> -s
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/annotations
>> -g -nowarn -target 1.6 -source 1.6 -encoding UTF-8
>>[INFO] Compiling 2 source files to
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/classes
>>
>>
>>Compare this with the single, but formatted, log statement below listing all
>>effective arguments passed to the XJC tool by the jaxb2-maven-plugin:
>>
>>[DEBUG]
>>
>>+=================== [11 XJC Arguments]
>>|
>>| [0]: -xmlschema
>>| [1]: -encoding
>>| [2]: UTF-8
>>| [3]: -d
>>| [4]:
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb
>>| [5]: -extension
>>| [6]: -episode
>>| [7]:
>>/Users/lj/Development/Projects/Codehaus/jaxb2-maven-plugin/target/it/mjaxb-33/target/generated-sources/jaxb/META-INF/sun-jaxb.episode
>>| [8]: -b
>>| [9]: src/main/xjb/spaced filename.xjb
>>| [10]: src/main/xsd/address.xsd
>>|
>>+=================== [End 11 XJC Arguments]
>>
>>Not only is the listing here grouped visually to ensure that users can read
>>each argument as part of a whole, but the debug statement also provides
>>information about what the parts pertain to ("11 XJC Arguments").
>>These - to me - are considerably better log statements for jaxb2-maven-plugin
>>users when attempting to track down problems in their configuration than
>>traditional Maven logging-style statements.
>>Of course, these boxes stand out a tad from the traditional logging
>>statements - which is intentional @ debug log level.
>>
>>
>>
>>2015-02-10 8:32 GMT+01:00 Anders Hammar < and...@hammar.net > :
>>>I'll have a look.
>>>
>>>Also, I'm confused by the new type of debug logging. Many of the debug
>>>logging output chunks are formatted totally different from any Maven plugin
>>>I've seen. Any reason for this? What's wrong with the existing style?
>>>With different I mean that there are many separating lines (i.e.
>>>"=========================="), empty rows, no log level info in the
>>>beginning of the row, repeating plugin name/version/etc info, etc.
>>>
>>>/Anders
>>>
>>>On Tue, Feb 10, 2015 at 5:14 AM, Lennart Jörelid <
>>>lennart.jore...@gmail.com > wrote:
>>>>Ah.
>>>>
>>>>Since I don't use Eclipse, I am unsure about how to test or validate this.
>>>>There is no change in the file
>>>>(src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml) or goals
>>>>that it uses, so I suspect something else is afoot.
>>>>
>>>>Could I get some assistance from someone who uses eclipse so I can
>>>>understand what should be done?
>>>>Like a log trace, and possibly some poinpoint-the-error-time?
>>>>
>>>>
>>>>2015-02-09 22:44 GMT+01:00 Anders Hammar < and...@hammar.net > :
>>>>>-1
>>>>>
>>>>>The m2e integration doesn't work. I've only tested the xjc mojo so far
>>>>>though. The problem can be seen by importing IT 'xjc-main' for example.
>>>>>
>>>>>/Anders
>>>>>
>>>>>On Mon, Feb 9, 2015 at 7:35 AM, Lennart Jörelid <
>>>>>lennart.jore...@gmail.com > wrote:
>>>>>>Hi all,
>>>>>>
>>>>>>I'd like to release version 2.0 of the JAXB2 Maven Plugin, which is a
>>>>>>major plugin
>>>>>>upgrade that contains rewritten plugin mechanics, updates to the JAXB2
>>>>>>toolset
>>>>>>and several bug fixes.
>>>>>>
>>>>>>The JAXB2-Maven-Plugin uses the Java API for XML Binding (JAXB), version
>>>>>>2+, to
>>>>>>generate Java classes from XML Schemas and to create XML Schemas from
>>>>>>annotated
>>>>>>Java classes. The plugin delegates most of its work to either of the two
>>>>>>JDK-supplied tools XJC and Schemagen.
>>>>>>
>>>>>>We solved 25 issues:
>>>>>>http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11699&version=20768
>>>>>>
>>>>>>Bug
>>>>>>
>>>>>> [MJAXB-27] - Test for staleness doesns't handle deep tree files
>>>>>>correctly
>>>>>> [MJAXB-89] - external resource restriction due to JAXP 1.5 in JDK 1.8
>>>>>> [MJAXB-90] - schemagen prints "null" on screen and creates empty
>>>>>>"schemagen" target folder
>>>>>> [MJAXB-91] - schemagen no overwriting of named xsd file
>>>>>> [MJAXB-97] - mjaxb-14 fails when running under JDK 8
>>>>>> [MJAXB-109] - Define the purpose of all ITs
>>>>>> [MJAXB-115] - Synthesize the SchemaGen classpath for managing module
>>>>>>dependencies
>>>>>>
>>>>>>Improvement
>>>>>>
>>>>>> [MJAXB-35] - Postfix of bindingfiles can't be set
>>>>>> [MJAXB-93] - Add support for multi-line arguments for the xjc
>>>>>>configuration
>>>>>> [MJAXB-101] - Upgrade JAXB dependencies to 2.2.11+
>>>>>> [MJAXB-102] - Update maven-plugin-testing-harness
>>>>>> [MJAXB-103] - Add structured post-processing pipeline to handle
>>>>>>Javadoc-to-XML Documentation
>>>>>> [MJAXB-104] - Move all Collection properties to standard Maven Lists
>>>>>> [MJAXB-105] - Only warn when defined encoding and platform's default
>>>>>>encoding differ
>>>>>> [MJAXB-106] - The formatting of XSD documentation annotations for a
>>>>>>JavaDoc comment must be configurable
>>>>>> [MJAXB-107] - Add pipeline/engine for structured ordering of
>>>>>>NodeProcessors for post-processing generated XSDs
>>>>>> [MJAXB-108] - Ensure that dependent XJC flags are set as required
>>>>>> [MJAXB-110] - Create validation scripts for each IT in the plugin
>>>>>> [MJAXB-111] - Clarify how SchemaGenerator sources are calcualted and
>>>>>>included
>>>>>> [MJAXB-112] - Clarify how encoding is set and used by the plugin and
>>>>>>its tools
>>>>>> [MJAXB-113] - Remove the generated bytecode files from SchemaGen when
>>>>>>sources exist in normal compile scope
>>>>>> [MJAXB-114] - The SchemaGenerator should not use
>>>>>>target/generated-resources as a work directory
>>>>>>
>>>>>>New Feature
>>>>>>
>>>>>> [MJAXB-58] - Add native support for episodes
>>>>>>
>>>>>>Story
>>>>>>
>>>>>> [MJAXB-100] - Update xjc to 2.2.11
>>>>>>
>>>>>>Task
>>>>>>
>>>>>> [MJAXB-87] - Fix IT mjaxb-33
>>>>>>
>>>>>>
>>>>>>
>>>>>>There are still a couple of issues left in JIRA - but they are for
>>>>>>upcoming releases
>>>>>>http://jira.codehaus.org/browse/MASPECTJ#selectedTab=com.atlassian.jira.plugin.system.project:issues-panel
>>>>>>
>>>>>>Staging Repositories:
>>>>>>General: https://nexus.codehaus.org/content/groups/staging/
>>>>>>Exclusive:
>>>>>>https://nexus.codehaus.org/content/groups/staging/org/codehaus/mojo/jaxb2-maven-plugin/2.0/
>>>>>>
>>>>>>(Staging) Site:
>>>>>>http://mojo.codehaus.org/jaxb2-maven-plugin/
>>>>>>
>>>>>>SCM Tag:
>>>>>>jaxb2-maven-plugin-2.0
>>>>>>
>>>>>>ADDITIONAL_INFORMATION
>>>>>>
>>>>>> [ ] +1
>>>>>> [ ] +0
>>>>>> [ ] -1
>>>>>>
>>>>>>The vote is open for 72 hours and will succeed by lazy consensus.
>>>>>>
>>>>>>--
>>>>>>--
>+==============================+
>| Bästa hälsningar,
>| [sw. "Best regards"]
>|
>| Lennart Jörelid
>| EAI Architect & Integrator
>|
>| jGuru Europe AB
>| Mölnlycke - Kista
>|
>| Email: l...@jguru.se
>| URL: www.jguru.se
>| Phone
>| (skype): jgurueurope
>| (intl): +46 708 507 603
>| (domestic): 0708 - 507 603
>+==============================+
>>>>
>>>>
>>>>
>>>>--
>>>>--
>+==============================+
>| Bästa hälsningar,
>| [sw. "Best regards"]
>|
>| Lennart Jörelid
>| EAI Architect & Integrator
>|
>| jGuru Europe AB
>| Mölnlycke - Kista
>|
>| Email: l...@jguru.se
>| URL: www.jguru.se
>| Phone
>| (skype): jgurueurope
>| (intl): +46 708 507 603
>| (domestic): 0708 - 507 603
>+==============================+
>>
>>
>>
>>--
>>--
>+==============================+
>| Bästa hälsningar,
>| [sw. "Best regards"]
>|
>| Lennart Jörelid
>| EAI Architect & Integrator
>|
>| jGuru Europe AB
>| Mölnlycke - Kista
>|
>| Email: l...@jguru.se
>| URL: www.jguru.se
>| Phone
>| (skype): jgurueurope
>| (intl): +46 708 507 603
>| (domestic): 0708 - 507 603
>+==============================+
