All notable changes to this project will be documented in this file.
- Update to appengine-plugins-core 0.10.0 that supports GAE java17 and java21 runtimes.
- Update to appengine-plugins-core 0.9.9, for automatic Java 17 compatibility when running local devserver appengine-plugins-core#894.
- Update to appengine-plugins-core 0.9.8 which includes a version upgrade for gson to 2.8.9 and fix for
StringIndexOutOfBoundsException
. (#418)
- Update to appengine-plugins-core 0.9.7 for Java 17 compatibility (#413)
- Update to appengine-plugins-core 0.9.5 (#405)
- Fixed bug when using
plugins
block inbuild.gradle
(#388)
appengine.tools.verbosity
option for defining gcloud log verbosity (#384)
- Update to appengine-plugins-core 0.9.0 (#377)
- Includes support for binary artifacts for app.yaml based deployments (appengine-plugins-core:#840)
- Update to appengine-plugins-core 0.8.1 (#364)
- Automatically copy
Class-Path
entries in jar manifest to staging directory (appengine-plugins-core:#804)
gcloudMode
toappengine.deploy
block (#356)
- Remove release candidate warning (#344)
See 2.0.0-rc1 - 2.0.0-rc6 for details
- Dev App Server
v2-alpha
support removed.appengineStop
doesn't fail build on failure, just logs error
- Cloud Sdk
cloudSdkHome
,cloudSdkVersion
,serviceAccountKeyFile
added toappengine.tools
configuration block.appengineCloudSdkLogin
to trigger cloud sdk login flowcheckCloudSdk
validates version of installed sdk on system- Managed Cloud SDK
- Auto download google cloud sdk if no
cloudSdkHome
provided - Skip download in
--offline
mode - Do not download appengine components for app.yaml based deployments
- Auto download google cloud sdk if no
- Auto inject command runners into customer user appengine tasks
- Support for multiple extra files directories:
extraFilesDirectory
->extraFilesDirectories
- Support for app.yaml based standard deployments
project
is renamed toprojectId
projectId
andversion
are required parameters. Must be set to a value or toGCLOUD_CONFIG
to delegate to gcloud.projectId
can be configured for multi-module dev appserver runsdeployables
config parameter removedappYamls
config paramter removed
- Remove support for
APPENGINE_CONFIG
option inprojectId
andversion
(#325) - Remove support for
v2-alpha
devappserver version (#336)
- Actually skip downloading/updating the cloud sdk in offline mode (#337)
- Update appengine-plugins-core to 0.7.3 (#322)
- Resolve
GCLOUD_CONFIG
,APPENGINE_CONFIG
late (#321) - Fix
UP-TO-DATE
configuration on some tasks (#320) - Only download appengine components of cloud sdk when running compat projects (#317)
extraFilesDirectory
->ExtraFilesDirectories
(#315), (#316)
- Add deprecated error for
appengine.deploy.project
(#295) - Old flex build path is now used for all app.yaml (standard and flex) based builds (#310)
- Update appengine-plugins-core to 0.7.1 (#308)
- Changed
appengine.deploy.project
->appengine.deploy.projectId
(#286). - New
appengine.run.projectId
to set project for devserver runs. (#286).
- Auto inject internal command runners into custom app engine tasks (#279).
- New
cloudSdkVersion
parameter to specify desired Cloud SDK version. - New
downloadCloudSdk
task installs/updates the Cloud SDK and Java App Engine components (#205). Task runs automatically whencloudSdkHome
is not configured. - New
checkCloudSdk
task validates the Cloud SDK installation (#212). Task runs automatically whencloudSdkHome
andcloudSdkVersion
are both configured. - New
appengine.tools.serviceAccountKeyFile
configuration parameter, andappengineCloudSdkLogin
task. (#235) - New
appengineDeployAll
task to deploy application with all valid yaml configs simultaneously. (#239, #240)
appengineStop
no longer fails if the stop request to server fails, but it will log an error. (#267)- Upgrade App Engine Plugins Core dependency to 0.5.2.
- Remove deprecated
appYamls
parameter. project
andversion
are no longer pulled from the global gcloud state by default.project
must be configured in build.gradle using thedeploy.project
property, users may use special keywords for project to specify that they would like to read it from appengine-web.xml (project = "APPENGINE_CONFIG"
) or from gcloud global state (project = "GCLOUD_CONFIG"
).version
is also configured the same way.- Removed
deployables
parameter. To deploy specific configuration files, use the appropriate deploy tasks (i.e. appengineDeployCron, appengineDeployIndex, etc.) (#261).
- Build Extensions Statically (#192)
- Make extensions accessible to Kotlin users (#191)
- Check minimum gradle version (#169)
- New
<additionalArguments>
parameter to pass additional arguments to Dev App Server (#179), relevant pull request in App Engine Plugins Core: appengine-plugins-core/433
- Gradle 3.4.1 is required.
- Upgrade App Engine Plugins Core dependency to 0.3.9 (#179)
- Log Dev App Server output to file (#156)
- Gradle 4.0 is required.
- Preserve datastore-indexes-auto.xml across non-clean rebuilds (#165)
- Use sync instead of copy on the explodeWar task (#162)
- Allow direct application of standard or flexible plugin (#144)
- Fix path to appengine-web.xml in fallback detection of standard or flexible environment (#136)
- New
environment
option in therun
closure to pass environment variables to Dev App Server (#128) (appengine-plugins-core/381) - Automatically read environment from
appengine-web.xml
(appengine-plugins-core/378)
- Upgrade App Engine Plugins Core dependency to 0.3.2 (#128)
appengineShowConfiguration
no longer prints the gradle project parameters of extensions (#121)
- Dev Appserver1 integration (#113)
- Primitive User Guide
- Default local dev server is Java Dev Appserver1
- Flex Staging only copies app.yaml to staging out via (#363)
- Output directory for ExplodeWar is now
${buildDir}/exploded-<projectName>
instead ofexploded-app
(#117)
- Flex deployments failing in multimodule configuration (#108)