Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9877

project examples should go into user workspace and preferably be able to set it differentl

        Details

          Description

          noticed today that project examples goes into a hidden workspace folder instead of where users normally store their projects.

          i.e. /Users/max/Documents/workspaces/jbosstools-trunk/.JBossToolsMavenProjects/numberguess/jboss-as-numberguess

          it should at least be /Users/max/Documents/workspaces/jbosstools-trunk/numberguess/jboss-as-numberguess

          and optimally users should be able to say which root directory they want projects downloaded by an example goes to.

            Gliffy Diagrams

              Issue Links

              cloned to

              Bug - A problem which impairs or prevents the functions of the product. JBIDE-10009 project examples should provide way to set the output direcotry

              • Major - A request that should be considered seriously but is not a show stopper.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                snjeza Snjezana Peco added a comment -

                This issue has been partially fixed within JBIDE-9774. The is committed to the trunk and 3.3.0.M4 branch.

                > and optimally users should be able to say which root directory they want projects downloaded by an example goes to.

                Since the standard Eclipse Import>Existing Projects into Workspace action doesn't enable a user to change the destination location, I suppose we also don't have to do that.
                If you still think differently, please reopen this jira.

                BTW
                I have chosen a location to unpack an archive since m2e doesn't provide importing a project from any archive.

                Show
                snjeza Snjezana Peco added a comment - This issue has been partially fixed within JBIDE-9774 . The is committed to the trunk and 3.3.0.M4 branch. > and optimally users should be able to say which root directory they want projects downloaded by an example goes to. Since the standard Eclipse Import>Existing Projects into Workspace action doesn't enable a user to change the destination location, I suppose we also don't have to do that. If you still think differently, please reopen this jira. BTW I have chosen a location to unpack an archive since m2e doesn't provide importing a project from any archive.
                Hide
                Permalink
                maxandersen Max Rydahl Andersen added a comment -

                thanks - having the default content be in a proper location was the most important part, cloned this issue and reduced the severity for the remaining issue of users being able to set their example destination: JBIDE-10009

                Show
                maxandersen Max Rydahl Andersen added a comment - thanks - having the default content be in a proper location was the most important part, cloned this issue and reduced the severity for the remaining issue of users being able to set their example destination: JBIDE-10009
                Hide
                Permalink
                mmalina Martin Malina added a comment -

                Verified in jbdevstudio-product-eap-macosx-cocoa-5.0.0.v201110271830R-H42-M4.jar . The examples are now added directly to the workspace directory.

                Show
                mmalina Martin Malina added a comment - Verified in jbdevstudio-product-eap-macosx-cocoa-5.0.0.v201110271830R-H42-M4.jar . The examples are now added directly to the workspace directory.

                  People

                  • Assignee:
                    snjeza Snjezana Peco
                    Reporter:
                    maxandersen Max Rydahl Andersen
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Development