Hi Dennis,
Yes & No, this is a module Gradle build of trunk, looking forward to
some contribution from you on that front. We're currently trying to
figure out how to move other components of the project, such as the
site, ldj tests and other contributions.
Perhaps we should move http://svn.apache.org/viewvc/river/jtsk/ now,
then people who want to focus on trunk can proceed, eg the gradle build
and then move the remaining parts of http://svn.apache.org/viewvc/river/
later?
artwork/ <http://svn.apache.org/viewvc/river/artwork/> *1069292*
<http://svn.apache.org/viewvc/river/artwork/?view=log> 10 years
gmcdonald River now a TLP
attic/ <http://svn.apache.org/viewvc/river/attic/> *1069292*
<http://svn.apache.org/viewvc/river/attic/?view=log> 10 years
gmcdonald River now a TLP
extra/ <http://svn.apache.org/viewvc/river/extra/> *1069292*
<http://svn.apache.org/viewvc/river/extra/?view=log> 10 years
gmcdonald River now a TLP
jtsk/ <http://svn.apache.org/viewvc/river/jtsk/> *1884639*
<http://svn.apache.org/viewvc/river/jtsk/?view=log> 8 weeks
peter_firmstone replace trunk with modules branch
ldj-tests/ <http://svn.apache.org/viewvc/river/ldj-tests/> *1234443*
<http://svn.apache.org/viewvc/river/ldj-tests/?view=log> 9 years
peter_firmstone River-32 The Jini spec tests inside the qa suite used
used to be called tck, so…
permission_delegates/
<http://svn.apache.org/viewvc/river/permission_delegates/> *1394888*
<http://svn.apache.org/viewvc/river/permission_delegates/?view=log> 8
years peter_firmstone upload delegate implementations
river-examples/ <http://svn.apache.org/viewvc/river/river-examples/>
*1694732* <http://svn.apache.org/viewvc/river/river-examples/?view=log>
5 years gtrasuk [maven-release-plugin] prepare for next development
iteration
river-rt-tools/ <http://svn.apache.org/viewvc/river/river-rt-tools/>
*1645730* <http://svn.apache.org/viewvc/river/river-rt-tools/?view=log>
6 years gtrasuk Start package now references the correct message
bundle, and can start the brows…
site/ <http://svn.apache.org/viewvc/river/site/> *1827149*
<http://svn.apache.org/viewvc/river/site/?view=log> 2 years zkuti -
alerts for helping hands - long due changes in people added - success
stories …
doap_river.rdf <http://svn.apache.org/viewvc/river/doap_river.rdf?view=log>
Regards,
Peter.
On 16/02/2021 6:19 am, Dennis Reedy wrote:
I did this conversion a while ago, does this help?
https://github.com/dreedyman/apache-river
<https://github.com/dreedyman/apache-river>
Regards
Dennis
On Mon, Feb 15, 2021 at 2:44 PM Dan Rollo <danro...@gmail.com
<mailto:danro...@gmail.com>> wrote:
Hi Peter,
Silly questions to follow.
I found the empty repo at: river-ldj-tests.git
<https://git.apache.org/repos/asf/river-ldj-tests.git
<https://git.apache.org/repos/asf/river-ldj-tests.git>>
(https://git.apache.org/repos/asf/river-ldj-tests.git
<https://git.apache.org/repos/asf/river-ldj-tests.git>)
As a sanity check: Is the one to migrate from?:
http://svn.apache.org/repos/asf/river/jtsk/trunk
<http://svn.apache.org/repos/asf/river/jtsk/trunk>
While I agree refactoring of the project structure into separate,
stand alone git repos would be an improvement, I’m wondering if a
safer first step would be to move the svn repo to git as is? That
way, we start from a working state in git, and preserve all the
svn history. From there, we can start to “break things” (literally
and figuratively) into smaller repos. The underlying assumption is
just about everything will be easier to do (merging, etc) with a
git repo.
Either way, I’ll start looking for lines along which I could break
things.
Dan
> On Feb 9, 2021, at 3:42 AM, Peter Firmstone
<peter.firmst...@zeus.net.au <mailto:peter.firmst...@zeus.net.au>>
wrote:
>
> Thanks Dan,
>
> https://infra.apache.org/svn-to-git-migration.html
<https://infra.apache.org/svn-to-git-migration.html>
>
> https://gitbox.apache.org/setup/newrepo.html
<https://gitbox.apache.org/setup/newrepo.html>
>
> http://svn.apache.org/viewvc/river/
<http://svn.apache.org/viewvc/river/>
>
> https://gitbox.apache.org/repos/asf#river
<https://gitbox.apache.org/repos/asf#river>
>
> I just created a git repository for the "Apache river JiniTM
Technology Lookup, Discovery, and Join Compatibility Kit", I
figure it might be easier to start with something that's had
relatively few commits as an experiment.
>
> But basically everything we have on svn needs to be broken up
into separate projects, typical of what people are used to seeing
on github.
>
> The QA test suite is an ant build project, it's currently part
of trunk, but I was thinking of separating it out into it's own build.
>
> On 9/02/2021 12:31 pm, Dan Rollo wrote:
>> Hi Peter,
>>
>> I’m apologize for not being more help. I haven’t had much time
of late. Is there a thread I could pull regarding the Git
migration? Where to start?
>>
>> The plan you itemize makes sense to me.
>>
>> Dan Rollo
>>
>>> On Feb 8, 2021, at 8:35 PM, Peter Firmstone
<peter.firmst...@zeus.net.au <mailto:peter.firmst...@zeus.net.au>>
wrote:
>>>
>>> Hello River folk,
>>>
>>> There's an upcoming board report due shortly, I wanted to
gauge people's interest in the project.
>>>
>>> We've got two pending tasks:
>>>
>>> 1. SVN to Git Migration
>>> 2. Website migration
>>>
>>> Following the Git Migration, the plan is to continue with the
modular build, using gradle?
>>>
>>> Lately we don't have a lot of participation, I was hoping that
we would have some more buy in, especially with the Git migration.
>>>
>>> I don't want to be making decisions alone, are there people on
this list who have time to assist, are willing to assist or intend
to do so in future when they have time?
>>>
>>> --
>>> Regards,
>>> Peter Firmstone
>>>
> --
> Regards,
> Peter Firmstone
>
--
Regards,
Peter Firmstone
0498 286 363
Zeus Project Services Pty Ltd.
