[JBoss JIRA] (JBIDE-11882) Errors running builder 'JavaScript Validator'
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11882?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-11882 at 1/15/14 7:28 PM:
------------------------------------------------------------------
For JBIDE-11630: There is known issue in BugZilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366247 (RESOLVED WORKSFORME, probably fixed in another issue, 3.5.1). The patch is proposed for JSDT issue in BugZilla.
was (Author: vrubezhny):
For JBIDE-11630: There is known issue in BugZilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366247 (New, Not targeted yet). The patch is proposed for JSDT issue in BugZilla.
> Errors running builder 'JavaScript Validator'
> ---------------------------------------------
>
> Key: JBIDE-11882
> URL: https://issues.jboss.org/browse/JBIDE-11882
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 3.3.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: jsdt
> Fix For: LATER
>
>
> Errors running builder 'JavaScript Validator' occurs when importing some example projects with JavaScripts.
> See:
> - JBIDE-11652: Errors running builder 'JavaScript Validator' on project 'ticket-monster' (Resolved with a workaround that disables validation of JavaScripts)
> - JBIDE-11630: javascript validation error occurs when creating birt project
> The UpStream issue is created as an overall issue for JSDT problems.
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2857) Add OS X Mavericks to the support matrix
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2857:
---------------------------------------
[~burrsutter], do you want to add this as one of the potential items for 7.1.1? Or should it be left for 8.0.0?
> Add OS X Mavericks to the support matrix
> ----------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2851:
-----------------------------------
Yes, git support is part of JBDS. And for this particular jira, the goal is to describe (and clean up where necessary) how a team of developers would use a solution such as git + maven + ci/jenkins within the context of the IDE.
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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
12 years, 7 months
[JBoss JIRA] (TOOLSDOC-435) Update 8.0 User Guide text and screen caps for IDE look & behavior changes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-435?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-435:
-------------------------------------
Description:
Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
*Usage Data*
* Report JVM name (JBIDE-15596)
* Report 32/64-bit Eclipse/Java (JBIDE-16333)
* Report installs from JBDS Central (JBDS-2732)
* Report actual used features (JBDS-2848)
*Server Tools*
* Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
*Forge Tools*
* Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
* Ctrl+3?? (from JBIDE-16111)
*Web Service Tools*
* Support JAX-RS 2.0 (JBIDE-16329)
*Mobile Web Tools*
* Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
** Option to select which jQM version in mobile palette (JBIDE-16293)
** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
** New popup wizard?? (JBIDE-16326)
*BrowserSim*
* Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
*Hybrid Mobile Tools + CordovaSim*
* Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
* Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
* Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
* Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
* Issue exporting project if Android SDK location not set (JBIDE-16276)
* Changes to layout of CordovaSim UI (JBIDE-16323)
* Run configuration ignored for Android emulator (JBIDE-16330)
* 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
*OpenShift*
* New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
* Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
* Web balancer cartridge should not be listed (JBIDE-16040)
* Change to button names in port forwarding wizard (JBIDE-13963)
* Select which ports to forward rather than forward all (JBIDE-12600)
* Provide user-friendly way to increase Git timeout (JBIDE-12812)
* Fix timeout typo in Preferences pane (JBIDE-16157)
* Fix missing info i icon in new app wizard (JBIDE-16145)
* Only show gear sizes appropriate for domain in new app wizard (JBIDE-15936)
was:
Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
*Usage Data*
* Report JVM name (JBIDE-15596)
* Report 32/64-bit Eclipse/Java (JBIDE-16333)
*Server Tools*
* Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
*Forge Tools*
* Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
* Ctrl+3?? (from JBIDE-16111)
*Web Service Tools*
* Support JAX-RS 2.0 (JBIDE-16329)
*Mobile Web Tools*
* Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
** Option to select which jQM version in mobile palette (JBIDE-16293)
** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
** New popup wizard?? (JBIDE-16326)
*BrowserSim*
* Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
*Hybrid Mobile Tools + CordovaSim*
* Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
* Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
* Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
* Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
* Issue exporting project if Android SDK location not set (JBIDE-16276)
* Changes to layout of CordovaSim UI (JBIDE-16323)
* Run configuration ignored for Android emulator (JBIDE-16330)
* 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
*OpenShift*
* New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
* Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
* Web balancer cartridge should not be listed (JBIDE-16040)
* Change to button names in port forwarding wizard (JBIDE-13963)
* Select which ports to forward rather than forward all (JBIDE-12600)
* Provide user-friendly way to increase Git timeout (JBIDE-12812)
> Update 8.0 User Guide text and screen caps for IDE look & behavior changes
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-435
> URL: https://issues.jboss.org/browse/TOOLSDOC-435
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
>
> Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
> *Usage Data*
> * Report JVM name (JBIDE-15596)
> * Report 32/64-bit Eclipse/Java (JBIDE-16333)
> * Report installs from JBDS Central (JBDS-2732)
> * Report actual used features (JBDS-2848)
> *Server Tools*
> * Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
> *Forge Tools*
> * Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
> ** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
> ** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
> ** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
> ** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
> * Ctrl+3?? (from JBIDE-16111)
> *Web Service Tools*
> * Support JAX-RS 2.0 (JBIDE-16329)
> *Mobile Web Tools*
> * Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
> ** Option to select which jQM version in mobile palette (JBIDE-16293)
> ** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
> ** New popup wizard?? (JBIDE-16326)
> *BrowserSim*
> * Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
> *Hybrid Mobile Tools + CordovaSim*
> * Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
> * Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
> * Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
> * Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
> * Issue exporting project if Android SDK location not set (JBIDE-16276)
> * Changes to layout of CordovaSim UI (JBIDE-16323)
> * Run configuration ignored for Android emulator (JBIDE-16330)
> * 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
> *OpenShift*
> * New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
> * Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
> * Web balancer cartridge should not be listed (JBIDE-16040)
> * Change to button names in port forwarding wizard (JBIDE-13963)
> * Select which ports to forward rather than forward all (JBIDE-12600)
> * Provide user-friendly way to increase Git timeout (JBIDE-12812)
> * Fix timeout typo in Preferences pane (JBIDE-16157)
> * Fix missing info i icon in new app wizard (JBIDE-16145)
> * Only show gear sizes appropriate for domain in new app wizard (JBIDE-15936)
--
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
12 years, 7 months
[JBoss JIRA] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-445:
-------------------------------------
Assignee: Gorkem Ercan (was: Michelle Murray)
> Document the Hybrid Mobile project artifacts that should be placed under version control
> ----------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-445
> URL: https://issues.jboss.org/browse/TOOLSDOC-445
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - Hybrid Mobile Tools
> Affects Versions: 4.1.1
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.2.0
>
>
> I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}.
> I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects.
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Michelle Murray edited comment on JBDS-2851 at 1/15/14 6:31 PM:
----------------------------------------------------------------
[~burrsutter], when you say eGit "out of the box", do you mean that eGit is packaged as part of JBDS installations? If eGit is essential for using OpenShift then we can document some instructions. From the examples given in the description, we could document how to:
* import a git project in preparation for deploying it to OpenShift
* once deployed on OpenShift, check in changes without necessarily publishing to OpenShift
* view git commit history for app deployed on OpenShift
Notice how these are very OpenShift and git centric. [~burrsutter] and [~adietish], what other tasks do users need to be able to perform?
was (Author: mmurray):
[~burrsutter], when you say eGit "out of the box", do you mean that eGit is packaged as part of JBDS installations? If eGit is essential for using OpenShift then we can document some instructions. From the examples given in the description, we could document how to:
* import a git project in preparation for deploying it to OpenShift
* once deployed on OpenShift, check in changes without necessarily publishing to OpenShift
Notice how these are very OpenShift and git centric. [~burrsutter] and [~adietish], what other tasks do users need to be able to perform?
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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
12 years, 7 months
[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-447:
-------------------------------------
Affects Version/s: 4.1.1
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.1
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Michelle Murray
> Priority: Minor
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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
12 years, 7 months
[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-447:
-------------------------------------
Fix Version/s: 4.2.0
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.1
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.2.0
>
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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
12 years, 7 months
[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-447:
-------------------------------------
Component/s: User Guide - OpenShift Tools
(was: User Guide)
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Michelle Murray
> Priority: Minor
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2851:
---------------------------------------
[~burrsutter], when you say eGit "out of the box", do you mean that eGit is packaged as part of JBDS installations? If eGit is essential for using OpenShift then we can document some instructions. From the examples given in the description, we could document how to:
* import a git project in preparation for deploying it to OpenShift
* once deployed on OpenShift, check in changes without necessarily publishing to OpenShift
Notice how these are very OpenShift and git centric. [~burrsutter] and [~adietish], what other tasks do users need to be able to perform?
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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
12 years, 7 months