-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the current way of getting to a working build? #3
Comments
Hmm, thanks for the file, and it should work! I get
|
I'm getting this:
|
I'm also wondering how your flywayMigrate and jooqGenerate are working, when you've stopped running the database they both connect to. |
I hit the same issue as @Sch3lp, but I think I've found the root cause of the issue. I found that removing the following line allowed the Line 139 in 9de9031
That line was added under a commit to improve the build time of the application by caching the |
Here's a suggestion for a
CONTRIBUTING.md
file:Contributing
Prerequisites
Before you run ./gradlew build
Since this project uses jOOQ's generated classes we'll first need to generate those.
jOOQ requires a database connection to do so, and to make sure the whole team has the same database schema to generate the jOOQ classes from, we use Flyway to perform database migrations.
./gradlew flywayMigrate
(by default it uses your postgres running at 5433, aka the test database)../gradlew generateJooq
This should generate classes in
build/generated-src/jooq/main
under a package ofcom.gildedrose.db
That last part is not working for me however.
I have a running database, and I can see the items table that was created because of the flyway migration.
But when I run generateJooq, I don't get any generated classes.
What am I still doing wrong?
The text was updated successfully, but these errors were encountered: