I wanted to build app factory.
Am I correct that before it I should build:
first need to build orbit, then kernel and finally build the platform.
When it is done I should build AppFactory?
In svn I see https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.2AF/ -this is AppFactory 4.0.2
So I need first build orbit,kernel,platform with the same 4.0.2 version? (first build 4.0.0 and then patch it to 4.0.2)?
Thanks
i was found https://docs.wso2.com/display/AF210/Installing+On-Premise links with instruction.
There is writing to make checkout:
svn co https://svn.wso2.org/repos/wso2/scratch/appfactory_2.0.0/products/appfactory/2.1.0/modules/puppet-manifests /home/ubuntu/puppetsource/
Does it mean that I don't firstly build orbit, kernel and platform?
Related
I'm using given conan packages
gtest/1.8.0#bincrafters/stable
boost/1.66.0#conan/stable
log4cplus/2.0.2#bincrafters/stable`
and clang (version at least 6.0).
While first two packages has binaries for clang 6.0, log4cplus doesn't (last is clang 3.9). I don't like the idea that on each workstation I would need to build this package by hand.
How can I upload localy build binary with clang 6.0?
conan upload looks promising, however it suggest that it will be NEW package. Second question - wouldn't I interfere with package author in any way?
I do recommend open an issue for Bincrafters, requesting clang 3.9 support: https://github.com/bincrafters/community/issues/
Include a new package configuration is just one line in the Travis recipe.
How can I upload localy build binary with clang 6.0?
You could use JFrog Artifactory, there is a Community Edition with Conan support. Also, you could create a "mirror" for your packages locally with Artifactory, instead to download from Bintray:
https://docs.conan.io/en/latest/uploading_packages/artifactory_ce.html
However, Conan respects your remote list by it order, if your Conan client finds log4cplus first in Bincrafters' remote but the correct binary is only available in your local repository, Conan will ignore your local remote and will show a message error about missed binary package for log4cplus. Thus, in your case, you will need to copy ALL binaries to your local repository.
Regards!
You will find the conan packages installed on your Linux system at .conan/data/package_name/version/repo_name/tag. There will be a package folder inside it. If you want to manually add binaries to existing packages then you can add the binary in /bin folder in packages.
Or else you can look into the conan recipe in exports folder and look for the package, that from where it is getting its binaries from and add that binary in that path.
When I use "yarn build", i got an error message:
Error: Missing binding /www/htdocs/node_modules/node-sass/vendor/linux-x64-57/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 8.x
Found bindings for the following environments:
- Linux 64-bit with Node.js 10.x
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to download the binding for your current environment.
I tried to use npm rebuild node-sass but it didn't work. What should I do?
This problem seems to be related to globally installed packages.
I have been fighting getting a CMS package - Enduro - to work and finally I found a solution.
Normally Enduro is installed in /usr/local/lib however it can also be installed in the project. When I run Enduro from the /usr/local/lib I get the "sass version error" like you. However when I run the local project version ./node-modules/.bin/enduro there is no version problems.
I got no clue how to fix the global installation since the bindings will not fix when I run the rebuild sass command.
But running Enduro from the project works fine for me for now.
I hope you can use some of this even if you are dealing with another product using Sass.
Try to build Dartium 1.21.0 on Ubuntu 16.10, following the instructions https://github.com/dart-lang/sdk/wiki/Building-Dartium
Replacing gclient config --deps-file tools/deps/dartium.deps/DEPS --name=src/dart https://github.com/dart-lang/sdk.git
with gclient config --deps-file tools/deps/dartium.deps/DEPS --name=src/dart https://github.com/dart-lang/sdk.git#1.21.0
With some minor tweaks, things works, until hit by same as this https://github.com/js-platform/node-webrtc/issues/221
Fixed in a later version of boringssl
https://boringssl.googlesource.com/boringssl/+/241364c6f4d44165ce2dc707b9ad141dcc880d1b
Chromium builds more or less of the box.
To continue, two options occur. To step the boringssl version and update the build files, alternativly find at matching os distro and version. What distro and version is Dartium build on? Goobuntu is based on Ubuntu, maybe 16.04 should be used? Or are there some other tweaks that will fix this?
ps. yes, I know at the moment the future of Dartium is uncertain (will use a build to look into the dart bindings towards blinks web idl).
The latest release of MRUnit is 0.9. This release does not support DistributedCache.
This https://issues.apache.org/jira/browse/MRUNIT-98 shows that 1.0.0 supports DistributedCache. I want to get ahold of an MRUnit 1.0.0 jar that is built for hadoop1, but I cannot find one. So I tried to build it myself, but the required jars are missing from the maven repo.
Here is the command I'm using:
mvn package -DenvClassifier=hadoop1 -DspecificHadoopVersion=1.0.3
It fails with dependency errors. I can get ahold of the required jars manually, but I don't know how to get the build to use them.
How can I get ahold of the jar I want (either build it myself, or download it)?
I figured this out after I posted the question.
The answer is simple. Checkout the hadoop1 branch, and build that:
$ git checkout -b local/trunk-hadoop1 remotes/origin/trunk-hadoop1
$ mvn package
I'm trying to run yeoman build on a project that uses requireJS and the require-handlebars-plugin. I'm am getting this error when running the rjs task:
<WARN> Error: ENOENT, no such file or directory '/Users/tkrell/Sites/pathrabbit-marionette-require/temp/scripts/template/schedules/day-jobs -past.js'
In module tree:
main
schedules/schedule-layouts
schedules/schedule-jobs-view
hbs
at Object.fs.openSync (fs.js:338:18)
Use --force to continue. </WARN>
I believe this is the same as this issue which appears to simply need the latest version of r.js to be resolved. When I use a newer version of r.js manually, I don't get the error and everything works fine. How can I force the yeoman build task to use the latest version r.js?
The advice given on the issue I created on Yeoman's github page worked for me:
Yeoman uses 2.0.2 (see it's package.json).
You could go into the directory yeoman is installed and run npm install -f requirejs to force install a newer version. No promises it won't break though.
However, in yeoman 1.0 (which is imminent), we'll be using grunt-requirejs instead.