Skip to content

Commit b7325e8

Browse files
authored
Update java.md (#901)
Remove warning. Maven no longer copies into `~/.m2` so this isn't an issue.
1 parent f4d2c32 commit b7325e8

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

content/docs/howto/java.md

-2
Original file line numberDiff line numberDiff line change
@@ -178,8 +178,6 @@ pack build samples/java \
178178
--volume $HOME/.gradle:/home/cnb/.gradle:rw
179179
{{< /code/copyable >}}
180180

181-
**DO NOT** use this option if [including a Maven or Gradle binding]({{< relref "#connect-to-a-private-maven-repository" >}})! If you do this, it will overwrite your actual local config file with the binding file which could cause data loss. It is also unnecessary because we are volume mounting the entire Maven or Gradle directory into the container which includes your Maven and Gradle settings.
182-
183181
##### Include or Exclude Custom Files
184182

185183
When building your application from source code, the Java buildpacks will capture the output artifact from your build process, typically a JAR/WAR file, and include that in the image that is generated. If you need to include/exclude additional files you may do so by setting the `BP_INCLUDE_FILES` or `BP_EXCLUDE_FILES` environment variables. Each can be set with a colon separated list of glob patterns. If a file or directory matches then it'll be included or excluded. If both include and exclude patterns are specified then the include patterns are applied first, followed by the exclude patterns second. By default, no additional files are included or excluded.

0 commit comments

Comments
 (0)