[jbosstools-issues] [JBoss JIRA] (JBIDE-13703) Explore better ways for team import/sharing of projects
[
https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-13703:
--------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta1)
This is a non-trivial subject I don't think we can cover before 4.1.0.GA.
In the mean time, in order to get a better workflow, I suggest you install the appropriate
m2eclipse-(your scm) connector.
Maven connectors for Subclipse, Subversive, EGit can be found in Window > Preferences
> Maven > Discovery > Open Catalog
The CVS connector's been dropped from the Maven Discovery Catalog for some reason
(most likely, Sonatype doesn't maintain it anymore). I haven't tested the it, but
you can install it from
http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-cvs/0.13.0/N/0.13...
Once the appropriate connector is installed, you can do New > Project > Checkout
Maven Projects from SCM. See
http://books.sonatype.com/m2eclipse-book/reference/creating.html#creating...
for more information.
Explore better ways for team import/sharing of projects
-------------------------------------------------------
Key: JBIDE-13703
URL: https://issues.jboss.org/browse/JBIDE-13703
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central, common/jst/core
Reporter: Burr Sutter
Assignee: Fred Bricon
Fix For: 4.1.x
Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG
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