[jira] [Closed] (WAGON-484) Update WebDAV Provider naming
[ https://issues.apache.org/jira/browse/WAGON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-484. Resolution: Fixed Fixed with [01b5631f2712d4a983c2f43f7a0b0d3df784501a|https://git-wip-us.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=01b5631f2712d4a983c2f43f7a0b0d3df784501a]. > Update WebDAV Provider naming > - > > Key: WAGON-484 > URL: https://issues.apache.org/jira/browse/WAGON-484 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-webdav >Affects Versions: 2.11 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Trivial > Fix For: 2.12 > > > There are a bunch of styles throughout the project how WebDAV is written. Use > the canonical name: WebDAV. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MPIR-352) use protocol agnostic url for gravatar
[ https://issues.apache.org/jira/browse/MPIR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-352: --- Assignee: Michael Osipov > use protocol agnostic url for gravatar > --- > > Key: MPIR-352 > URL: https://issues.apache.org/jira/browse/MPIR-352 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: team >Affects Versions: 2.9 >Reporter: Eric Barboni >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.10 > > Attachments: gravatarpir.diff > > > Hi, > Team page deployed on https server use http scheme for gravatar image that > lead to partial secure page. > According to the followin page: > https://fr.gravatar.com/site/implement/images/ section "Secure Requests" > I made a little patch to use the protocol agnostic scheme for Team page > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPIR-352) use protocol agnostic url for gravatar
[ https://issues.apache.org/jira/browse/MPIR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801938#comment-15801938 ] Michael Osipov commented on MPIR-352: - While this seems to be correct, note that the page won't work offline anymore. > use protocol agnostic url for gravatar > --- > > Key: MPIR-352 > URL: https://issues.apache.org/jira/browse/MPIR-352 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: team >Affects Versions: 2.9 >Reporter: Eric Barboni >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.10 > > Attachments: gravatarpir.diff > > > Hi, > Team page deployed on https server use http scheme for gravatar image that > lead to partial secure page. > According to the followin page: > https://fr.gravatar.com/site/implement/images/ section "Secure Requests" > I made a little patch to use the protocol agnostic scheme for Team page > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-974) https in project tag
[ https://issues.apache.org/jira/browse/MRELEASE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801951#comment-15801951 ] Michael Osipov commented on MRELEASE-974: - There seems to be a misunderstand of the concept of XML namespaces. The namespace is an arbitrary URI, in this case an HTTP URL, it does not even has to exist. It is an opaque token not to be modified by you, but solely reserved by us for our schema. It remains fixed. You can host the schema whereever you want, though. Unless you want the schema to be served by HTTPS, this is a won't fix. > https in project tag > > > Key: MRELEASE-974 > URL: https://issues.apache.org/jira/browse/MRELEASE-974 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: Jeremy Landis >Priority: Minor > > In the pom on the tag, I'd like to use https as they are available > for the xmlns, xmlns:xsi, and xsi:schemaLocation locations. When I run other > plugins it's fine but if I try to release it fails. It initially fails with > xmlns:xsi issue. If I set that back to http, then it flags tags all with > http throughout and crashes. > What I have to use now... > ``` > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > What I would like to use... > ``` > https://maven.apache.org/POM/4.0.0"; > xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="https://maven.apache.org/POM/4.0.0 > https://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > Is this possible? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WAGON-484) Update WebDAV Provider naming
[ https://issues.apache.org/jira/browse/WAGON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801976#comment-15801976 ] Hudson commented on WAGON-484: -- SUCCESS: Integrated in Jenkins build maven-wagon #1333 (See [https://builds.apache.org/job/maven-wagon/1333/]) [WAGON-484] Update WebDAV Provider naming (michaelo: [http://git-wip-us.apache.org/repos/asf/?p=maven-wagon.git&a=commit&h=01b5631f2712d4a983c2f43f7a0b0d3df784501a]) * (edit) wagon-providers/wagon-webdav-jackrabbit/src/test/java/org/apache/maven/wagon/providers/webdav/WebDavWagonTest.java * (edit) wagon-providers/wagon-webdav-jackrabbit/pom.xml * (edit) wagon-providers/wagon-webdav-jackrabbit/src/main/resources/META-INF/plexus/default-bindings.xml * (edit) wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/WebDavWagon.java * (edit) pom.xml * (edit) wagon-providers/wagon-webdav-jackrabbit/src/site/site.xml > Update WebDAV Provider naming > - > > Key: WAGON-484 > URL: https://issues.apache.org/jira/browse/WAGON-484 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-webdav >Affects Versions: 2.11 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Trivial > Fix For: 2.12 > > > There are a bunch of styles throughout the project how WebDAV is written. Use > the canonical name: WebDAV. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-681) Add timestamp when each test is run in the generated report
[
https://issues.apache.org/jira/browse/SUREFIRE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802202#comment-15802202
]
Cheng Xu commented on SUREFIRE-681:
---
[~tibor17] It looks like an addition to the TEST-...xml would suffice. I'm
thinking right next to the elapsed time would be:
{code}
{code}
Maybe we can have a config property set to false by default and turned on by:
true
> Add timestamp when each test is run in the generated report
> ---
>
> Key: SUREFIRE-681
> URL: https://issues.apache.org/jira/browse/SUREFIRE-681
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Viggo Navarsete
>
> We run integration tests using maven-surefire-plugin by filtering on the
> names (they end with *TestIntegration). These tests access a JBoss server,
> and leave log entires in the server log. When a test fail, it would be great
> to have a timestamp on each test in the test report from surefire so that it
> can be matched against what is happening in the server log. This is
> especially true when you have a lot of integration tests running and you
> can't directly spot the server log entries related to the failing test. By
> adding a timestamp to the tests it would make it MUCH easier to figure out
> the server log dependent calls.
> Current output:
> {noformat]
> ---
> Test set: com.tracetracker.gqi3.QueryRestTestIntegration
> ---
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec
> <<< FAILURE!
> testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: List of recordTime should not be empty
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
> {noformat}
> Each failing test should have the timestamp added to the start of the line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRELEASE-974) https in project tag
[ https://issues.apache.org/jira/browse/MRELEASE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803229#comment-15803229 ] Jeremy Landis commented on MRELEASE-974: Not really a misunderstanding issue but rather I am trying to remove any reference from 'http' throughout my code bases. What I didn't expect was the release plugin to fail. The addSchema false optino makes sense as maven has always rewritten the project tag which affects my formatting. Eventually I gave up on that formatting not knowing I could disable that behaviour. If that works for me (haven't tried yet), then the work around is perfect. Can you tell me a bit more on what exactly maven is doing internally that required the rewriting of project tag in the first place? > https in project tag > > > Key: MRELEASE-974 > URL: https://issues.apache.org/jira/browse/MRELEASE-974 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: Jeremy Landis >Priority: Minor > > In the pom on the tag, I'd like to use https as they are available > for the xmlns, xmlns:xsi, and xsi:schemaLocation locations. When I run other > plugins it's fine but if I try to release it fails. It initially fails with > xmlns:xsi issue. If I set that back to http, then it flags tags all with > http throughout and crashes. > What I have to use now... > ``` > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > What I would like to use... > ``` > https://maven.apache.org/POM/4.0.0"; > xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="https://maven.apache.org/POM/4.0.0 > https://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > Is this possible? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MRELEASE-974) https in project tag
[ https://issues.apache.org/jira/browse/MRELEASE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803229#comment-15803229 ] Jeremy Landis edited comment on MRELEASE-974 at 1/6/17 2:04 AM: Not really a misunderstanding issue but rather I am trying to remove any reference from 'http' throughout my code bases. What I didn't expect was the release plugin to fail. The addSchema false option makes sense as maven has always rewritten the project tag which affects my formatting. Eventually I gave up on that formatting not knowing I could disable that behaviour. If that works for me (haven't tried yet), then the work around is perfect. Can you tell me a bit more on what exactly maven is doing internally that required the rewriting of project tag in the first place? was (Author: hazendaz): Not really a misunderstanding issue but rather I am trying to remove any reference from 'http' throughout my code bases. What I didn't expect was the release plugin to fail. The addSchema false optino makes sense as maven has always rewritten the project tag which affects my formatting. Eventually I gave up on that formatting not knowing I could disable that behaviour. If that works for me (haven't tried yet), then the work around is perfect. Can you tell me a bit more on what exactly maven is doing internally that required the rewriting of project tag in the first place? > https in project tag > > > Key: MRELEASE-974 > URL: https://issues.apache.org/jira/browse/MRELEASE-974 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5.3 >Reporter: Jeremy Landis >Priority: Minor > > In the pom on the tag, I'd like to use https as they are available > for the xmlns, xmlns:xsi, and xsi:schemaLocation locations. When I run other > plugins it's fine but if I try to release it fails. It initially fails with > xmlns:xsi issue. If I set that back to http, then it flags tags all with > http throughout and crashes. > What I have to use now... > ``` > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > What I would like to use... > ``` > https://maven.apache.org/POM/4.0.0"; > xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="https://maven.apache.org/POM/4.0.0 > https://maven.apache.org/xsd/maven-4.0.0.xsd";> > ``` > Is this possible? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-681) Add timestamp when each test is run in the generated report
[
https://issues.apache.org/jira/browse/SUREFIRE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803280#comment-15803280
]
Tibor Digana commented on SUREFIRE-681:
---
We can extend the XSD schema with two optional XML attributes as you have
proposed in the XML test result.
Can you open PR and implement it?
I am going to push several commits and then cut a release version so I do
not guarantee that your PR would be able to merge to master if you was
faster to commit than me.
You can simplify naming *testCaseStartTime *to *startTime *because it's
obvious that we are in test-case element.
Same with end time.
I am not sure if we are writing time format already in the xml report file,
but if we do so then we should keep it here the same format as well.
> Add timestamp when each test is run in the generated report
> ---
>
> Key: SUREFIRE-681
> URL: https://issues.apache.org/jira/browse/SUREFIRE-681
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Viggo Navarsete
>
> We run integration tests using maven-surefire-plugin by filtering on the
> names (they end with *TestIntegration). These tests access a JBoss server,
> and leave log entires in the server log. When a test fail, it would be great
> to have a timestamp on each test in the test report from surefire so that it
> can be matched against what is happening in the server log. This is
> especially true when you have a lot of integration tests running and you
> can't directly spot the server log entries related to the failing test. By
> adding a timestamp to the tests it would make it MUCH easier to figure out
> the server log dependent calls.
> Current output:
> {noformat]
> ---
> Test set: com.tracetracker.gqi3.QueryRestTestIntegration
> ---
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec
> <<< FAILURE!
> testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: List of recordTime should not be empty
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
> {noformat}
> Each failing test should have the timestamp added to the start of the line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-681) Add timestamp when each test is run in the generated report
[
https://issues.apache.org/jira/browse/SUREFIRE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803293#comment-15803293
]
Tibor Digana commented on SUREFIRE-681:
---
We do not need to have _dateTimeBoundaries_ in config yet. If the people are
shouting to introduce it we will do so but optional attribute in xsd should
just fine.
> Add timestamp when each test is run in the generated report
> ---
>
> Key: SUREFIRE-681
> URL: https://issues.apache.org/jira/browse/SUREFIRE-681
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Viggo Navarsete
>
> We run integration tests using maven-surefire-plugin by filtering on the
> names (they end with *TestIntegration). These tests access a JBoss server,
> and leave log entires in the server log. When a test fail, it would be great
> to have a timestamp on each test in the test report from surefire so that it
> can be matched against what is happening in the server log. This is
> especially true when you have a lot of integration tests running and you
> can't directly spot the server log entries related to the failing test. By
> adding a timestamp to the tests it would make it MUCH easier to figure out
> the server log dependent calls.
> Current output:
> {noformat]
> ---
> Test set: com.tracetracker.gqi3.QueryRestTestIntegration
> ---
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec
> <<< FAILURE!
> testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: List of recordTime should not be empty
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
> {noformat}
> Each failing test should have the timestamp added to the start of the line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-681) Add timestamp when each test is run in the generated report
[
https://issues.apache.org/jira/browse/SUREFIRE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803886#comment-15803886
]
Michael Osipov commented on SUREFIRE-681:
-
There is nothing like this in {{surefire-test-report.xsd}}. We can simply use
{{xs:dateTime}}, that's it.
> Add timestamp when each test is run in the generated report
> ---
>
> Key: SUREFIRE-681
> URL: https://issues.apache.org/jira/browse/SUREFIRE-681
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Viggo Navarsete
>
> We run integration tests using maven-surefire-plugin by filtering on the
> names (they end with *TestIntegration). These tests access a JBoss server,
> and leave log entires in the server log. When a test fail, it would be great
> to have a timestamp on each test in the test report from surefire so that it
> can be matched against what is happening in the server log. This is
> especially true when you have a lot of integration tests running and you
> can't directly spot the server log entries related to the failing test. By
> adding a timestamp to the tests it would make it MUCH easier to figure out
> the server log dependent calls.
> Current output:
> {noformat]
> ---
> Test set: com.tracetracker.gqi3.QueryRestTestIntegration
> ---
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec
> <<< FAILURE!
> testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: List of recordTime should not be empty
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
> {noformat}
> Each failing test should have the timestamp added to the start of the line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-681) Add timestamp when each test is run in the generated report
[
https://issues.apache.org/jira/browse/SUREFIRE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-681:
Description:
We run integration tests using maven-surefire-plugin by filtering on the names
(they end with *TestIntegration). These tests access a JBoss server, and leave
log entires in the server log. When a test fail, it would be great to have a
timestamp on each test in the test report from surefire so that it can be
matched against what is happening in the server log. This is especially true
when you have a lot of integration tests running and you can't directly spot
the server log entries related to the failing test. By adding a timestamp to
the tests it would make it MUCH easier to figure out the server log dependent
calls.
Current output:
{noformat}
---
Test set: com.tracetracker.gqi3.QueryRestTestIntegration
---
Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec <<<
FAILURE!
testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
Time elapsed: 0.031 sec <<< FAILURE!
junit.framework.AssertionFailedError: List of recordTime should not be empty
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
{noformat}
Each failing test should have the timestamp added to the start of the line.
was:
We run integration tests using maven-surefire-plugin by filtering on the names
(they end with *TestIntegration). These tests access a JBoss server, and leave
log entires in the server log. When a test fail, it would be great to have a
timestamp on each test in the test report from surefire so that it can be
matched against what is happening in the server log. This is especially true
when you have a lot of integration tests running and you can't directly spot
the server log entries related to the failing test. By adding a timestamp to
the tests it would make it MUCH easier to figure out the server log dependent
calls.
Current output:
{noformat]
---
Test set: com.tracetracker.gqi3.QueryRestTestIntegration
---
Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec <<<
FAILURE!
testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
Time elapsed: 0.031 sec <<< FAILURE!
junit.framework.AssertionFailedError: List of recordTime should not be empty
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
com.tracetracker.gqi3.QueryRestTestIntegration.testSimpleEventQueryRecordTime(QueryRestTestIntegration.java:283)
{noformat}
Each failing test should have the timestamp added to the start of the line.
> Add timestamp when each test is run in the generated report
> ---
>
> Key: SUREFIRE-681
> URL: https://issues.apache.org/jira/browse/SUREFIRE-681
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Viggo Navarsete
>
> We run integration tests using maven-surefire-plugin by filtering on the
> names (they end with *TestIntegration). These tests access a JBoss server,
> and leave log entires in the server log. When a test fail, it would be great
> to have a timestamp on each test in the test report from surefire so that it
> can be matched against what is happening in the server log. This is
> especially true when you have a lot of integration tests running and you
> can't directly spot the server log entries related to the failing test. By
> adding a timestamp to the tests it would make it MUCH easier to figure out
> the server log dependent calls.
> Current output:
> {noformat}
> ---
> Test set: com.tracetracker.gqi3.QueryRestTestIntegration
> ---
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.546 sec
> <<< FAILURE!
> testSimpleEventQueryRecordTime(com.tracetracker.gqi3.QueryRestTestIntegration)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: List of recordTime should not be empty
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> com.tracetracker.gqi3.Query
