That’s correct. I’ll raise a JIRA. thanks
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Michael Anstis
Sent: Wednesday, June 11, 2014 4:36 PM
To: Rules Users List
Subject: Re: [rules-users] Can't clone repository NoSuchElementException
If I read your email correctly you're saying cloning a non-bare repository works ok
provided it has a unique name?
However we should better (a) document a repository cannot be bare if it is to be cloned
into the workbench and (b) validate names of new or cloned repositories.
If I understand correctly then yes please raise a JIRA for Guvnor.
Thanks,
Mike
Sent on the move
On 11 Jun 2014 21:28, "Parham, Clinton"
<cparham@biosignia.com<mailto:cparham@biosignia.com>> wrote:
Hi Michael,
Ok, some progress.
Here’s what I’ve found:
If I first try cloning a bare repo (say I call it “test”), it fails with “Can't clone
repository. java.util.NoSuchElementException”. So I assume nothing happened… but at the
file system level I see the “test” repo in the drools/brms git folder. It doesn’t show in
the BusinessCentral/Guvnor repo list.
If I then try again to clone, using “test” (because I don’t know of the conflict) but pull
from a populated repo, it still fails with “Can't clone repository.
java.util.NoSuchElementException”. But this is because “test” actually exists at the file
system level. If I change my Repo Name to something that doesn’t exist in the git folder,
it clones just fine.
Sounds like a bug that should be reported, yes?
Thanks.
From:
rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org>
[mailto:rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org>]
On Behalf Of Michael Anstis
Sent: Wednesday, June 11, 2014 2:07 PM
To: Rules Users List
Subject: Re: [rules-users] Can't clone repository NoSuchElementException
Have you tried a non-bare repo? (I don't know if this will solve the issue but IIRC we
normally use non-bare when testing).
Sent on the move
On 11 Jun 2014 03:46, "Parham, Clinton"
<cparham@biosignia.com<mailto:cparham@biosignia.com>> wrote:
Hello,
I have Drools 6.0.1 installed on RedHat Linux 5 and running under JBoss EAP 6.1.1.
I would like to clone from a local git server running on the same server. But when I do
so, I get a “Can't clone repository. java.util.NoSuchElementException” message in the
browser. There are no errors in the server.log
Why doesn’t this work?
Here’s how I’m running the git daemon:
$ git daemon --verbose --export-all --port=9419 --base-path=/home/brms/git/
URL I enter into the Clone Repository dialog:
git://localhost:9419/test.git
This is how I setup my repo:
$ cd /home/brms/git/
$ mkdir test.git
$ cd test.git/
$ git init --bare
Initialized empty Git repository in /home/brms/git/test.git/
Thanks,
Clint
________________________________
The contents contained herein may contain confidential information. If you are not the
intended recipient, you are hereby notified that any disclosure, copying, distribution,
printing or action taken on the contents is strictly prohibited. If you have received this
email in error, please notify the sender immediately and delete this message.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
________________________________
The contents contained herein may contain confidential information. If you are not the
intended recipient, you are hereby notified that any disclosure, copying, distribution,
printing or action taken on the contents is strictly prohibited. If you have received this
email in error, please notify the sender immediately and delete this message.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
________________________________
The contents contained herein may contain confidential information. If you are not the
intended recipient, you are hereby notified that any disclosure, copying, distribution,
printing or action taken on the contents is strictly prohibited. If you have received this
email in error, please notify the sender immediately and delete this message.