[jbosstools-issues] [JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

[Max Rydahl Andersen (JIRA)]

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

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

I agree this sucks but the problem is the CVS tooling was created before something like Maven got into eclipse. The workflow you follow is just not what the eclipse CVS tooling was expecting. It expects the checkout to have a working eclipse project.

We can try and get this fixed in eclipse by allowing for some kind of "detect what kind of project importer should be run based on files in the checkout" but this will not make it into eclipse anytime soon.

What we can do is add our own "Import existing project" kind of wizard which could work with the various team providers but it would be our own custom UI and will add to the already existing set of crowded wizards. But at least we would have something we could point users to from Central etc.

About CVS not being enabled automatically then this is a general problem for team connections like svn and git too. They tend to not get automatically enabled (you have to use Team > Share Project...). I think this is mainly not done since enabling it on large projects can slow the IDE down considerably (i.e. if you have annotation or labels enabled you will have things be slow). Again, I think we here could consider having an "Check things on import" for projects that checks what kind of cvs, svn, git etc. files are available and offer to enable it.
 
Note: In the PDF you say you are looking for a simple Compile and Build button in the IDE but that is just not how Eclipse works - the user is not supposed to need to call these since eclipse will incrementally compile and build actions are specific to what kind of project you are importing using. But the Build button is under the Project menu if you need it.

Problem is probably that you expect Eclipse to use Maven or Ant or Gradle to do its build - but it simply aren't; it uses its own build and via m2e-wtp we use what is in the pom.xml to tell eclipse what to do.

Thus if your pom file is "normal" everything should be fine, but if you got special things, then yes you need the custom maven invocations like mvn install/mvn package - but not really any good place to put these in the IDE.




                
> Team - Verify the workflow
> --------------------------
>
>                 Key: JBIDE-13703
>                 URL: https://issues.jboss.org/browse/JBIDE-13703
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>            Reporter: Burr Sutter
>            Assignee: Burr Sutter
>         Attachments: JBDS-usability.pdf
>
>
> The average end-user would like to:
> 1) check out (clone) a project from CVS, SVN or Git
>  -- add repo, navigate repo, check out a project
>  -- project may or may not have .classpath, .project or .settings files
>  -- project may be Maven-based
> and see if the following work
> 2) Are the appropriate facets enabled?
> 3) Does it build immediately?
> 4) Can I immediately hit the run button to launch it on my app server?
> 5) Can I immediately hit the debug button to debug it on my app server?
>  -- how do I step if there are no break points?
> 6) Make a change to a file, re-run/debug again
> 7) Run JUnit tests
> 8) Check the change back into the repo with comments

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira