Skip to content

Latest commit

 

History

History
416 lines (371 loc) · 23.4 KB

CHANGELOG.markdown

File metadata and controls

416 lines (371 loc) · 23.4 KB

Liferay Blade CLI Change Log

3.9.0 - 2020-1-23 - 23d6986650aac47c37e98a3a3aac5804de3970dd

  • BLADE-474: blade create can throw a NullPointerException when workspace version is set to latest.release
  • BLADE-475: Adopt new project-templates 5.0.0 api
  • BLADE-481: Maven sometimes fails with erroneous exception "Failed to launch process to delete files after JVM exit : java.lang.NoClassDefFoundError: org/bridj/Platform$DeleteFiles"
  • BLADE-482: Upgrade blade to use bnd 4.3.0
  • BLADE-483: Blade Up To Date Checker Sometimes Detects Current Version As Out Of Date
  • BLADE-486: As a developer, I would like blade watch to support docker
  • BLADE-487: get dockerImageId and dockerContainerId from ProjectInfo model
  • BLADE-489: Blade gw does not function like ./gradlew
  • BLADE-490: update build to gradle 5.6.4
  • BLADE-493: Use Gradle 5 Project Templates in Blade
  • BLADE-499: Update Blade CLI to use Project Templates 5.0.18
  • LPS-105502: Update project templates for gradle 5 compatibility
  • LRDOCS-7448: Blade upgradeProps sub-command is not explained

3.8.0 - 2019-9-19 - 7ccb989a2b8fef4786812c8f74a75eb81923d2ce

  • BLADE-221: Support for Blade CLI "Interactive" mode
  • BLADE-329: blade server init should work from any workspace directory
  • [BLADE-464]: Update to project templates 4.3.1 to include new spring mvc portlet template
  • BLADE-467: Create args not taking blade settings
  • BLADE-468: Init command should prompt user for version and not set it by default
  • LPS-98820: Compile java failed because of missing dependency when building service in 71 project with target.platform specified

3.7.4 - 2019-7-23 - 5fb0dece50bd5a9603337d942ceb730f31951885

  • BLADE-461: Use Project Templates 4.2.27 - Point users to Liferay JS Toolkit for Npm projects

3.7.3 - 2019-6-24 - 1e0872fd2051fdfe0a2b4665f396a865024cf162

  • Update to Project Templates 4.2.26
  • LPS-96205: Parameterize SB dependency injector to use either DS or spring
  • LPS-97114: Add display name to portlet related template

3.7.2 - 2019-6-19 - 261bf24cb6c9ab7ce70066576e2e1f22ff2e460f

  • BLADE-441: Use project templates 4.2.25
  • BLADE-452: blade buildService with Maven should use Canonical path to avoid Windows path problem

3.7.1 - 2019-6-17 - 169ed4f04a3a6c2af839e166fa6965aa0bfb287c

  • BLADE-400: blade update should have a flag to specify the repository URL
  • BLADE-436: add samples command tests for 7.2
  • BLADE-441: Use project templates 4.2.24
  • BLADE-442: Service builder project name should not be false in modules folder after convert

3.7.0 - 2019-5-30 - 8dc27994d5f0dad2bee9ed79f52f481cbbeaead2

  • BLADE-408: blade convert theme should not find theme under plugins-sdk folder
  • BLADE-423: blade convert should support keep the original plugin projects
  • BLADE-425: Fix Extension Classloader in the event of failure
  • BLADE-431: add support for new core ext project template
  • BLADE-440: Add maven bundle support deploy command
  • BLADE-441: Use project templates 4.2.20

3.6.0 - 2019-4-12 - 907dbac73496b2436fc44f03e71a19c522dc3c9a

  • BLADE-373: Change .blade/settings.properties to .blade.properties, add an auto-migration
  • BLADE-392: blade server run should work on Maven
  • BLADE-398: Create blade server start / run tests for verifying custom port functionality
  • BLADE-407: Convert command should support "source" to set the plugins sdk location
  • BLADE-409: support migration of portal jars in liferay-plugin-package.properties
  • BLADE-411: Blade buildService implementation for Maven
  • BLADE-412: Restore ability to use old gogo shell deploy functionality in Blade

3.5.0 - 2019-2-25 - dae6dffde28c20d3420d6bb34c8bc6e661a68c33

  • BLADE-343: Pass in environment param when running blade server init
  • BLADE-383: Exception stack trace is printed when certain commands are executed
  • BLADE-385: Better Blade Maven Workspace Detection and Handling
  • BLADE-386: remove unneeded project template test builds
  • BLADE-387: Blade should run even if custom extensions have errors
  • BLADE-388: snapshots script is broken, doesn't embed correct version of maven profile
  • BLADE-389: blade prompter can hang in certain circumstances
  • BLADE-390: Turn parallel tests off by default. turn back on by passing in param
  • BLADE-394: Add unit tests for Blade Server -d, --debug flag behavior
  • BLADE-395: Add a -p, --port flag for blade server start and blade server run
  • BLADE-397: blade server start -t does not tail the log for wildfly

