File: develop.md

package info (click to toggle)
csvjdbc 1.0.37-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, forky, sid, trixie
  • size: 5,872 kB
  • sloc: java: 23,138; xml: 318; makefile: 2
file content (58 lines) | stat: -rw-r--r-- 1,798 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
## Building From Source

To checkout and build the latest source code from the
[CsvJdbc git repository](https://github.com/simoc/csvjdbc.git),
use the following commands ([git](http://git-scm.com/) and
[Maven](http://maven.apache.org/) must first be installed).

    cd $HOME
    mkdir workspace1
    cd workspace1
    git clone https://github.com/simoc/csvjdbc.git csvjdbc
    cd csvjdbc
    mvn install
    cd target
    dir csvjdbc*.jar

## Working With Eclipse

1. Start Eclipse with workspace `workspace1`
2. Install the JavaCC Eclipse Plug-in from the Help ->
Eclipse Marketplace... menu option
3. Create a new project named `csvjdbc` using menu option
File -> New -> Java Project
4. Open `src/main/javacc/org/relique/jdbc/csv/where.jj` in the Eclipse
Editor and then select menu option JavaCC -> Compile with javacc

## Maven Project Usage

CsvJdbc is available at [Maven Central](http://search.maven.org/).
To include CsvJdbc in a [Maven](http://maven.apache.org/) project,
add the following lines to the `pom.xml` file.

    <project>
     ...
    
      <dependencies>
        <dependency>
          <groupId>net.sourceforge.csvjdbc</groupId>
          <artifactId>csvjdbc</artifactId>
          <version>1.0.35</version>
        </dependency>
      </dependencies>

## Contributing

A change to CsvJdbc must first be entered as a
[Issue](https://github.com/simoc/csvjdbc/issues)
before starting development.
A [Pull Request](https://github.com/simoc/csvjdbc/pulls)
for an issue will then be accepted or not
accepted by a CsvJdbc administrator.

Completed changes must be provided as a [git](http://www.git-scm.com)
pull request and include
a unit test to test the changed functionality.

Label *good first issue* is used to identify existing
issues that are suitable for new developers.