Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/lfuelling/cleanfoot

Fork of Greenfoot (including BlueJ) using Maven
https://github.com/lfuelling/cleanfoot

cleanfoot game-development game-engine gradle greenfoot java java-8 java-library javafx maven

Last synced: 3 months ago
JSON representation

Fork of Greenfoot (including BlueJ) using Maven

Awesome Lists containing this project

README

        

# Cleanfoot

This is a fork of Greenfoot 3.5.4 (the last version supporting Java 8) which was moved from Ant to Maven.

The goal of this project is to provide a Java 1.8 compatible, supported Greenfoot version with some fixes like a public `greenfoot.Font(java.awt.Font)` constructor, cleaned up code, up to date dependencies and of course libraries that are usable via Maven.

## Usage

### Maven

To use this library, you need to use the GammelCloud repo:

```xml


jitpack.io
https://jitpack.io

```

And the following dependency:

```xml

com.github.lfuelling
cleanfoot
3.5.7

```

### Gradle

If you use Gradle, you can reference the repository like this:

```groovy
repositories {
maven { url 'https://jitpack.io' }
}
```

and the dependency itself like this:

```groovy
implementation 'com.github.lfuelling:cleanfoot:3.5.7'
```

### Code

After adding it, the library can be used like the regular Greenfoot project is used (ie. no package names have been changed). The only thing you need to add is a launcher class that extends `GreenfootScenarioApplication` and has a `main` method to launch the application.
If you need more information regarding using Greenfoot with Maven/Gradle and its implications, please see [this blog post](https://lerks.blog/p/making-games-with-greenfoot-without-greenfoot).

## Development

- The `THIRD-PARTY.txt` file is generated by running:
- `$ mvn license:add-third-party -Dlicense.outputDirectory=. -Dlicense.thirdPartyFilename=THIRD-PARTY.txt`
- The file bundled with Greenfoot/BlueJ is outdated.
- Building is done using: `$ mvn clean install -DskipTests`
- Publish is done using: `$ mvn clean install -DskipTests deploy:deploy`