... and, of course, when package migration and major refactoring is done we
will re-integrate the changes into the Codehaus SVN.

This may perhaps have been completely evident (or implied); just mentioning
it in the interest of clarity.

2014-11-20 11:36 GMT+01:00 Lennart Jörelid <lennart.jore...@gmail.com>:

> Considering that this development effort will presumably be somewhat
> bigger than between common releases, I have made a SVN to GIT conversion to
> enable branched development in GIT (without creating clutter and confusion
> in the Codehaus SVN repository).  The development GIT repo is found on
> https://github.com/lennartj/jaxb2-maven-plugin, and the main branch used
> for development is "Version_2_Migration", rather than "main".
>
> I will start pushing in the changes I have done so far ... in a little
> while.
>
> Presumably, this will simplify testing and discussing code changes without
> unnecessarily polluting the Codehaus SVN for the J-M-P.
>
> Fair?
>
>
> 2014-11-20 11:27 GMT+01:00 Anders Hammar <and...@hammar.net>:
>
>>
>> Oh - and the reason we should use the glassfish JARs is found in the POMs
>>> of the com.sun.... JAXB jar artifacts, claiming that they are "Old JAXB
>>> ....". An example is found below. The corresponding POMs of the
>>> org.glassfish JARs do not claim to be the Old JAXB ... but rather the jaxb
>>> distribution.
>>>
>>> So I deduct that we should use the glassfish dependencies. Fair?
>>>
>>
>> I did a quick compare of the com.sun.xml.bind jars and the
>> org.glassfish.jaxb jars. The difference is that the sun ones do include
>> some additional classes which are missing in the glassfish ones (this seems
>> to be handled through a separate dependency now according to the BOM). But
>> the "jaxb classes" are still in com.sun.* Java packages and are identical
>> in the two jar sets.
>> One note though: "jaxb-impl" is called "jaxb-runtime" in the glassfish
>> set.
>>
>> Based on the note of "new" and "old" in the BOM is think we should go
>> with the glassfish set.
>>
>> I'll add this to the JIRA ticket for future reference.
>>
>> /Anders
>>
>>
>>>     <parent>        <groupId>com.sun.xml.bind.mvn</groupId>        
>>> <artifactId>jaxb-bundles</artifactId>        <version>2.2.11</version>    
>>> </parent>    <groupId>com.sun.xml.bind</groupId>    
>>> <artifactId>jaxb-impl</artifactId>    <packaging>jar</packaging>    
>>> <name>Old JAXB Runtime</name>    <description>Old JAXB Runtime module. 
>>> Contains sources required for runtime processing.</description>
>>>
>>>
>>>
>>> 2014-11-18 22:43 GMT+01:00 Lennart Jörelid <lennart.jore...@gmail.com>:
>>>
>>>> Hello there,
>>>>
>>>>
>>>> Duh!  I meant version 2.2.11, of course; just a typo on my part.
>>>> However, in the 2.2.11 JAXB bom you will find the following:
>>>>
>>>> <stax-ex.version>1.7.7</stax-ex.version>
>>>>
>>>> ... which is the root of my question. I cant find an artifact
>>>> corresponding to the JAXB BOM's dependency on the stax-ex version 1.7.7 in
>>>> repo1. Am I missing something? The actual dependency snippet from the BOM
>>>> is found below:
>>>>
>>>>             <dependency>                
>>>> <groupId>org.jvnet.staxex</groupId>                
>>>> <artifactId>stax-ex</artifactId>                
>>>> <version>${stax-ex.version}</version>                <exclusions>          
>>>>           <!-- part of JDK 6+ -->                    <exclusion>           
>>>>              <groupId>javax.activation</groupId>                        
>>>> <artifactId>activation</artifactId>                    </exclusion>        
>>>>             <exclusion>                        
>>>> <artifactId>stax-api</artifactId>                        
>>>> <groupId>javax.xml.stream</groupId>                    </exclusion>        
>>>>         </exclusions>            </dependency>
>>>>
>>>>
>>>>
>>>>
>>>> 2014-11-18 22:20 GMT+01:00 Anders Hammar <and...@hammar.net>:
>>>>
>>>>>
>>>>>>    1. The org.glassfish.jaxb:jaxb-runtime:2.2.12 depends on the
>>>>>>    artifact org.jvnet.staxex:stax-ex:1.7.7 which I can't find in repo1.
>>>>>>    (Version 1.7.6 is present, though). I can test refactoring the plugin 
>>>>>> using
>>>>>>    the 1.7.6 version, but I would rather that the normal dependency set 
>>>>>> of the
>>>>>>    jaxb-runtime can be included in the plugin without any special 
>>>>>> measures.
>>>>>>    Can you find the stax-ex dependency version 1.7.7 somewhere (... i.e. 
>>>>>> is it
>>>>>>    just me being blind...?)
>>>>>>
>>>>>>
>>>>> Why org.glassfish.jaxb:jaxb-runtime:2.2.12? 2.2.11 is the one used for
>>>>> JAXB RI v2.2.11.
>>>>> They now have a BOM [1] that we could use.
>>>>>
>>>>>
>>>>>>
>>>>>>    1. Parts of JAXB plugin's structure reflects the former JAXB
>>>>>>    distribution (Packages, introspection etc.) This will obviously need
>>>>>>    upgrading - to the point where I feel that we should release a new 
>>>>>> major
>>>>>>    version for the JAXB plugin. It will simply not be backwards 
>>>>>> compatible any
>>>>>>    more. I will start the implementation of this, but it implies some 
>>>>>> heavy
>>>>>>    lifting underhood.
>>>>>>
>>>>>> Cool go for it. Bumping major version is good in this case I think.
>>>>>
>>>>> [1]
>>>>> https://repo1.maven.org/maven2/org/glassfish/jaxb/jaxb-bom/2.2.11/jaxb-bom-2.2.11.pom
>>>>>
>>>>> /Anders
>>>>>
>>>>>>
>>>>>>    1.
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> --
>>>>>> +==============================+
>>>>>> | 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
>>> +==============================+
>>>
>>>
>>
>
>
> --
>
> --
> +==============================+
> | 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
+==============================+

Reply via email to