3.4.3 - 2019-1-23 - 53683e6dee0a07972b79493944328e56bfaab9cd

  • BLADE-377: init command should honor the -p, --profile-name flag over any defaults
  • BLADE-380: Separate handling of settings directory and extensions directory
  • BLADE-381: 'blade update' should not run the updateCheck

3.4.2 - 2019-1-18 - 981940b943cc198836483b35569de8e3e3721f38

  • BLADE-346: Update to project templates
  • BLADE-361: blade 'deploy' should behave more like traditional "deploy" tasks, i.e. its behavior should be obvious
  • BLADE-377: init command should honor the -p, --profile-name flag over any defaults
  • BLADE-378: update gives confusing message when switching to released version

3.4.1 - 2018-12-18 - 3cc0d3f734001578fc14ff0c51f3b38b6f7daff9

  • BLADE-245: As a developer, I would to simplify the server command
  • BLADE-319: blade create does not handle modules.dir property with multiple values
  • BLADE-354: blade init will create new workspaces even if it is inside of another workspace without throwing an error
  • BLADE-356: blade cli tests sometimes leave a leftover liferay server process running
  • BLADE-357: Remove duplicate test classes from maven-profile
  • BLADE-358: if I'm on a snapshot version, the automatic 'checkForUpdate' doesn't prompt if a new snapshot is available
  • BLADE-359: Enable blade update functionality on Windows
  • BLADE-360: Deploying modules created from project templates (OOB) fail using Blade
  • BLADE-366: update project.templates dependency to 4.2.3
  • BLADE-367: maven-profile.jar incorrectly being embedded inside itself
  • BLADE-369: Update blade cli to use project templates 4.2.4
  • BLADE-370: publish maven-profile snapshots
  • BLADE-371: Add blade jar smoke tests
  • BLADE-372: daily update check gives wrong message when using snapshots
  • BLADE-375: update gradle tooling api to 4.10.2

3.3.0 - 2018-11-15 - 9939c44d9a1d981adfcae13ad168b6c63c2851d5

  • BLADE-214: Create a blade-extension blade sample project, demonstrating how blade may be extended with custom commands
  • BLADE-313: Add Maven support for blade server
  • BLADE-320: Notify Blade users of updates via the CLI so they don't have to manually check
  • BLADE-321: Strip version suffix of WAR artifact when it's deployed to Liferay Portal
  • BLADE-327: Add watch command
  • BLADE-331: Add Maven support for blade server init
  • BLADE-332: Update to project templates 4.1.8
  • BLADE-333: Publish Blade CLI JAR to Nexus
  • BLADE-334: Add set method for create command argument
  • BLADE-335: Modify blade update to install latest release from Nexus repo
  • BLADE-342: Prompt Maven users to create a .blade/settings.properties file if it does not exist
  • BLADE-344: Improve Blade errors to be more informative
  • BLADE-345: Make extension path required for blade extension install command
  • BLADE-346: Update to project templates 4.1.10
  • BLADE-347: Include Maven profile classes in Blade CLI JAR
  • BLADE-349: Skip project rebuilding when blade watch is executed
  • BLADE-350: Update test projects to use same Gradle wrapper as Blade CLI's root project
  • BLADE-355: Create release branch for Blade CLI
  • LRDOCS-5843: Wordsmith README for building Blade profiles and extensions

3.2.0 - 2018-10-08 - 46b7d0a258376c9dccd5fecaae6156ed5a797d89

  • BLADE-214: Create a blade-extension blade sample project, demonstrating how blade may be extended with custom commands
  • BLADE-286: blade should be able to create module ext project
  • BLADE-294: blade open . does not work
  • BLADE-296: deploy for wars is swallowing output
  • BLADE-300: the setter methods for InitArgs
  • BLADE-301: Add set methods for Server related args
  • BLADE-302: Investigate blade gw deploy
  • BLADE-304: As a developer I want blade to remember what liferay version is set so I don't have to
  • BLADE-307: Refactor extension tests into the extensions themselves
  • BLADE-308: improve blade classloader for both embedding and custom commands
  • BLADE-309: Commands with @BladeProfile are global
  • BLADE-310: Open command fails when running with argument
  • BLADE-311: Use a combined classloader for loading classes in blade
  • BLADE-314: As a developer, I would like to get version specific samples
  • BLADE-315: blade server init command for tooling-agnostic way to initialize the liferay-workspace
  • BLADE-323: Create documentation for building blade profiles

