• R/O
  • HTTP
  • SSH

hayashi: Commit

hayashi lib.

Commit MetaInfo

Revisióna2765814b242a8cd82119b507f25759ee2e13fee (tree)
Tiempo2020-11-22 19:32:34
Autorhaya4 <hayashi.yuu@gmai...>

Log Message

delete file

Cambiar Resumen

  • delete: .classpath
  • modified: .gitignore (diff)
  • delete: lib/activation-1.1.jar
  • delete: lib/hamcrest-core-1.3.jar
  • delete: lib/junit-4.12.jar
  • delete: lib/mail-1.4.jar
  • delete: lib/servlet-api.jar
  • delete: lib/xercesImpl.jar
  • delete: nbbuild.xml

Diferencia incremental

--- a/.classpath
+++ /dev/null
@@ -1,14 +0,0 @@
1-<?xml version="1.0" encoding="UTF-8"?>
3- <classpathentry kind="src" path="src"/>
4- <classpathentry kind="src" path="test"/>
5- <classpathentry kind="lib" path="lib/activation-1.1.jar"/>
6- <classpathentry kind="lib" path="lib/junit.jar"/>
7- <classpathentry kind="lib" path="lib/mail-1.4.jar"/>
8- <classpathentry kind="lib" path="lib/servlet-api.jar"/>
9- <classpathentry kind="lib" path="lib/xercesImpl.jar"/>
10- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
11- <classpathentry kind="con" path="org.eclipse.jdt.junit.JUNIT_CONTAINER/4"/>
12- <classpathentry kind="lib" path="/home/yuu/workspace/AdjustTime/importPicture/hayashi_0226.jar"/>
13- <classpathentry kind="output" path="classes"/>
--- a/.gitignore
+++ b/.gitignore
@@ -9,6 +9,6 @@ doc
99 /dist/
1010 /target/
1111 /build/
1313 build.*
1414 nbnuild.xml
Binary files a/lib/activation-1.1.jar and /dev/null differ
Binary files a/lib/hamcrest-core-1.3.jar and /dev/null differ
Binary files a/lib/junit-4.12.jar and /dev/null differ
Binary files a/lib/mail-1.4.jar and /dev/null differ
Binary files a/lib/servlet-api.jar and /dev/null differ
Binary files a/lib/xercesImpl.jar and /dev/null differ
--- a/nbbuild.xml
+++ /dev/null
@@ -1,73 +0,0 @@
1-<?xml version="1.0" encoding="UTF-8"?>
2-<!-- You may freely edit this file. See commented blocks below for -->
3-<!-- some examples of how to customize the build. -->
4-<!-- (If you delete it and reopen the project it will be recreated.) -->
5-<!-- By default, only the Clean and Build commands use this build script. -->
6-<!-- Commands such as Run, Debug, and Test only use this build script if -->
7-<!-- the Compile on Save feature is turned off for the project. -->
8-<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
9-<!-- in the project's Project Properties dialog box.-->
10-<project name="hayashi" default="default" basedir=".">
11- <description>Builds, tests, and runs the project hayashi.</description>
12- <import file="nbproject/build-impl.xml"/>
13- <!--
15- There exist several targets which are by default empty and which can be
16- used for execution of your tasks. These targets are usually executed
17- before and after some main targets. They are:
19- -pre-init: called before initialization of project properties
20- -post-init: called after initialization of project properties
21- -pre-compile: called before javac compilation
22- -post-compile: called after javac compilation
23- -pre-compile-single: called before javac compilation of single file
24- -post-compile-single: called after javac compilation of single file
25- -pre-compile-test: called before javac compilation of JUnit tests
26- -post-compile-test: called after javac compilation of JUnit tests
27- -pre-compile-test-single: called before javac compilation of single JUnit test
28- -post-compile-test-single: called after javac compilation of single JUunit test
29- -pre-jar: called before JAR building
30- -post-jar: called after JAR building
31- -post-clean: called after cleaning build products
33- (Targets beginning with '-' are not intended to be called on their own.)
35- Example of inserting an obfuscator after compilation could look like this:
37- <target name="-post-compile">
38- <obfuscate>
39- <fileset dir="${build.classes.dir}"/>
40- </obfuscate>
41- </target>
43- For list of available properties check the imported
44- nbproject/build-impl.xml file.
47- Another way to customize the build is by overriding existing main targets.
48- The targets of interest are:
50- -init-macrodef-javac: defines macro for javac compilation
51- -init-macrodef-junit: defines macro for junit execution
52- -init-macrodef-debug: defines macro for class debugging
53- -init-macrodef-java: defines macro for class execution
54- -do-jar: JAR building
55- run: execution of project
56- -javadoc-build: Javadoc generation
57- test-report: JUnit report generation
59- An example of overriding the target for project execution could look like this:
61- <target name="run" depends="hayashi-impl.jar">
62- <exec dir="bin" executable="launcher.exe">
63- <arg file="${dist.jar}"/>
64- </exec>
65- </target>
67- Notice that the overridden target depends on the jar target and not only on
68- the compile target as the regular run target does. Again, for a list of available
69- properties which you can use, check the target you are overriding in the
70- nbproject/build-impl.xml file.
72- -->
Show on old repository browser