[jbosstools-issues] [JBoss JIRA] (JBIDE-18314) Import Maven - copy into workspace

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002703#comment-13002703 ] 

Max Rydahl Andersen commented on JBIDE-18314:
---------------------------------------------

that is deliberate.

eclipse has limitations on what/how projects can behave inside a workspace.

i.e. the folder name of the project have to be exactly the same as the project name - that does not fly well with maven, i.e. jboss quickstarts insists on having folder name != maven project name thus the quickstarts would not work with this.

Also, maven projects often have a nested structure, that does not fly well within workspace.

This and similar issues is why git projects defaults to clone *outside* the workspace too.

In general storing projects inside the workspace is *not* recommended for anything but trivial non-nested, non-git shared projects...

I suggest you either copy the projects manually or use git on the project so you can just hack away ;)



> Import Maven - copy into workspace
> ----------------------------------
>
>                 Key: JBIDE-18314
>                 URL: https://issues.jboss.org/browse/JBIDE-18314
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven, upstream
>            Reporter: Burr Sutter
>            Assignee: Fred Bricon
>         Attachments: 2014-09-11_2105.png
>
>
> Most other Eclipse Import tools have the "copy into workspace" feature but Maven does not - this is particular useful when reviewing samples and not wishing to "injure" them.  Copy into workspace means I have my own working copy and can hack away.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)