Merge pull request #2 from xlui/feature/2.0

Remove unsupport features, update actions

Author: xlui

Dockerfile

@@ -1,15 +1,15 @@
-FROM maven:3.6-jdk-11-slim
+FROM maven:3.6-openjdk-11-slim
 
-LABEL "name"="Maven CLI Action with JDK 11"
+LABEL "name"="Maven CLI For GitHub Actions"
 LABEL "maintainer"="xlui <i@xlui.me>"
-LABEL "version"="1.1.0"
+LABEL "version"="2.0"
 
-LABEL "com.github.actions.name"="GitHub Action for Maven & JDK 11"
-LABEL "com.github.actions.description"="Provide maven cli for JDK 11 projects."
+LABEL "com.github.actions.name"="Maven CLI For GitHub Actions"
+LABEL "com.github.actions.description"="Provide maven cli for GitHub Actions"
 LABEL "com.github.actions.icon"="package"
 LABEL "com.github.actions.color"="green"
-COPY LICENSE README.md /
 
+COPY LICENSE README.md /
 COPY entrypoint.sh /entrypoint.sh
 
 ENTRYPOINT ["/entrypoint.sh"]

README.md

@@ -1,66 +1,50 @@
-# GitHub Action for the Maven CLI
+# Maven CLI For GitHub Actions
 
-The [origin project](https://github.com/LucaFeger/action-maven-cli) creates a Maven action with only JDK 8. But I'm writing java with JDK 11 and in the short future I'll keep using JDK 11. So I have forked the origin repository and add support for JDK 11.
-
-The GitHub Action for [Maven](https://maven.apache.org/) wraps the Maven CLI to enable Maven commands to be run. This can be used to run every Maven Command.
+The Maven CLI For GitHub Actions wraps the maven cli to enable maven commands to be runned inner GitHub Actions. You can use all the maven commands to do whatever you want.
 
 ## Usage
 
 ```yml
-# This is a basic workflow to help you get started with Actions
-
-name: CI
+name: Run maven test on push
 
-# Controls when the action will run. Triggers the workflow on push or pull request 
-# events but only for the master branch
 on:
   push:
     branches: [ master ]
   pull_request:
     branches: [ master ]
 
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
-  # This workflow contains a single job called "build"
   build:
-    # The type of runner that the job will run on
     runs-on: ubuntu-latest
 
-    # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
-    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
-    - uses: actions/checkout@v2
-
-    # Runs a single command using the runners shell
-    - name: Run a one-line script
-      run: echo Hello, world!
+    - name: 1. Checkout code
+      uses: actions/checkout@v2
 
-    # Runs a set of commands using the runners shell
-    - name: Run maven script
-      uses: xlui/action-maven-cli/jdk11@master
-      id: test
+    - name: 2. Run maven test
+      uses: xlui/action-maven-cli
       with:
         lifecycle: 'clean package test'
 ```
 
-Under the last `jobs.build.steps.name` you can set the value of `uses` to this action.
+You can specify any maven lifecycle at the last part of the file.
 
-```yml
-uses: xlui/action-maven-cli/jdk11@master
-```
+In the above example we customize a lifecycle `clean package test`, the real command GitHub Actions run is:
 
-or
+```bash
+#!/bin/sh -l
 
-```yml
-uses: xlui/action-maven-cli/jdk8@master
-```
+set -e
 
-As JDK 11 is the latest LTS JDK, there is a convenient way to use it:
+echo "==========Starting Maven Commands=========="
 
-```yml
-uses: xlui/action-maven-cli@master
+sh -c "mvn clean package test"
+
+echo "==========Finished Maven Commands=========="
 ```
 
+Have you noticed the conversion?
+
 ## License
 
 The Dockerfile and associated scripts and documentation in this project are released under the [MIT License](LICENSE.md).

action.yml

@@ -1,5 +1,5 @@
-name: 'Maven CLI for the GitHub Actions'
-description: 'Use Maven CLI with JDK 8, 11, 13'
+name: 'Maven CLI For GitHub Actions'
+description: 'Use Maven CLI with JDK 8, 11, 14'
 inputs:
     lifecycle:
         description: 'Maven lifecycles'