You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Mukul Gandhi <mu...@apache.org> on 2019/10/28 11:25:53 UTC

should we have only one location of Xerces-J codebase

Hi all,
    Currently, we have following two active source code locations for
Xerces-J,

1) https://svn.apache.org/repos/asf/xerces/java/trunk/
2) https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/

Location 2) has all the functionality what location 1) has, and
additionally an XSD 1.1 implementation.

Can we make present contents of location 2) as the contents of trunk? And
consider, present codebase on trunk as archived and move it to a folder
like 'archive' on the svn.

I think, this shall ease the maintenance efforts for Xerces-J going
forward. With this, in future we would only develop for trunk (which will
have present codebase of location '2)') and shall release only a single
variant of Xerces-J (unlike presently, where we release one build from
trunk and another one from location '2)').

What do people on this list think about above mentioned suggestions?



-- 
Regards,
Mukul Gandhi

Re: should we have only one location of Xerces-J codebase

Posted by Mukul Gandhi <mu...@apache.org>.
Hi all,
    Given the lack of wider consensus on the list about the topic I've
raised below, lets keep the Xerces-J source repositories and process as
they're currently (i.e I give up my ideas mentioned in mail trail below).

I've also rethought about the below mentioned issues and think that, how
Xerces-J source repositories and process are structured currently is
valuable.

On Mon, Oct 28, 2019 at 4:55 PM Mukul Gandhi <mu...@apache.org> wrote:


> Currently, we have following two active source code locations for Xerces-J,
>
> 1) https://svn.apache.org/repos/asf/xerces/java/trunk/
> 2)
> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/
>
> Location 2) has all the functionality what location 1) has, and
> additionally an XSD 1.1 implementation.
>
> Can we make present contents of location 2) as the contents of trunk? And
> consider, present codebase on trunk as archived and move it to a folder
> like 'archive' on the svn.
>
> I think, this shall ease the maintenance efforts for Xerces-J going
> forward. With this, in future we would only develop for trunk (which will
> have present codebase of location '2)') and shall release only a single
> variant of Xerces-J (unlike presently, where we release one build from
> trunk and another one from location '2)').
>
> What do people on this list think about above mentioned suggestions?
>




-- 
Regards,
Mukul Gandhi

Re: should we have only one location of Xerces-J codebase

Posted by Mukul Gandhi <mu...@apache.org>.
On Mon, Oct 28, 2019 at 5:56 PM Enrico Olivelli <eo...@gmail.com> wrote:

> Can you please also consider switching to ASF gitbox/github ?
> This will ease contributions.
>

As far as I know, ASF hasn't deprecated the use of SVN in place of GitBox
as a version control system. Migration of Xerces-J to GitBox could be done,
if majority of Xerces-J committers and pmc members agree to it.

I personally think that, SVN is still a fairly good version control system
& collaboration tool.



-- 
Regards,
Mukul Gandhi

Re: should we have only one location of Xerces-J codebase

Posted by Mukul Gandhi <mu...@apache.org>.
On Mon, Oct 28, 2019 at 8:49 PM Gary Gregory <ga...@gmail.com> wrote:

> On Mon, Oct 28, 2019 at 10:21 AM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
>> Can you please also consider switching to ASF gitbox/github ?
>> This will ease contributions.
>>
>
> This has help us a lot in Commons.
>
>
Thinking about having only a single build for Xerces-J (that has XSD 1.1
with all other Xerces-J functionalities), I think that it could be slightly
problematic for XalanJ to consume. I think that, considering the impact of
Xerces-J moving to a single build, to XalanJ is important.

Including a future Xerces-J build (that includes XSD 1.1) by XalanJ, might
require XalanJ in future to also ship following new jars (that are provided
by Xerces XSD 1.1 build),
cupv10k-runtime.jar
icu4j.jar
org.eclipse.wst.xml.xpath2.processor_1.2.0.jar
resolver.jar
Is this right and convenient for XalanJ?



-- 
Regards,
Mukul Gandhi

Re: should we have only one location of Xerces-J codebase

Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Oct 28, 2019 at 10:21 AM Enrico Olivelli <eo...@gmail.com>
wrote:

> Hello,
> Can you please also consider switching to ASF gitbox/github ?
> This will ease contributions.
>

This has help us a lot in Commons.

Gary


>
> Sorry for being slightly off topic
>
> Enrico
>
> Il lun 28 ott 2019, 12:26 Mukul Gandhi <mu...@apache.org> ha scritto:
>
>> Hi all,
>>     Currently, we have following two active source code locations for
>> Xerces-J,
>>
>> 1) https://svn.apache.org/repos/asf/xerces/java/trunk/
>> 2)
>> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/
>>
>> Location 2) has all the functionality what location 1) has, and
>> additionally an XSD 1.1 implementation.
>>
>> Can we make present contents of location 2) as the contents of trunk? And
>> consider, present codebase on trunk as archived and move it to a folder
>> like 'archive' on the svn.
>>
>> I think, this shall ease the maintenance efforts for Xerces-J going
>> forward. With this, in future we would only develop for trunk (which will
>> have present codebase of location '2)') and shall release only a single
>> variant of Xerces-J (unlike presently, where we release one build from
>> trunk and another one from location '2)').
>>
>> What do people on this list think about above mentioned suggestions?
>>
>>
>>
>> --
>> Regards,
>> Mukul Gandhi
>>
>

Re: should we have only one location of Xerces-J codebase

Posted by Enrico Olivelli <eo...@gmail.com>.
Hello,
Can you please also consider switching to ASF gitbox/github ?
This will ease contributions.

Sorry for being slightly off topic

Enrico

Il lun 28 ott 2019, 12:26 Mukul Gandhi <mu...@apache.org> ha scritto:

> Hi all,
>     Currently, we have following two active source code locations for
> Xerces-J,
>
> 1) https://svn.apache.org/repos/asf/xerces/java/trunk/
> 2)
> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/
>
> Location 2) has all the functionality what location 1) has, and
> additionally an XSD 1.1 implementation.
>
> Can we make present contents of location 2) as the contents of trunk? And
> consider, present codebase on trunk as archived and move it to a folder
> like 'archive' on the svn.
>
> I think, this shall ease the maintenance efforts for Xerces-J going
> forward. With this, in future we would only develop for trunk (which will
> have present codebase of location '2)') and shall release only a single
> variant of Xerces-J (unlike presently, where we release one build from
> trunk and another one from location '2)').
>
> What do people on this list think about above mentioned suggestions?
>
>
>
> --
> Regards,
> Mukul Gandhi
>