WSO2 Endpoint look-up sample - wso2

I am trying to set up the WSO2 Endpoint look-up sample. I have made the changes according to the documentation, but when I try to build the app using "mvn clean install" I am receiving the following error:
Downloading: http://maven.wso2.org/nexus/content/groups/wso2-public/eclipse/vali
dateutility/0.95/validateutility-0.95.pom
[WARNING] Checksum validation failed, expected 53f8bac71524372a3d51a6ecf11365042
96f37af but is 8edc83998e0bf2a8867395883f3853eb901be267 for http://maven.wso2.or
g/nexus/content/groups/wso2-public/eclipse/validateutility/0.95/validateutility-
0.95.pom
Downloading: http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/
osgi/org.eclipse.osgi.services/3.2.0.v20090520-1800/org.eclipse.osgi.services-3.
2.0.v20090520-1800.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is 8edc83998e0bf2a8
867395883f3853eb901be267 for http://maven.wso2.org/nexus/content/groups/wso2-pub
lic/org/eclipse/osgi/org.eclipse.osgi.services/3.2.0.v20090520-1800/org.eclipse.
osgi.services-3.2.0.v20090520-1800.pom
The checksums are failing. Does someone need to update the files in the repository?

I managed to get the handler sample to build by:
1) Checkout the Greg 4.5.3 Source Code:
svn co https://svn.wso2.org/repos/wso2/carbon/platform/tags/4.0.5/products/greg/4.5.3/ wso2_greg_453
2) Build the source:
cd wso2_greg_453
mvn clean install -Dmaven.test.skip=true
I had a build failure due to maven issues cleaning up surefire reports, which I ignored.
3) Build the handler sample in the directory I unzipped the binary version of GREG to:
cd %CARBON_HOME%
wso2greg-4.5.3\samples\handler\src
mvn clean install
This time the handler sample built ok.
The approach above is a bit long winded, but it works!

Related

How to fix build error because Install pods using EAS build EXPO?

I'm trying to build an IOS app using EAS service expo, but when I try to build, there is an error while install pods on build details expo. And this is the error.
Unable to find a specification for `UMTaskManagerInterface` depended upon by `EXLocation`
I try to install pod by npm i pod-install but still get error. Is this because I build on Windows, or what should I do to fix this error? I also try to find the error in GitHub forum, and it's say adding path pod in ios/Podfile which I can't find it in my expo project. Where is ios/Podfile file located in expo project?
This is the full error
Installing pods
Using Expo modules
Auto-linking React Native modules for target `MMS`: RNCAsyncStorage, RNCCheckbox, RNDateTimePicker, RNGestureHandler, RNPermissions, RNReanimated, RNScreens, react-native-safe-area-context, and react-native-viewpager
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `RCT-Folly` from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Adding spec repo `trunk` with CDN `https://cdn.cocoapods.org/`
CocoaPods 1.11.2 is available.
To update use: `sudo gem install cocoapods`
For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.11.2
[!] Unable to find a specification for `UMTaskManagerInterface` depended upon by `EXLocation`
You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* mistyped the name or version.
* not added the source repo that hosts the Podspec to your Podfile.
[stderr] [!] `<PBXResourcesBuildPhase UUID=`13B07F8E1A680F5B00A75B9A`>` attempted to initialize an object with an unknown UUID. `2EE81B3C866A4A13B6460929` for attribute: `files`. This can be the result of a merge and the unknown UUID is being discarded.
pod exited with non-zero code: 1
Edit*
i try using expo build:ios-> archive is working perfectly. why using eas build -p ios i got that error?

Why am I getting this error in AWS Device farm? Tests skipped due to test package parsing error. Please check Parsing result for more details

In AWS Device Farm, I created a new run. I chose native application. I uploaded my APK. I chose Calabash as the tests. I got this error message:
Tests skipped due to test package parsing error. Please check Parsing result for more details.
I downloaded the Parsing result. Here's what it said:
Failed to run cucumber dry-run command. See the information below for more details.
Here are the contents for the Parsing result:
'cucumber --dry-run --format json --out /tmp/scratchvxnAeX.scratch/tmpF6f5Xx' failed.
Could not find proper version of cucumber (2.99.0) in any of the sources
Run `bundle install` to install missing gems.
Solution
I have some .rb page objects. I added require 'calabash-android' to the top of those files. Then I made a new run and ran it. It worked.
How I got to the solution
Through Google I came across CALABASH_TEST_PACKAGE_DRY_RUN_FAILED here.
Running this command failed: cucumber-ios --dry-run --format json features
I figured that was for ios. So I tried this: bundle exec calabash-android run .\app-releaseStaging.apk --dry-run. I got this error:
uninitialized constant Calabash::ABase (NameError)
I wasn't getting that error when running locally.
According to this:
-d, --dry-run Invokes formatters without executing the steps. This also omits the loading of your support/env.rb file if it exists.
I had require 'calabash-android' inside env.rb. So I moved it to my page objects. Then it worked.
You may find the aws-device-farm-calabash-tests-for-sample-app useful.

