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.
Thanks - if I run the build twice, the yarn.lock file does not get
changed by run 2 from what it was on run 1 - hope that means it isn't a
hash table issue.
Andy
On Tue, 25 Jan 2022 at 06:38, Andy Seaborne <a...@apache.org> wrote:
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
"
https://registry.yarnpkg.com/@babel/core/-/core-7.16.7.tgz#db990f931f6d40cb9b87a0dc7d2adc749f1dcbcf";
- integrity
sha512-aeLaqcqThRNZYmbMqtulsetOQZ/5gbR/dWruUCJcpas4Qoyy+QeagfDsPdMrqwsPRDNxJvBlRiZxxX7THO7qtA==
dependencies:
"@babel/code-frame" "^7.16.7"
"@babel/generator" "^7.16.7"
Some are reordering in the file.
I'm not sure what's going to happen in a release build - it may check in
the changes because it does other commits, or it might get upset that
changes are happening while running.
Can the update of yarn.lock be turned off?
The build is failing
https://ci-builds.apache.org/job/Jena/job/Jena_Development_Test/309/console
[INFO] --- frontend-maven-plugin:1.10.4:yarn (yarn run build) @
jena-fuseki-ui ---
[INFO] Running 'yarn run build' in
/home/jenkins/jenkins-agent/workspace/Jena/Jena_Development_Test/jena-fuseki2/jena-fuseki-ui
[INFO] yarn run v0.16.1
[INFO] $ vue-cli-service build
[INFO]
[INFO] - Building for production...
[INFO] ERROR Failed to compile with 1 error5:18:32 PM
[INFO]
[INFO] Syntax Error: TypeError: Cannot read properties of undefined
(reading 'parseComponent')
[INFO]
guessing but could it be a version of problem with some tooling?
Andy