3.1.2 - 2018-08-30 - ba8e7d64a866b4fbef383be37522d0eaf3bc8b4f

  • BLADE-256: As a developer, i'd like tests to run in parallel
  • BLADE-265: Print Gradle Errors in Test Results
  • BLADE-270: blade init will fails if run in the empty folder
  • BLADE-271: blade server start for finding the right server to start
  • BLADE-274: blade deploy does not start wars on reinstall
  • BLADE-276: blade init . doesn't create a workspace
  • BLADE-277: blade server stop not recognizing folder names correctly
  • BLADE-280: update to project templates 4.1.5
  • BLADE-281: Creating project templates in workspace that has TP enabled should use TP enabled version of project template
  • BLADE-284: update to project templates 4.1.6

3.1.1 - 2018-07-18 - 5d9faab454e1023e3fbe8502365f752c26fcc7c9

  • BLADE-211: Add Changelog using changelog plugin
  • BLADE-253: Specify blade version in build config
  • BLADE-257: Correct server start command
  • BLADE-258: Always alert users of deployment errors
  • BLADE-259: Fix NPE in server stop command
  • BLADE-260: Fix exception in server stop command
  • BLADE-262: Update to project template 4.1.1 artifact
  • BLADE-264: Update default version to 7.1

3.1.0 - 2018-07-05 - 570a5b7ae626ee0e7bf8751656104c5e33f8512b

  • BLADE-214: Create a blade-extension blade sample project, demonstrating how blade may be extended with custom commands
  • BLADE-231: Blade Custom Project Template Support
  • BLADE-244: As a developer, I would like my tomcat logs to be colorized
  • BLADE-246: create project from service template doesn't show that -s is required
  • BLADE-250: extension install fails if you install same extension twice
  • BLADE-251: blade gw sometimes has trouble finding gradlew

Updated to use Project Templates 4.1.0

  • IDE-4081: Blade's MVC Portlet template doesn't generate javax.portlet.title Language key properly
  • LPS-78045: Remove exported package from portal-portlet-bridge-soy
  • LPS-79301: Project Templates: Remove build.gradle if build type is maven, pom.xml if gradle
  • LPS-79417: Blade template to create a social bookmark module
  • LPS-79495: Store Liferay-Versions in MANIFEST.MF of Project Templates
  • LPS-79496: Change project templates velocity templates to check if Liferay Version starts with 7.0, 7.1, rather than checking whole string
  • LPS-79653: Portlet 3.0: Upgrade to the Portlet 3.0.0 API
  • LPS-80284: Update bndlib to 3.5.0
  • LPS-80404: As a developer, I would like to see stacktraces from the gradlerunner build
  • LPS-80472: Use local npm proxy in CI
  • LPS-82590: Move project templates off snapshots

3.0.0 - 2018-03-30 - 52ac672f21e8503f4371b6dbc403a9527582eff4

Added

  • BLADE-190: As a developer, I would like blade to support deploying wars to Liferay
  • BLADE-199: As a developer, I would like to create a liferay maven workspace using blade
  • BLADE-201: Add log settings to all samples so their INFO logging can be seen
  • BLADE-211: Create CHANGELOG.md file in github for keeping track of changes
  • BLADE-228: blade create should support specifying the Liferay Version

Changed

  • BLADE-202: Update Blade CLI to use JCommander
  • BLADE-207: Upgrade all Blade Samples to set up logging
  • BLADE-214: Removed install command blade install ... and shell command should be used instead blade sh install ...
  • BLADE-226: Print warning and usage info when blade create -t fragment is invoked without -H and -h flags
  • BLADE-230: blade create -t argument should be mandatory

Fixed

  • BLADE-193: Deploy Command does not properly handle bundle states
  • BLADE-206: blade create puts wars inside the modules folder, they should go in the wars folder
  • BLADE-208: Restore blade version command and add a test for it
  • BLADE-209: Restore blade help command and add a test for it
  • BLADE-210: blade create inside of 'modules' subfolder of workspace fails to create a 'workspace' type of project
  • BLADE-212: blade init command failed for no destination
  • BLADE-216: Generating Blade Samples with Blade CLI is outdated and broken
  • BLADE-219: server start command can result in java.lang.IllegalStateException
  • BLADE-227: blade help is currently too verbose, should just be command names with description
  • BLADE-233: blade deploy causes java.lang.NumberFormatException: For input string: "lb -s -u"

2.3.1 - 2017-11-21

Changed

2.3.0 - 2017-11-02

Changed

  • Updated Gradle Plugins Workspace
    • LPS-73746: Trim authentication token in case users add extra lines into their token file.
    • LPS-73913: Add the ability to pass the Liferay bundle authentication token password from a file by setting the liferay.workspace.bundle.token.password.file property in gradle.properties
    • LPS-74124: Add the ability to configure the cache directory for downloaded Liferay bundles by setting the liferay.workspace.bundle.cache.dir property in gradle.properties
    • LPS-74818: Fail the build if the source and destination of the downloadBundle task are the same
    • LPS-75479: Use Liferay 7.0.4 GA5 by default
  • Updated Liferay Gradle Plugin
    • Updated Service Builder to 1.0.173
  • LPS-74994: Added NPM Project Templates
  • LPS-75587: Use latest Project Template Archetypes