Skip to content
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

Change to use absolute path as db.basedir at initdb #146

Closed
2 tasks done
kazuki43zoo opened this issue Jul 27, 2015 · 0 comments
Closed
2 tasks done

Change to use absolute path as db.basedir at initdb #146

kazuki43zoo opened this issue Jul 27, 2015 · 0 comments
Assignees
Milestone

Comments

@kazuki43zoo
Copy link
Contributor

Description

Currently, db.basedir has been specified using relative path (see here).
However if relative path is used, there is possible to occur a build error at sql execution plugin.
(Actually, the build error has been occurred at the travis-ci)

projectName-initdb/pom.xml

<db.basedir>src/main/sqls/postgres</db.basedir>

Possible Solutions

Change to use absolute path.

projectName-initdb/pom.xml

<db.basedir>${project.basedir}/src/main/sqls/postgres</db.basedir>

Affects Version/s

  • 5.0.0.RELEASE
  • 1.0.2.RELEASE

Fix Version/s

  • 5.1.0
  • 5.0.2

Issue Links

@kazuki43zoo kazuki43zoo added this to the 5.0.2 milestone Jul 27, 2015
making added a commit that referenced this issue Aug 1, 2015
#146: Change to use absolute path as db.basedir at initdb
kazuki43zoo added a commit that referenced this issue Aug 6, 2015
making added a commit that referenced this issue Aug 7, 2015
[5.0.x] #146: Change to use absolute path as db.basedir at initdb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants