No commit message

RoFage/build.xml

@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="RoFage" default="default" basedir=".">
+    <description>Builds, tests, and runs the project RoFage.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar-with-manifest:    JAR building (if you are using a manifest)
+      -do-jar-without-manifest: JAR building (if you are not using a manifest)
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="RoFage-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

RoFage/derby/RoFageDB/service.properties

@@ -0,0 +1,22 @@
+#G:\dev\NetBeansProjects\RoFage\derby\RoFageDB
+# *********************************************************************************
+# ***                Veuillez ne PAS éditer ce fichier.                 ***
+# *** LA MODIFICATION DE SON CONTENU PEUT ENTRAINER UNE ALTERATION DES DONNEES. ***
+# *********************************************************************************
+#Sun Mar 01 17:22:41 CET 2009
+SysschemasIndex2Identifier=225
+SyscolumnsIdentifier=144
+SysconglomeratesIndex1Identifier=49
+SysconglomeratesIdentifier=32
+SyscolumnsIndex2Identifier=177
+SysschemasIndex1Identifier=209
+SysconglomeratesIndex3Identifier=81
+SystablesIndex2Identifier=129
+SyscolumnsIndex1Identifier=161
+derby.serviceProtocol=org.apache.derby.database.Database
+SysschemasIdentifier=192
+derby.storage.propertiesId=16
+SysconglomeratesIndex2Identifier=65
+derby.serviceLocale=fr_FR
+SystablesIdentifier=96
+SystablesIndex1Identifier=113

RoFage/derby/derby.log

@@ -0,0 +1,6 @@
+----------------------------------------------------------------
+2009-03-01 23:28:32.237 GMT:
+ Amor�age de Derby version The Apache Software Foundation - Apache Derby - 10.3.1.4 - (561794) : instance c013800d-011f-c45e-0d60-0000240d4efa
+sur le r�pertoire de base de donn�es G:\dev\NetBeansProjects\RoFage\derby\RoFageDB  
+
+Chargeur de classe de la base de donn�es d�marr� - derby.database.classpath=''

RoFage/lib/Log4J/src/assembly/bin.xml

@@ -0,0 +1,64 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+-->
+<assembly>
+	<id>bin</id>
+	<formats>
+		<format>zip</format>
+		<format>tar.gz</format>
+	</formats>
+	<baseDirectory>apache-log4j-${project.version}</baseDirectory>
+	<includeSiteDirectory>true</includeSiteDirectory>
+	<fileSets>
+		<fileSet>
+			<includes>
+				<include>*.txt</include>
+				<include>*.sample</include>
+				<include>*.xml</include>
+				<include>INSTALL</include>
+				<include>KEYS</include>
+				<include>LICENSE</include>
+				<include>NOTICE</include>
+				<include>contribs/**</include>
+				<include>examples/**</include>
+				<include>src/assembly/**</include>
+				<include>src/changes/**</include>
+				<include>src/main/**</include>
+				<include>src/ntdll/**</include>
+				<include>src/performance/**</include>
+				<include>src/site/**</include>
+				<include>tests/README</include>
+				<include>tests/*.xml</include>
+				<include>tests/*.sample</include>
+				<include>tests/*.bat</include>
+				<include>tests/input/**</include>
+				<include>tests/resources/**</include>
+				<include>tests/src/**</include>
+				<include>tests/witness/**</include>
+			</includes>
+		</fileSet>
+	</fileSets>
+        <files>
+        	<file>
+		   <source>target/log4j-${project.version}.jar</source>
+                </file>
+                <file>
+                   <source>target/NTEventLogAppender.dll</source>
+                   <fileMode>0755</fileMode>
+                </file>
+        </files>
+</assembly>