Wso2 5.3 : Source code for authenticationendpoint war and other wars - wso2-identity-server

I am on wso2 5.3 version, and need to customize the following wars for project need.
oauth2.war
accountrecoveryendpoint.war
emailotpauthenticationendpoint.war
authenticationendpoint
Could you please share the github repo url for these wars which are deployed under :
{wso2Home}\repository\deployment\server\webapps folder
Could you please share the steps needed to build/compile the authenticationendpoint.war after making changes ?

You can find the sources at the following repositories/locations
Oauth
accountrecoveryendpoint
emailotpauthenticationendpoint
authenticationendpoint
They all can be build with the usual maven commands (mvn clean install). Just make sure you delete any extracted webapp folders of those when replacing with your custom built ones. Otherwise the new webapps won't be deployed.

Related

The correct order to rebuild the WSO2 repositories on my local computer

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.

How to deploy files for Sitecore using TDS

I'm starting a new Sitecore 9 project using Helix and TDS. I've got my basic structure setup, using Hedgehog's fork of the Habitat site as a guide. I'm also referencing Hedgehog's docs.
My solution is just a start, so it's very simple right now, only a Foundation.Serialization module that contains the TDS projects for the basic layer folders and a Project.Website module that contains a TDS project and an MVC Website project (MVC)....it's got a basic Razor view and some random CSS/JS files.
The TDS Habitat readme, says to use Solution > Deploy Solution to deploy the projects. When I do this on my project it builds and the Sitecore items are deployed to Sitecore, but my Views and CSS/JS are not....presumably because I haven't configured anything to facilitate this.
Looking at the docs and the TDS Habitat solution, it's not clear to me how to configure TDS to know anything about how to deploy files. I'm finding info on the web that says that TDS will deploy files, transform configs, etc but with no examples of how to actually make that happen.
How do I set things up so Deploy Solution will also deploy files from all of the web projects in a solution to my local web root?
First, you will need to make sure the Sitecore Deploy Folder is set. From the documentation:
Sitecore Deploy Folder – Contains the path to the ROOT of the Sitecore
instance on the file system. This setting is used to install the TDS
Classic service when needed and to deploy the compiled code when the
TDS Classic project is built.
You also need to make sure that file deployment has not been disabled:
Disable File Deployment – Stops TDS Classic deploying files to the
directory specified in the Sitecore Deploy Folder.
If you are still not seeing the files being deployed, you will need to check if the process has access to the deploy folder.
You can also deploy files as a .update package and then use another automated tool to deploy the .update package to the target environment.
I figured out the issue. On the properties page for a TDS project there is a field where you indicate which projects should be built and deployed along with the sitecore items:
https://www.hhogdev.com/help/tds/propgeneral

Nexus 3.5.1 proxies from snapshot repo nothing but maven metadata files

I have upgraded nexus repository from 2.x to 3.x through following path:
2.4.14 -> 3.4.0 -> 3.5.1
All nexus services were packed in docker with data directory mapped from host's. For all services I use default either sonatype/nexus or sonatype/nexus3 containers. Nexus web interface is hidden behind nginx with simple reverse proxying.
I use the nexus service with boot-cj (with no credentials) tools which manages dependencies the same way as maven. Anyway the tool first downloads nexus-maven.xml with relevant sha1 files and tries to download jars. It works fine with all 2.x I had.
I created a proxy repository against remote sonatype-snapshots repo. When I start compilation I have Could not find artifact error. I found that the meatdata files are cached but all poms and jars.
I have tried to fix it by cleaning cache with the clean_cache file trick and more rough rm -rfv /srv/nexus3/nexus-data/cache/* with no success. There are no any logs about error. Also I have checked manually that required artefact exists in the remote repository. More obvious Rebuild index button gave no solution. I do not thing it is a problem with nginx, but who knows? Also leaving overnight to run the scheduled tasks did not help.
The expected artifact is org.eclipse.rdf4j:rdf4j:pom:2.3-20170901.145510-11.

Configure a remote project

I am starting a Django project. I'd like to connect this project in such a way my partner could work remotly and we can see the trackings and modifications on that project. What do you suggest to set up those configurations?
The program is called git, its not necessary use GitHub, Bitbucket to deploy your Django project in a server, also you can have a version control of your project and work with your patner without problems. Read this to deploy your Django project https://www.digitalocean.com/community/tutorials/how-to-use-git-hooks-to-automate-development-and-deployment-tasks#using-git-hooks-to-deploy-to-a-separate-production-server and this is git https://git-scm.com/

wso2 carbon: how to hack the source and deploy the changes to a carbon server

I have the carbon source tree set up in eclipse - and have made some code changes.
Can I build just one component (e.g. org.wso2.carbon.feature.mgt.ui-4.1.0.jar) using maven / eclipse, and then deploy that to an existing carbon server?
I have tried dropping the built jar in the repository\deployment directory and restarting the server, but the changes don't appear to have been picked up.
Am I doing something wrong?
Place the jars at <CARBON_HOME>/repository/components/plugins. Also delete the relevant existing jars from repository/components/plugins