[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481005#comment-17481005
]
Andy Seaborne commented on JENA-2213:
-
No - I have not taken the values from your comment. The PR was
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481005#comment-17481005
]
Andy Seaborne edited comment on JENA-2213 at 1/24/22, 10:59 AM:
No - I
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Neumann closed JENA-2213.
---
Fix Version/s: Jena 4.4.0
Resolution: Fixed
changes to values in tests have been made to suit
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480968#comment-17480968
]
Andy Seaborne commented on JENA-2213:
-
Reopened and marked "resolved" which is how we managed tickets
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reopened JENA-2213:
-
> Jena GeoSPARQL Tests Fail With SIS 1.1
> --
>
>
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480983#comment-17480983
]
Marco Neumann commented on JENA-2213:
-
[~andy] if you have used the values from the diff as posted we
[
https://issues.apache.org/jira/browse/JENA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481063#comment-17481063
]
Marco Neumann commented on JENA-2213:
-
Ok I see [~andy] not a big deal these current values now will
1/ jena-fuseki-ui
When I run maven, the yarn.lock file is being changed.
Most changes are to do with "integrity" beginning deleted.
"@babel/core@^7.11.0":
version "7.16.7"
resolved
"https://registry.yarnpkg.com/@babel/core/-/core-7.16.7.tgz#db990f931f6d40cb9b87a0dc7d2adc749f1dcbcf;
-
On 24/01/2022 13:16, Andy Seaborne wrote:
2/ Java11.
That might have been an upstream fix. The offending search.js seems to
be a different size. But this is fragile as to which tools generated
the javadoc,
For now
1: remove the breaking fix.
2: see what happens
3: if no better
On 24/01/2022 13:16, Andy Seaborne wrote:
1/ jena-fuseki-ui
When I run maven, the yarn.lock file is being changed.
Most changes are to do with "integrity" beginning deleted.
"@babel/core@^7.11.0":
version "7.16.7"
resolved
I was building locally yesterday and got the same error message on the ui
module. However when I deleted node_modules before building it completed
successfully. Is there any cache on the apache CI build server or is there
something else at work?
This was on
[
https://issues.apache.org/jira/browse/JENA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481237#comment-17481237
]
ASF subversion and git services commented on JENA-2232:
---
Commit
[
https://issues.apache.org/jira/browse/JENA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481236#comment-17481236
]
ASF subversion and git services commented on JENA-2232:
---
Commit
The range of our UI dependencies is probably allowing for updates. When
running `yarn install` it is either finding new versions that match the
range (since the last time someone run yarn install and updated the lock
file), or a developer modified a dependency in NPM (harder to happen I
think).
I
[
https://issues.apache.org/jira/browse/JENA-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481281#comment-17481281
]
ASF subversion and git services commented on JENA-2258:
---
Commit
On 24/01/2022 18:46, Bruno Kinoshita wrote:
Taking a look at it today. In another project I bumped the version of Yarn
to v3 (we are using v1 I think, v2 is stable, v3 is the greatest and
latest). Will see if that solves the changes in the lock file, and also
look why the build is failing.
[
https://issues.apache.org/jira/browse/JENA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481275#comment-17481275
]
Andy Seaborne commented on JENA-2253:
-
The test artifacts for jena-base, jena-core and jena-arq now
[
https://issues.apache.org/jira/browse/JENA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2253.
-
Fix Version/s: Jena 4.4.0
Assignee: Andy Seaborne
Resolution: Fixed
> Add
Taking a look at it today. In another project I bumped the version of Yarn
to v3 (we are using v1 I think, v2 is stable, v3 is the greatest and
latest). Will see if that solves the changes in the lock file, and also
look why the build is failing.
On Tue, 25 Jan 2022 at 06:38, Andy Seaborne
Bruno P. Kinoshita created JENA-2261:
Summary: UI: add unit tests
Key: JENA-2261
URL: https://issues.apache.org/jira/browse/JENA-2261
Project: Apache Jena
Issue Type: Improvement
Bruno P. Kinoshita created JENA-2260:
Summary: UI: build is modifying yarn.lock
Key: JENA-2260
URL: https://issues.apache.org/jira/browse/JENA-2260
Project: Apache Jena
Issue Type: Bug
On 24/01/2022 20:37, Bruno Kinoshita wrote:
The range of our UI dependencies is probably allowing for updates. When
running `yarn install` it is either finding new versions that match the
range (since the last time someone run yarn install and updated the lock
file), or a developer modified a
On 24/01/2022 19:33, Øyvind Gjesdal wrote:
I was building locally yesterday and got the same error message on the ui
module. However when I deleted node_modules before building it completed
successfully. Is there any cache on the apache CI build server or is there
something else at work?
[
https://issues.apache.org/jira/browse/JENA-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2258.
-
Fix Version/s: Jena 4.4.0
Assignee: Adam Soroka
Resolution: Fixed
>
24 matches
Mail list logo