I haven’t tried it, but what about a pattern like ‘dot[.]branch’? The ‘.’ is
then part of a character set match. If it works (and as a regex it should)
this allows for the use of regex patterns as part of ‘dot’ and ‘branch’.
> On 7 Dec 2016, at 1:15 am, Jaikiran Pai
That served me perfectly, Jaikiran.
Thank you very much!
Gabriel
On Tue, Dec 6, 2016 at 12:15 PM, Jaikiran Pai
wrote:
> Looking at the Ivy code, it appears that it's using a exactOrRegex matcher
> (by default) for matching the org/module/branch values and it's
Looking at the Ivy code, it appears that it's using a exactOrRegex
matcher (by default) for matching the org/module/branch values and it's
considering the . within the branch value as a regex and that causes
weirdness. I just ran a test to see if using something like
"dot\.branch" (notice the
I would advice to have a look at the documentation for repreport.
I remember something that there are specific requirements for the pattern
of the repositories.
If you are using ivy-banches, I suppose they must be grouped in separate
directories. The same for the revisions.
Marc
2016-12-02
I ran some tests with debug enabled and I notice some differences in the
logs.
As an example, calling:
**
logs:
...
[ivy:repreport] using maggie to list all in
\\192.168.0.1\root\ivyrep\dist\Apache\log4j
[ivy:repreport] using maggie to list all in
Since branches often refer to versions or releases, it is not unusual that
they contain dots in their names.
We also have dots in the name of our branches and don't have any problems
with it.
Maybe you can execute your repreport with debugging enabled ?
Regards
Marc
2016-12-02 16:54 GMT+01:00
Hello,
I'm calling a basic repreport for a module on my local repo:
Most of the time, the task behaves as expected but every time the branch
contains a '.' it outputs an empty report (the same behavior as if the
branch didn't exist).
Does this limitation make sense?
May I be hitting a bug?
Is