maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar (JIRA)" <>
Subject [jira] Closed: (MECLIPSE-493) Automatically locate workspace
Date Tue, 23 Sep 2008 03:48:45 GMT


Barrie Treloar closed MECLIPSE-493.

       Resolution: Fixed
    Fix Version/s: 2.6

Eclispe Plugin
- workspace type changes from String to File
- getWorkspaceConfiguration() now locates the workspace if it is null.
- exposed some constants needed outside of class
- getProjectLocation()
  - now package scoped for unit testing
  - rewrote internals to read in the URI string inside ".location" file
  - now closes stream
- readArtefact() now takes projectLocation as File instead of String
- readAvailableJREs() returns null if no prefs file exists and a workspace was located.
  This causes the defaultJre to be used.
- added test fixtures used in TestCases.
- usePathToProject changed to which projects inside the workspace should be linked in the
  This value was only null to avoid re-initializing the internal workspaces, which test fixtures
- Removed localizedIndicator as static test fixtures are configured once at class load time
  regenerating these files each test run is not a large burden.  However misconfuration of
the test files
  and not regenerating was a source of errors during creation of extra ITs.
- Refactored out writeLocationFile()
- Deleted getWorkspaceLocation() as the variable is public.
- Added testProject( File basedir ) for ITs running inside the test eclipse workspaces.

> Automatically locate workspace
> ------------------------------
>                 Key: MECLIPSE-493
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Workspace settings
>    Affects Versions: 2.5.1
>            Reporter: Barrie Treloar
>            Assignee: Barrie Treloar
>             Fix For: 2.6
> Support locating the workspace automatically.
> Often the project will be located within an Eclipse workspace and it will save the user
manually using -Declipse.workspace by traversing the directory structure to locate a parent
directory that is the Eclipse workspace.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message