Is there any documentation available that describes the WSO2 svn structure?
It seems that the folder https://svn.wso2.org/repos/wso2/branches/ is deprecated.
Question 1: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
In the https://svn.wso2.org/repos/wso2/carbon/ folder, I'm managing to piece bits together, for example the difference between Carbon orbit, kernel and platform (see previous stackoverflow question).
In the https://svn.wso2.org/repos/wso2/carbon/platform/branches/ folder, there are 3 sub-folders:
4.0.0
4.0.2AF
4.1.0
Question 2: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
Question 3: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
Question: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
WSO2 is currently doing active development in following svn directory.
https://svn.wso2.org/repos/wso2/carbon/
Question: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
The branches in https://svn.wso2.org/repos/wso2/carbon/platform/branches/ are for the Carbon platform. The branch 4.0.2AF is for WSO2 App Factory (http://wso2.com/cloud/app-factory/)
Question: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
You can build Carbon 4.0.3 from following:
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/
You will be able to build products using the branch. That's why branch SVN URL is given in the links.
Each branch has a patch release for minor platform releases. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/
As mentioned in your answer, you can build from a tagged version also.
You can more details about product version and carbon version from the release matrix: http://wso2.com/products/carbon/release-matrix/
You can also subscribe to WSO2 mailing lists and get more information, if you have not subscribed already.
The answer to question 3 is build a checkout a tagged version (of course!!). Thanks to the answer here for pointing me in the right direction.
I was blindly following the wiki documentation which tells you to checkout a branch.
Related
I want to rebuild the WSO2 EI from source code on Git repository. But I do not know how to start this job. I have already sent an email to dev#wso2.org to get advice for along time. But I have not received any information from them yet.
I also downloaded and rebuilt the carbon-commons repository tag that was used for the WSO2 AS 5.3.0 release successfully. But I do not know what is the tag of WSO2 EI from the carbon repository?
(following this reference link: https://docs.wso2.com/display/Carbon4411/Working+with+the+Source+Code)
Could you give me some advice to do this job quickly ?
You can build the EI pack by cloning product-ei repository from the Github and checkout to the relevant tag. All WSO2 related dependencies are hosted in WSO2 nexus repository. Therefore you don't need to build dependent repositories. You can build EI project without running test cases by simply running "mvn clean install -Dmaven.test.skip=true".
If you need to do a code change for dependent repository, then you can do the necessary changes in relevant dependent repository and build the repositories in following order.
For example, If you need to do a code change to the Synapse, first you need to build the Synapse. Then build Carbon-mediation project with updated Synapse version. Finally build EI with latest synapse and carbon-mediation version.
I am trying to upgrade my Ionic environment to the latest version.
I have an existing app I built on Ionic 2.0.0-beta.32. I want to upgrade it to the latest version 2.0.1 (or the final release).
My questions are :
1) How can I upgrade my environment ?
2) Is there any changes I have to do in my code ? (if yes please can you tell me exactly how to proceed it... ?)
answering question 1:
try these in the root of your project
sudo npm install -g ionic
ionic lib update
question number 2 is hard to answer. generally you should be good. You should try running your code and do some regression testing and then ask specific questions if you face any problems.
Ionic provides upgrade instructions in their changelog. Usually it is enough to upgrade your package version, but sometimes when there are breaking changes that you need to manually address they will be listed on that page.
I've visited the wso2 website and the install instructions are very disjointed in that there is a lot of jumping around between pages. I've seen the following blog that seemed to streamline the instructions but it doesn't seem complete (plus it's out of date with the version it's installing) - https://maxmalm.se/blog/2014-06-17-installing-wso2-enterprise-mobility-manager-110
Has anyone seen step-by-step instructions on what needs to be done to completely setup wso2-EMM on a newly installed Ubuntu 14.04 virtual machine with just the O/S on it and none of the pre-reqs installed yet? The blog I mentioned above seems to give a lot of the necessary apt-get install bits but doesn't mention anything about a database (yet the wso2 has a whole section on installing and using a database).
Thank you.
To try out WSO2 EMM you will only need to have JDK 7 or 8 [1] installed as minimum to start off the server. WSO2 products are build to run with OOB database which is H2. So to get things started and play around, I suggest that you install java and then start the pack to get things going.
[1] https://docs.wso2.com/display/EMM201/Installing+on+Linux+or+OS+X
To getting started all you need is JDK installed in your machine and setting the Java related environment variables like PATH, JAVA_HOME. You might have to install the correct version of JDK for the particular version of the EMM.
I try to build wso2 bps 3.5 from source code by following document (https://docs.wso2.com/display/BPS350/Working+with+the+Source+Code), but there is no org.wso2.carbon.humantask_4.4.4.jar inside the downloading component. Also I cannot find the source code in svn (https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/business-processes/humantask/org.wso2.carbon.humantask/).
Can somebody help to figure out where is this code repository.
If you look at the release matrix, this is released with carbon 4.4.x where sources are in Git repos. So the sources should be available in this Git repo (checkout the correct branch version). Note that you don't have to build the entire product from sources, just do the changes to the relevant component and build the jar. Then apply it as a patch to the product.
The release matrix for the wso2 platform is here: http://wso2.com/products/carbon/release-matrix/
If I want to build Identity Server 4.0.0 it seems that I need carbon 4.0.3.
Question 1. Will Identity Server only build on carbon 4.0.3, or will it build on 4.0.3+?
I have checked out the source from:
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
However, when I look in the orbit patch-releases folder, I only see:
4.0.1
4.0.2
4.0.5
4.0.6
Question 2. Which version of orbit patch release will I need to build for IS 4.0.0?
Question 01
To build IS 4.0.0 you need to build patch-release 4.0.3
But there can be some components from 4.0.0 up-to 4.0.3 but not 4.0.3+ So its better to build all main branch plus patch-release versions below your required version. As Ratha mentioned if you build online these jars will be downloaded if available.
Question 02
You need to build orbit patch-release 4.0.2 since it was used on IS 4.0.0
The reason for not having patch-release 4.0.3 version is there is no difference from 4.0.2 version. So same version is used during production.
Hope this will help you.
if you don't find particular version, that means product is released with older version of jars..
In your case, you might need to build 4.0.2..
Anyway if you do online build, if jars are available in the repo, they will be downloaded..You don't need to build older versions..
If not, you have to..