You are depending on the user manager in the commons project, at least,
which means the branch should contain that code. You can remove
unncessary code from the branch. Also, the convention we agreed upon was
to branch the entire trunk, that is why we have
https://wso2.org/repos/wso2/trunk/registry/ &
https://wso2.org/repos/wso2/branches/registry/, not
https://wso2.org/repos/wso2/registry/trunk &
https://wso2.org/repos/wso2/registry/branches
Also, with the current branching setup, once you ship the registry with
a particular revision of user manager, on a later date, how can I
retrieve the code for that particular user manager SNAPSHOT?
Azeez
Deepal Jayasinghe wrote:
Hi Devs,
The convention we follow when branching is to create a branch of the
entire trunk. We also include the external 3rd party source
dependencies (if there are SNAPSHOT deps). Then the unnecessary parts
are removed from this branch. If this was done, the commons project
dependencies such as user manager will also come into the registry 1.0
branch, and all the relevant sources will be in a single place.
In our case we do not depend on that much of snapshot dependencies so I
do not think we need to create a branch with all those source code.
-Deepal
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
