update links in readmes
This commit is contained in:
		
							parent
							
								
									42c4a6f647
								
							
						
					
					
						commit
						f1e0397dc0
					
				| @ -1,3 +1,2 @@ | ||||
| ## Relevant articles: | ||||
| 
 | ||||
| - [Writing a Jenkins Plugin](http://www.baeldung.com/jenkins-custom-plugin) | ||||
| This is an aggregator modules for Jenkins-related modules. | ||||
|  | ||||
							
								
								
									
										3
									
								
								jenkins/hello-world/README.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										3
									
								
								jenkins/hello-world/README.md
									
									
									
									
									
										Normal file
									
								
							| @ -0,0 +1,3 @@ | ||||
| ## Relevant articles: | ||||
| 
 | ||||
| - [Writing a Jenkins Plugin](http://www.baeldung.com/jenkins-custom-plugin) | ||||
| @ -1,3 +1,2 @@ | ||||
| ## Relevant articles: | ||||
| 
 | ||||
| - [Creating New APIs and Views in JHipster](https://www.baeldung.com/jhipster-new-apis-and-views) | ||||
| This is an aggregator module for JHipster 5 modules. | ||||
|  | ||||
| @ -1,179 +1,3 @@ | ||||
| # Bookstore | ||||
| ## Relevant articles: | ||||
| 
 | ||||
| This application was generated using JHipster 5.8.2, you can find documentation and help at [https://www.jhipster.tech/documentation-archive/v5.8.2](https://www.jhipster.tech/documentation-archive/v5.8.2). | ||||
| 
 | ||||
| ## Development | ||||
| 
 | ||||
| Before you can build this project, you must install and configure the following dependencies on your machine: | ||||
| 
 | ||||
| 1.  [Node.js][]: We use Node to run a development web server and build the project. | ||||
|     Depending on your system, you can install Node either from source or as a pre-packaged bundle. | ||||
| 
 | ||||
| After installing Node, you should be able to run the following command to install development tools. | ||||
| You will only need to run this command when dependencies change in [package.json](package.json). | ||||
| 
 | ||||
|     npm install | ||||
| 
 | ||||
| We use npm scripts and [Webpack][] as our build system. | ||||
| 
 | ||||
| Run the following commands in two separate terminals to create a blissful development experience where your browser | ||||
| auto-refreshes when files change on your hard drive. | ||||
| 
 | ||||
|     ./mvnw | ||||
|     npm start | ||||
| 
 | ||||
| Npm is also used to manage CSS and JavaScript dependencies used in this application. You can upgrade dependencies by | ||||
| specifying a newer version in [package.json](package.json). You can also run `npm update` and `npm install` to manage dependencies. | ||||
| Add the `help` flag on any command to see how you can use it. For example, `npm help update`. | ||||
| 
 | ||||
| The `npm run` command will list all of the scripts available to run for this project. | ||||
| 
 | ||||
| ### Service workers | ||||
| 
 | ||||
| Service workers are commented by default, to enable them please uncomment the following code. | ||||
| 
 | ||||
| -   The service worker registering script in index.html | ||||
| 
 | ||||
| ```html | ||||
| <script> | ||||
|     if ('serviceWorker' in navigator) { | ||||
|         navigator.serviceWorker.register('./service-worker.js').then(function() { | ||||
|             console.log('Service Worker Registered'); | ||||
|         }); | ||||
|     } | ||||
| </script> | ||||
| ``` | ||||
| 
 | ||||
| Note: workbox creates the respective service worker and dynamically generate the `service-worker.js` | ||||
| 
 | ||||
| ### Managing dependencies | ||||
| 
 | ||||
| For example, to add [Leaflet][] library as a runtime dependency of your application, you would run following command: | ||||
| 
 | ||||
|     npm install --save --save-exact leaflet | ||||
| 
 | ||||
| To benefit from TypeScript type definitions from [DefinitelyTyped][] repository in development, you would run following command: | ||||
| 
 | ||||
|     npm install --save-dev --save-exact @types/leaflet | ||||
| 
 | ||||
| Then you would import the JS and CSS files specified in library's installation instructions so that [Webpack][] knows about them: | ||||
| Edit [src/main/webapp/app/vendor.ts](src/main/webapp/app/vendor.ts) file: | ||||
| 
 | ||||
| ``` | ||||
| import 'leaflet/dist/leaflet.js'; | ||||
| ``` | ||||
| 
 | ||||
| Edit [src/main/webapp/content/css/vendor.css](src/main/webapp/content/css/vendor.css) file: | ||||
| 
 | ||||
| ``` | ||||
| @import '~leaflet/dist/leaflet.css'; | ||||
| ``` | ||||
| 
 | ||||
| Note: there are still few other things remaining to do for Leaflet that we won't detail here. | ||||
| 
 | ||||
| For further instructions on how to develop with JHipster, have a look at [Using JHipster in development][]. | ||||
| 
 | ||||
| ### Using angular-cli | ||||
| 
 | ||||
| You can also use [Angular CLI][] to generate some custom client code. | ||||
| 
 | ||||
| For example, the following command: | ||||
| 
 | ||||
|     ng generate component my-component | ||||
| 
 | ||||
| will generate few files: | ||||
| 
 | ||||
|     create src/main/webapp/app/my-component/my-component.component.html | ||||
|     create src/main/webapp/app/my-component/my-component.component.ts | ||||
|     update src/main/webapp/app/app.module.ts | ||||
| 
 | ||||
| ## Building for production | ||||
| 
 | ||||
| To optimize the Bookstore application for production, run: | ||||
| 
 | ||||
|     ./mvnw -Pprod clean package | ||||
| 
 | ||||
| This will concatenate and minify the client CSS and JavaScript files. It will also modify `index.html` so it references these new files. | ||||
| To ensure everything worked, run: | ||||
| 
 | ||||
|     java -jar target/*.war | ||||
| 
 | ||||
| Then navigate to [http://localhost:8080](http://localhost:8080) in your browser. | ||||
| 
 | ||||
| Refer to [Using JHipster in production][] for more details. | ||||
| 
 | ||||
| ## Testing | ||||
| 
 | ||||
| To launch your application's tests, run: | ||||
| 
 | ||||
|     ./mvnw clean test | ||||
| 
 | ||||
| ### Client tests | ||||
| 
 | ||||
| Unit tests are run by [Jest][] and written with [Jasmine][]. They're located in [src/test/javascript/](src/test/javascript/) and can be run with: | ||||
| 
 | ||||
|     npm test | ||||
| 
 | ||||
| For more information, refer to the [Running tests page][]. | ||||
| 
 | ||||
| ### Code quality | ||||
| 
 | ||||
| Sonar is used to analyse code quality. You can start a local Sonar server (accessible on http://localhost:9001) with: | ||||
| 
 | ||||
| ``` | ||||
| docker-compose -f src/main/docker/sonar.yml up -d | ||||
| ``` | ||||
| 
 | ||||
| Then, run a Sonar analysis: | ||||
| 
 | ||||
| ``` | ||||
| ./mvnw -Pprod clean test sonar:sonar | ||||
| ``` | ||||
| 
 | ||||
| For more information, refer to the [Code quality page][]. | ||||
| 
 | ||||
| ## Using Docker to simplify development (optional) | ||||
| 
 | ||||
| You can use Docker to improve your JHipster development experience. A number of docker-compose configuration are available in the [src/main/docker](src/main/docker) folder to launch required third party services. | ||||
| 
 | ||||
| For example, to start a mysql database in a docker container, run: | ||||
| 
 | ||||
|     docker-compose -f src/main/docker/mysql.yml up -d | ||||
| 
 | ||||
| To stop it and remove the container, run: | ||||
| 
 | ||||
|     docker-compose -f src/main/docker/mysql.yml down | ||||
| 
 | ||||
| You can also fully dockerize your application and all the services that it depends on. | ||||
| To achieve this, first build a docker image of your app by running: | ||||
| 
 | ||||
|     ./mvnw package -Pprod verify jib:dockerBuild | ||||
| 
 | ||||
| Then run: | ||||
| 
 | ||||
|     docker-compose -f src/main/docker/app.yml up -d | ||||
| 
 | ||||
| For more information refer to [Using Docker and Docker-Compose][], this page also contains information on the docker-compose sub-generator (`jhipster docker-compose`), which is able to generate docker configurations for one or several JHipster applications. | ||||
| 
 | ||||
| ## Continuous Integration (optional) | ||||
| 
 | ||||
| To configure CI for your project, run the ci-cd sub-generator (`jhipster ci-cd`), this will let you generate configuration files for a number of Continuous Integration systems. Consult the [Setting up Continuous Integration][] page for more information. | ||||
| 
 | ||||
| [jhipster homepage and latest documentation]: https://www.jhipster.tech | ||||
| [jhipster 5.8.2 archive]: https://www.jhipster.tech/documentation-archive/v5.8.2 | ||||
| [using jhipster in development]: https://www.jhipster.tech/documentation-archive/v5.8.2/development/ | ||||
| [using docker and docker-compose]: https://www.jhipster.tech/documentation-archive/v5.8.2/docker-compose | ||||
| [using jhipster in production]: https://www.jhipster.tech/documentation-archive/v5.8.2/production/ | ||||
| [running tests page]: https://www.jhipster.tech/documentation-archive/v5.8.2/running-tests/ | ||||
| [code quality page]: https://www.jhipster.tech/documentation-archive/v5.8.2/code-quality/ | ||||
| [setting up continuous integration]: https://www.jhipster.tech/documentation-archive/v5.8.2/setting-up-ci/ | ||||
| [node.js]: https://nodejs.org/ | ||||
| [yarn]: https://yarnpkg.org/ | ||||
| [webpack]: https://webpack.github.io/ | ||||
| [angular cli]: https://cli.angular.io/ | ||||
| [browsersync]: http://www.browsersync.io/ | ||||
| [jest]: https://facebook.github.io/jest/ | ||||
| [jasmine]: http://jasmine.github.io/2.0/introduction.html | ||||
| [protractor]: https://angular.github.io/protractor/ | ||||
| [leaflet]: http://leafletjs.com/ | ||||
| [definitelytyped]: http://definitelytyped.org/ | ||||
| - [Creating New APIs and Views in JHipster](https://www.baeldung.com/jhipster-new-apis-and-views) | ||||
|  | ||||
| @ -1,4 +1,2 @@ | ||||
| ### Relevant Articles: | ||||
| - [Batch Processing with Spring Cloud Data Flow](http://www.baeldung.com/spring-cloud-data-flow-batch-processing) | ||||
| - [Getting Started with Stream Processing with Spring Cloud Data Flow](http://www.baeldung.com/spring-cloud-data-flow-stream-processing) | ||||
| - [Spring Cloud Data Flow With Apache Spark](https://www.baeldung.com/spring-cloud-data-flow-spark) | ||||
| 
 | ||||
| This is an aggregator module for Spring Cloud Data Flow modules. | ||||
|  | ||||
							
								
								
									
										3
									
								
								spring-cloud-data-flow/apache-spark-job/README.MD
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										3
									
								
								spring-cloud-data-flow/apache-spark-job/README.MD
									
									
									
									
									
										Normal file
									
								
							| @ -0,0 +1,3 @@ | ||||
| ### Relevant Articles: | ||||
| 
 | ||||
| - [Spring Cloud Data Flow With Apache Spark](https://www.baeldung.com/spring-cloud-data-flow-spark) | ||||
							
								
								
									
										3
									
								
								spring-cloud-data-flow/batch-job/README.MD
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										3
									
								
								spring-cloud-data-flow/batch-job/README.MD
									
									
									
									
									
										Normal file
									
								
							| @ -0,0 +1,3 @@ | ||||
| ### Relevant Articles: | ||||
| - [Batch Processing with Spring Cloud Data Flow](http://www.baeldung.com/spring-cloud-data-flow-batch-processing) | ||||
| 
 | ||||
| @ -13,13 +13,9 @@ | ||||
|     </parent> | ||||
| 
 | ||||
|     <modules> | ||||
|         <module>data-flow-server</module> | ||||
|         <!-- <module>data-flow-shell</module> --> | ||||
|         <module>time-source</module> | ||||
|         <module>time-processor</module> | ||||
|         <module>log-sink</module> | ||||
|         <module>spring-cloud-data-flow-stream</module> | ||||
|         <module>spring-cloud-data-flow-etl</module> | ||||
|         <module>batch-job</module> | ||||
|         <module>etl</module> | ||||
|         <module>apache-spark-job</module> | ||||
|     </modules> | ||||
| 
 | ||||
|  | ||||
| @ -1,7 +1,7 @@ | ||||
| <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||||
|     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | ||||
|     <modelVersion>4.0.0</modelVersion> | ||||
|     <artifactId>etl</artifactId> | ||||
|     <artifactId>spring-cloud-data-flow-etl</artifactId> | ||||
|     <version>0.0.1-SNAPSHOT</version> | ||||
|     <name>etl</name> | ||||
|     <packaging>pom</packaging> | ||||
| @ -0,0 +1,4 @@ | ||||
| ### Relevant Articles: | ||||
| 
 | ||||
| - [Getting Started with Stream Processing with Spring Cloud Data Flow](http://www.baeldung.com/spring-cloud-data-flow-stream-processing) | ||||
| 
 | ||||
| @ -0,0 +1,23 @@ | ||||
| <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||||
|     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | ||||
|     <modelVersion>4.0.0</modelVersion> | ||||
|     <artifactId>spring-cloud-data-flow-stream</artifactId> | ||||
|     <version>0.0.1-SNAPSHOT</version> | ||||
|     <name>spring-cloud-data-flow-stream</name> | ||||
|     <packaging>pom</packaging> | ||||
| 	 | ||||
|     <parent> | ||||
|         <groupId>com.baeldung</groupId> | ||||
|         <artifactId>parent-modules</artifactId> | ||||
|         <version>1.0.0-SNAPSHOT</version> | ||||
|     </parent> | ||||
| 
 | ||||
|     <modules> | ||||
|         <module>data-flow-server</module> | ||||
|         <module>data-flow-shell</module> | ||||
|         <module>time-source</module> | ||||
|         <module>time-processor</module> | ||||
|         <module>log-sink</module> | ||||
|     </modules> | ||||
| 
 | ||||
| </project> | ||||
| @ -1,15 +1,5 @@ | ||||
| 
 | ||||
| ## Testing Modules | ||||
| 
 | ||||
| ### Relevant Articles: | ||||
| This is a aggregator module containing several modules focused on testing libraries.  | ||||
| 
 | ||||
| - [Quick Guide to BDDMockito](http://www.baeldung.com/bdd-mockito) | ||||
| - [AssertJ Exception Assertions](http://www.baeldung.com/assertj-exception-assertion) | ||||
| - [Using Hamcrest Number Matchers](http://www.baeldung.com/hamcrest-number-matchers) | ||||
| - [Assertions in JUnit 4 and JUnit 5](http://www.baeldung.com/junit-assertions) | ||||
| - [REST-assured with Groovy](http://www.baeldung.com/rest-assured-groovy) | ||||
| - [Hamcrest Bean Matchers](http://www.baeldung.com/hamcrest-bean-matchers) | ||||
| - [Hamcrest Object Matchers](http://www.baeldung.com/hamcrest-object-matchers) | ||||
| - [Headers, Cookies and Parameters with REST-assured](http://www.baeldung.com/rest-assured-header-cookie-parameter) | ||||
| - [JSON Schema Validation with REST-assured](http://www.baeldung.com/rest-assured-json-schema) | ||||
| - [Testing Callbacks with Mockito](http://www.baeldung.com/mockito-callbacks) | ||||
|  | ||||
| @ -11,3 +11,4 @@ | ||||
| - [A Quick JUnit vs TestNG Comparison](http://www.baeldung.com/junit-vs-testng) | ||||
| - [Guide to JUnit 5 Parameterized Tests](https://www.baeldung.com/parameterized-tests-junit-5) | ||||
| - [JUnit 5 Conditional Test Execution with Annotations](https://www.baeldung.com/junit-5-conditional-test-execution) | ||||
| - [Assertions in JUnit 4 and JUnit 5](http://www.baeldung.com/junit-assertions) | ||||
|  | ||||
| @ -18,3 +18,7 @@ | ||||
| - [Hamcrest Common Core Matchers](http://www.baeldung.com/hamcrest-core-matchers) | ||||
| - [Testing Callbacks with Mockito](http://www.baeldung.com/mockito-callbacks) | ||||
| - [Using Hamcrest Number Matchers](https://www.baeldung.com/hamcrest-number-matchers) | ||||
| - [Quick Guide to BDDMockito](http://www.baeldung.com/bdd-mockito) | ||||
| - [Hamcrest Bean Matchers](http://www.baeldung.com/hamcrest-bean-matchers) | ||||
| - [Hamcrest Object Matchers](http://www.baeldung.com/hamcrest-object-matchers) | ||||
| - [Testing Callbacks with Mockito](http://www.baeldung.com/mockito-callbacks) | ||||
|  | ||||
| @ -3,3 +3,7 @@ | ||||
| - [REST-assured Support for Spring MockMvc](https://www.baeldung.com/spring-mock-mvc-rest-assured) | ||||
| - [Getting and Verifying Response Data with REST-assured](https://www.baeldung.com/rest-assured-response) | ||||
| - [REST Assured Authentication](https://www.baeldung.com/rest-assured-authentication) | ||||
| - [REST-assured with Groovy](http://www.baeldung.com/rest-assured-groovy) | ||||
| - [Headers, Cookies and Parameters with REST-assured](http://www.baeldung.com/rest-assured-header-cookie-parameter) | ||||
| - [JSON Schema Validation with REST-assured](http://www.baeldung.com/rest-assured-json-schema) | ||||
| 
 | ||||
|  | ||||
| @ -21,3 +21,4 @@ | ||||
| - [Using Conditions with AssertJ Assertions](http://www.baeldung.com/assertj-conditions) | ||||
| - [A Guide to JavaFaker](https://www.baeldung.com/java-faker) | ||||
| - [Running JUnit Tests Programmatically, from a Java Application](https://www.baeldung.com/junit-tests-run-programmatically-from-java) | ||||
| - [AssertJ Exception Assertions](http://www.baeldung.com/assertj-exception-assertion) | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user