Quantcast

[GitHub] activemq-artemis pull request #1019: ARTEMIS-943 fix queueType in import-exp...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis pull request #1019: ARTEMIS-943 fix queueType in import-exp...

clebertsuconic-3
GitHub user cshannon opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1019

    ARTEMIS-943 fix queueType in import-export schema

    https://issues.apache.org/jira/browse/ARTEMIS-943
   
    queueType in the artemis-import-export schema needs to be marked with
    min and max occurs attributes to specify that the element can occur more than one
    time.  This is important so JAXB generates the correct bindings.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cshannon/activemq-artemis ARTEMIS-943

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1019.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1019
   
----
commit 637405a886acd272e8721a0bcc7ad39387f6eb2d
Author: Christopher L. Shannon (cshannon) <[hidden email]>
Date:   2017-02-15T15:12:07Z

    ARTEMIS-943 fix queueType in import-export schema
   
    https://issues.apache.org/jira/browse/ARTEMIS-943
   
    queueType in the artemis-import-export schema needs to be marked with
    min and max occurs attributes to specify that the element can occur more than one
    time.  This is important so JAXB generates the correct bindings.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis issue #1019: ARTEMIS-943 fix queueType in import-export sch...

clebertsuconic-3
Github user cshannon commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1019
 
    @clebertsuconic and @jbertram ,
   
    If necessary I can create a new Jira for this but it seemed minor enough that I just attached it to the existing Jira that was used to add the schema.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis issue #1019: ARTEMIS-943 fix queueType in import-export sch...

clebertsuconic-3
In reply to this post by clebertsuconic-3
Github user jbertram commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1019
 
    Looks good.  Nice catch.  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis pull request #1019: ARTEMIS-943 fix queueType in import-exp...

clebertsuconic-3
In reply to this post by clebertsuconic-3
Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1019


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...