Upgrading orchard from 1.8.2 to 1.10.2. but the build in vsts is failing in the 'Drop' step

Upgrading orchard from 1.8.2 to 1.10.2. but the build in vsts is failing in the 'Drop' step with the following error : "Publish build artifacts failed with error: Not found PathtoPublish: d:\a\1\s\ReleaseManagement\Zipped" .
Does this mean that any of the settings or config files are overwritten?
Guess some config information regarding the generation of ReleaseManagement.zip is missing.
During the upgrade the package.proj file and the MSbuild folder got deleted .Because of this the required releasemanagement zip file and other files didnt get generated. After including the deleted files back the build passed successfully.

Cannot setup Ionic monitoring with ionic cordova build --prod

I tried the following command to try add the monitoring feature of ionic to diagnose a problem in my app using ionic view.
$ ionic monitoring syncmaps
git rev-parse HEAD
√ Running command - done!
[INFO] No sourcemaps found, doing build...
? Do full prod build? (Y/n) y ?
Do full prod build? Yes
[INFO] Running app-scripts build: --prod
[22:16:31] build prod started ...
[22:16:31] clean started ...
[22:16:31] clean finished in 1 ms
[22:16:31] copy started ...
[22:16:31] ngc started ...
[22:16:37] ngc finished in 6.08 s
[22:16:37] preprocess started ...
[22:16:37] deeplinks started ...
[22:16:38] deeplinks finished in 441 ms
[22:16:38] optimization started ...
[22:16:38] copy finished in 6.63 s
Error: ./src/pages/admin/admin.ngfactory.js
Module not found: Error: Can't resolve '../../../angularfire2/auth' in >'C:\Users\Gavin\Desktop\Web Development\app\src\pages\admin'
resolve '../../../angularfire2/auth' in 'C:\Users\Gavin\Desktop\Web Development\app\src\pages\admin' using description file: C:\Users\Gavin\Desktop\Web Development\app\package.json (relative path: ./src/pages/admin)
Field 'browser' doesn't contain a valid alias configuration
This error keeps going down the page for a long time, I get the same error if I type
ionic cordova build --prod
I resolved it by deleting .ngmodules folder, downgrading my firebase version to npm i --save angularfire2#4.0.0-rc.1 , and then npm install. I was then able to build my app with ionic cordova --prod

wso2 governance registry build fail

i'm trying to build wso2 governance registry by src files with maven 3, but after many retries i'm stuck too.
I had dowload all required libraries, and fixed all duplicate child in pom files, but whem i'm trying to build i obtain this error.
"[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.
2-beta-5:attached (dist) on project axis2-kernel: Failed to create assembly: Err
or creating assembly archive docs: You must set at least one file. -> [Help 1]
[ERROR]"
and previously
"[FATAL] Non-readable POM C:\greg\wso2greg-4.1.1-src\dependencies\axis2\1.6.1-wso2v1\modules\pom.xml: C:\greg\wso2greg-4.1.1-src\dependencies\axis2\1.6.1-wso2v1\modules\pom.xml (Impossibile trovare il file specificato) #
for project at C:\greg\wso2greg-4.1.1-src\dependencies\axis2\1.6.1-wso2v1\modules\pom.xml for project at C:\greg\wso2greg-4.1.1-src\dependencies\axis2\1.6.1-wso2v1\modules\pom.xml"
I'm trying to build with maven 2 but, even if console output message shows "BUILD SUCCEFFULL" i can found bin folder and relative wso2server.bat file.
Anyone can help me?
Please clone below repos and run an mvn clean install -e on each and everyone accordingly.
https://github.com/wso2/carbon4-kernel.git
https://github.com/wso2/carbon-registry.git
https://github.com/wso2/carbon-governance.git
https://github.com/wso2/carbon-governance-extensions.git
https://github.com/wso2/carbon-store
Then build G-Reg from the source!
Note: Current G-Reg developer snapshot :https://github.com/wso2/product-greg.git