Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p><strong>Question</strong>: Should I only be working in the svn folder <a href="https://svn.wso2.org/repos/wso2/carbon/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/</a>?</p> </blockquote> <p>WSO2 is currently doing active development in following svn directory. </p> <p><a href="https://svn.wso2.org/repos/wso2/carbon/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/</a></p> <blockquote> <p><strong>Question</strong>: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?</p> </blockquote> <p>The branches in <a href="https://svn.wso2.org/repos/wso2/carbon/platform/branches/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/platform/branches/</a> are for the Carbon platform. The branch 4.0.2AF is for WSO2 App Factory (<a href="http://wso2.com/cloud/app-factory/" rel="nofollow">http://wso2.com/cloud/app-factory/</a>)</p> <blockquote> <p><strong>Question</strong>: 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?</p> </blockquote> <p>You can build Carbon 4.0.3 from following:</p> <p><a href="https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/</a></p> <p>You will be able to build products using the branch. That's why branch SVN URL is given in the links.</p> <p>Each branch has a patch release for minor platform releases. For example: <a href="https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/" rel="nofollow">https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/</a></p> <p>As mentioned in your answer, you can build from a tagged version also.</p> <p>You can more details about product version and carbon version from the release matrix: <a href="http://wso2.com/products/carbon/release-matrix/" rel="nofollow">http://wso2.com/products/carbon/release-matrix/</a></p> <p>You can also subscribe to WSO2 mailing <a href="http://wso2.com/mail" rel="nofollow">lists</a> and get more information, if you have not subscribed already.</p>
    singulars
    1. This table or related slice is empty.
    1. POwso2 svn structure documentation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USIsuru Perera
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POwso2 svn structure documentation
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COTo build a patch release, do I simply need to change into the patch release directory (e.g. `./platform/branches/4.0.0/patch-releases/4.0.3/`) and perform `mvn clean install`?
      singulars
      1. PO
      1. USChris Snow
    2. COYes. You can open the pom.xml and see. All components, features, service stubs and products for relevant patch release will be built.
      singulars
      1. PO
      1. USIsuru Perera
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload