[mojo-dev] [jira] (MJAXB-76) XmlRootElement annotation not added to root element class if it has a type that's defined in the same schema
Title: Message Title
Anders Hammar commented on an issue
Re: XmlRootElement annotation not added to root element class if it has a type that's defined in the same schema
With all respect, I don't have time to do that. It would be the same amount of work for me as for you. I don't use jaxb from command line either.
I'll close this as not a bug in the plugin, as I think it has to do with the jaxb impl itself. If you can verify I'm wrong, please touch back and ask for the ticket to be re-opened!
Add Comment
Mojo's JAXB-2 Maven Plugin / MJAXB-76
XmlRootElement annotation not added to root element class if it has a type that's defined in the same schema
If my root element uses an anonymous complex type, the generated Java class is correctly annotated with XmlRootElement. If it's a custom type defined in the same schema then the class doesn't have the XmlRootElement annotation. *anonymous complex type* {code:xml} http://www.w3.org/2001/XMLSchema">...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please v
[mojo-dev] [jira] (MJAXB-76) XmlRootElement annotation not added to root element class if it has a type that's defined in the same schema
Title: Message Title Anders Hammar closed an issue as Not A Bug Mojo's JAXB-2 Maven Plugin / MJAXB-76 XmlRootElement annotation not added to root element class if it has a type that's defined in the same schema Change By: Anders Hammar Resolution: Not A Bug Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MLICENSE-103) Don't show each single file name
Title: Message Title Markus KARG created an issue Mojo's License Maven Plugin / MLICENSE-103 Don't show each single file name Issue Type: Improvement Assignee: Tony Chemit Created: 23/Feb/14 2:19 AM Priority: Minor Reporter: Markus KARG When the licence plugin is adding licence headers to files, it prints each single file name, and after that a summary. This is a bit too much. Particularly for large projects it would be enough to print the summary, and do not print each single file name. Hence, file names should only be printed in debug mode. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] [jira] (MJAXB-84) Convert to Mojo Java 5 annotations
Title: Message Title Anders Hammar created an issue Mojo's JAXB-2 Maven Plugin / MJAXB-84 Convert to Mojo Java 5 annotations Issue Type: Task Assignee: Unassigned Created: 23/Feb/14 2:21 AM Environment: n/a Priority: Minor Reporter: Anders Hammar Use the Java 5 annotations instead of the javadoc style ones. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] [jira] (MJAXB-84) Convert to Mojo Java 5 annotations
Title: Message Title Anders Hammar updated an issue Mojo's JAXB-2 Maven Plugin / MJAXB-84 Convert to Mojo Java 5 annotations Change By: Anders Hammar Fix Version/s: 1.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-84) Convert to Mojo Java 5 annotations
Title: Message Title Anders Hammar assigned an issue to Anders Hammar Mojo's JAXB-2 Maven Plugin / MJAXB-84 Convert to Mojo Java 5 annotations Change By: Anders Hammar Assignee: Anders Hammar Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-61) Upgrade to JAXB 2.2
Title: Message Title Anders Hammar commented on an issue Re: Upgrade to JAXB 2.2 This change will also imply a requirement of Java 6 as the jaxb-xjc v2.2 requires that (checked v2.2.6 and v2.2.7). Add Comment Mojo's JAXB-2 Maven Plugin / MJAXB-61 Upgrade to JAXB 2.2 Should we upgrade the used JAXB implementation (com.sun.xml.bind:jaxb-xjc) to the latest 2.2 version? Any impact, or is it fully backwards compatible? One benefit would be that in 2.2.5+ there is build-in support for configuring the output char encoding. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-85) Upgrade dependency to Java 6
Title: Message Title Anders Hammar updated an issue Mojo's JAXB-2 Maven Plugin / MJAXB-85 Upgrade dependency to Java 6 Change By: Anders Hammar Fix Version/s: 1.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-85) Upgrade dependency to Java 6
Title: Message Title Anders Hammar assigned an issue to Anders Hammar Mojo's JAXB-2 Maven Plugin / MJAXB-85 Upgrade dependency to Java 6 Change By: Anders Hammar Assignee: Anders Hammar Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-85) Upgrade dependency to Java 6
Title: Message Title Anders Hammar created an issue Mojo's JAXB-2 Maven Plugin / MJAXB-85 Upgrade dependency to Java 6 Issue Type: Improvement Assignee: Unassigned Created: 23/Feb/14 2:49 AM Environment: n/a Priority: Major Reporter: Anders Hammar Newest plexus-utils library requires Java 6 and also an upgrade to JAXB 2.2 will imply this. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] [jira] (MJAXB-86) Upgrade requirement to Maven 2.2.1
Title: Message Title Anders Hammar assigned an issue to Anders Hammar Mojo's JAXB-2 Maven Plugin / MJAXB-86 Upgrade requirement to Maven 2.2.1 Change By: Anders Hammar Assignee: Anders Hammar Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-86) Upgrade requirement to Maven 2.2.1
Title: Message Title Anders Hammar updated an issue Mojo's JAXB-2 Maven Plugin / MJAXB-86 Upgrade requirement to Maven 2.2.1 Change By: Anders Hammar Fix Version/s: 1.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-86) Upgrade requirement to Maven 2.2.1
Title: Message Title Anders Hammar created an issue Mojo's JAXB-2 Maven Plugin / MJAXB-86 Upgrade requirement to Maven 2.2.1 Issue Type: Improvement Assignee: Unassigned Created: 23/Feb/14 2:53 AM Environment: n/a Priority: Minor Reporter: Anders Hammar Maven 2 is EOF, so we should move requirement to 2.2.1 for this release and not support older versions. In the future we could even change to Maven 3 requirement. Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] Issues with latest mojo-parent due to cobertura-m-p 2.6
I see unit tests failing during the site lifecycle when using the latest mojo-parent (v33), which seems to be due to cobertura-mp-p v2.6. Using v2.5.2 it works just fine. Anyone else who has seen this? Can't find a jira ticket describing this. /Anders
[mojo-dev] [jira] (MJAXB-85) Upgrade dependency to Java 6
Title: Message Title Anders Hammar closed an issue as Fixed Fixed in r19452 Mojo's JAXB-2 Maven Plugin / MJAXB-85 Upgrade dependency to Java 6 Change By: Anders Hammar Resolution: Fixed Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-85) Upgrade dependency to Java 6
Title: Message Title Anders Hammar commented on an issue Re: Upgrade dependency to Java 6 I've also updated the ci build jobs with JDK 6 requirement Add Comment Mojo's JAXB-2 Maven Plugin / MJAXB-85 Upgrade dependency to Java 6 Newest plexus-utils library requires Java 6 and also an upgrade to JAXB 2.2 will imply this. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-86) Upgrade requirement to Maven 2.2.1
Title: Message Title Anders Hammar closed an issue as Fixed Fixed in r19454 Mojo's JAXB-2 Maven Plugin / MJAXB-86 Upgrade requirement to Maven 2.2.1 Change By: Anders Hammar Resolution: Fixed Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-84) Convert to Mojo Java 5 annotations
Title: Message Title Anders Hammar closed an issue as Fixed Fixed in r19455 Mojo's JAXB-2 Maven Plugin / MJAXB-84 Convert to Mojo Java 5 annotations Change By: Anders Hammar Resolution: Fixed Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-8) When having multiple executions the jaxb plugin uses same staleFile for both runs
Title: Message Title Anders Hammar assigned an issue to Anders Hammar Mojo's JAXB-2 Maven Plugin / MJAXB-8 When having multiple executions the jaxb plugin uses same staleFile for both runs Change By: Anders Hammar Assignee: Anders Hammar Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-8) When having multiple executions the jaxb plugin uses same staleFile for both runs
Title: Message Title Anders Hammar closed an issue as Fixed Fixed in r19456 Mojo's JAXB-2 Maven Plugin / MJAXB-8 When having multiple executions the jaxb plugin uses same staleFile for both runs Change By: Anders Hammar Resolution: Fixed Fix Version/s: 1.6 Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJAXB-79) JAXB-2 Maven Plugin don't include the license file
Title: Message Title Anders Hammar closed an issue as Fixed Mojo's JAXB-2 Maven Plugin / MJAXB-79 JAXB-2 Maven Plugin don't include the license file Change By: Anders Hammar Resolution: Fixed Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Re: [mojo-dev] NOTICE file in source tree
Depends on the license the plugin is using and the code provenance. On Sunday, 23 February 2014, Dan Tran wrote: > plugins at apache maven has those files automated under MANIFEST, are we > obligate to do so? > > -D > > > On Sat, Feb 22, 2014 at 4:34 AM, Anders Hammar > > > wrote: > >> MJAXB-79 asks for LICENSE and NOTICE file in the source tree of jaxb-m-p. >> I don't see any other plugin having a NOTICE file. Should we have that at >> Mojo? >> >> /Anders >> > > -- Sent from my phone
