Skip to content

Commit a088ed2

Browse files
authored
Update README.md
1 parent 5b2e052 commit a088ed2

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[![License Apache 2.0](https://img.shields.io/badge/license-Apache%20License%202.0-green.svg)](http://www.apache.org/licenses/LICENSE-2.0)
2-
[![Maven central](https://maven-badges.herokuapp.com/maven-central/com.igormaznitsa/jcp/badge.svg)](http://search.maven.org/#artifactdetails|com.igormaznitsa|jcp|7.0.1|jar)
2+
[![Maven central](https://maven-badges.herokuapp.com/maven-central/com.igormaznitsa/jcp/badge.svg)](http://search.maven.org/#artifactdetails|com.igormaznitsa|jcp|7.0.2|jar)
33
[![Codacy Badge](https://api.codacy.com/project/badge/grade/c6acda63097a40c68d8ca8eaef6180d8)](https://www.codacy.com/app/rrg4400/java-comment-preprocessor)
44
[![Java 1.8+](https://img.shields.io/badge/java-1.8%2b-green.svg)](http://www.oracle.com/technetwork/java/javase/downloads/index.html)
55
[![Maven 3.0+](https://img.shields.io/badge/maven-3.0%2b-green.svg)](https://maven.apache.org/)
@@ -59,7 +59,7 @@ The Preprocessor is published in the Maven Central (it is not published in Gradl
5959
<plugin>
6060
<groupId>com.igormaznitsa</groupId>
6161
<artifactId>jcp</artifactId>
62-
<version>7.0.1</version>
62+
<version>7.0.2</version>
6363
<executions>
6464
<execution>
6565
<id>preprocessSources</id>
@@ -78,13 +78,13 @@ The Preprocessor is published in the Maven Central (it is not published in Gradl
7878
# How to use from command line
7979
The Preprocessor jar can be started under Java as a console application. Let's take a look at short example below how to start in command line under Linux The Easy variant of usage:
8080
```
81-
java -jar jcp-7.0.1.jar --i:./test --o:./result
81+
java -jar jcp-7.0.2.jar --i:./test --o:./result
8282
```
8383
The Example just preprocess files from ./test folder which extensions allowed to be preprocessed by default, and places result into ./result folder, but keep in your mind that the preprocessor copies not all files, XML files will not be preprocessed by default. Files which extension are not marked for preprocessing will be just copied (of course if the extensions is not in the list of excluded file extensions)
8484

8585
More complex example:
8686
```
87-
java -jar jcp-7.0.1.jar --c --r --v --f:java,xml --ef:none --i:./test --o:./result '--p:HelloWorld=$Hello world$'
87+
java -jar jcp-7.0.2.jar --c --r --v --f:java,xml --ef:none --i:./test --o:./result '--p:HelloWorld=$Hello world$'
8888
```
8989
- --c clear the destination folder before work
9090
- --r remove all Java-style comments from preprocessed result files
@@ -143,5 +143,5 @@ In opposite a regular document, a Java document has as minimum two sections - pr
143143
# How to remove all coments from sources
144144
Sometime it is very useful to remove totally all comments from sources, such possiblitiy was included into JCP and can be activated through special flag or command line switcher. The Example of use for comment removing through CLI interface
145145
```
146-
java -jar ./jcp-7.0.1.jar --i:/sourceFolder --o:/resultFolder -ef:none --r
146+
java -jar ./jcp-7.0.2.jar --i:/sourceFolder --o:/resultFolder -ef:none --r
147147
```

0 commit comments

Comments
 (0)