groovy

devine package from directory structure

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: parser
  • Labels:
    None
  • Number of attachments :
    0

Description

So, while GROOVY-20 made package statements optional, it did not add magic to figure out missing package information from the directory structure.

Certainly now, packaging can be determined by comparing directory paths relative to a --sourcepath, eh?

Issue Links

is depended upon by

Task - A task that needs to be done. GROOVY-753 complete parser

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
james strachan added a comment -

Have a ponder about this one - no biggie, see what you think. It'd be nice for the location of a file in a file system (relative to a root directory) to be used as the mechanism to associate the package name to a class/script. If the package statement is used then use it - otherwise autogenerated it.

What you think? It'd make things simpler

Show
james strachan added a comment - Have a ponder about this one - no biggie, see what you think. It'd be nice for the location of a file in a file system (relative to a root directory) to be used as the mechanism to associate the package name to a class/script. If the package statement is used then use it - otherwise autogenerated it. What you think? It'd make things simpler
Hide
Permalink
Guillaume Laforge added a comment -

Groovy respects the Java conventions regarding packages.

Show
Guillaume Laforge added a comment - Groovy respects the Java conventions regarding packages.

People

  • Assignee:
    Guillaume Laforge
    Reporter:
    bob mcwhirter
Vote (2)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
33m
Original Estimate - 33 minutes
Remaining:
33m
Remaining Estimate - 33 minutes
Logged:
Not Specified
Time Spent - Not Specified