Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-2280

Being able to use ~ as the top level package root directory

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Duplicate
    • Major
    • 2.x Future
    • 2.15.1.Final
    • UI - Shell
    • None

    Description

      In Forge 1.x there was this notion of project root (with ~) but also the top level package root (with {}). So we could write something like that :

      new-project --named test --topLevelPackage com.mycomp.myproj
java new-class --named Test --package ~.constraints
Wrote com.mycomp.myproj.constraints.Test.java

      With the --package .constraints paramater, it will create a class under com.mycomp.myproj.constraints because {} represents the top level package com.mycomp.myproj.

      This is not possible with Forge 2.x. The same code in Forge 2.x produces the following exception : 

      project-new --named test --topLevelPackage com.mycomp.myproj
java-new-class --named Test --targetPackage ~.constraints
Exception when parsing/running: java-new-class --named Test6 --targetPackage ~.constraints, Invalid identifier : >~<

      When writing Forge scripts, it's much easier and reusable to be able to use the ~ represents the top level package.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue FORGE-2466 Cannot use '~' in most of the command parameters

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Sub-task - The sub-task of the issue FORGE-1391 cd~~ not going back to the project root directory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users FORGE-1751 Support Wildcards for package and class names

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. FORGE-1941 addon-build-and-install command doesn't understand ~ with a home dir.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. FORGE-2170 Forge addon-build-and-install doesn't work with wildcards "." "~"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              agoncal Antonio Goncalves (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: