[jboss-user] [JBoss Tools] - JBossToolsFAQ
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: JBossToolsFAQ To view the document, visit: https://community.jboss.org/docs/DOC-10796 -- *General FAQs* * https://community.jboss.org/docs/DOC-10797 JBoss Tools FAQ * https://community.jboss.org/docs/DOC-11753 JBoss Developer Studio FAQ * https://community.jboss.org/docs/DOC-10801 TroubleShooting * https://community.jboss.org/docs/DOC-14297 Matrix of supported platforms, runtimes and technologies in JBoss Tools/JBDS *Installation* * http://www.jboss.org/tools/download/installation JBoss Tools Installation Guide * https://community.jboss.org/docs/DOC-11754 JBoss Developer Studio Installation FAQ *Feature FAQs* * https://community.jboss.org/docs/DOC-18100 BrowserSim * https://community.jboss.org/docs/DOC-10862 Visual Editor *Building and Testing* * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/faq.md Building JBoss Tools 4.1 * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_to_build_jbosstools_4.adoc Building JBoss Tools 4 * http://www.jboss.org/tools/docs/testing.html Testing JBoss Tools (Using PDE Debugger w/ a Tycho/Maven Build) -- Comment by going to Community [https://community.jboss.org/docs/DOC-10796] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - JBossToolsTroubleShootingFAQ
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: JBossToolsTroubleShootingFAQ To view the document, visit: https://community.jboss.org/docs/DOC-10801 -- h2. JBoss Tools Trouble Shooting FAQ h3. Read this before adding an entry This FAQ is intended to provide information on JBoss Tools (and Eclipse in general) trouble shooting. *Q : The plugins does not seem to be loaded or active after installation* *A* : This can unfortunately happen if either some steps in the installation failed, Eclipse is somehow misconfigured or there are some conflicting plugins installed. To find out why plugins are not being loaded try and start eclipse with the -debug flag on the command line. Now Eclipse will log what plugins/bundles are not being loaded. You can open the Error Log View or look directly in .metadata/log for the information. See also http://wiki.eclipse.org/IRC_FAQ#How_do_I_debug_Eclipse.3F_How_can_I_see_what_plug-ins_are_being_started.3F_Why_aren.27t_the_plug-ins_I_installed_showing_up_in_the_UI.3F_How_do_I_start_the_OSGi_console.3F http://wiki.eclipse.org/IRC_FAQ#How_do_I_debug_Eclipse.3F_How_can_I_see_what_plug-ins_are_being_started.3F_Why_aren.27t_the_plug-ins_I_installed_showing_up_in_the_UI.3F_How_do_I_start_the_OSGi_console.3F *Q : Eclipse is running out of memory OR Eclipse is running very slow!* *A* : Eclipse default setup is to use 64mb of memory and that works ok for small number of projects; but if you have more projects and/or using many plugins Eclipse would like to use more memory and hence its behavior will be slower operations (because of too much garbage collection or simply halting because it runs out of memory). The solution is to start eclipse with a set of flags to allow it to allocate more memory: eclipse -vmargs -Xmx1024m -XX:MaxPermSize=128m The above will allow it to use up to 1Gb of memory (you can of course lower it if you want, but this is what I use ;) and finally it will also increase the MaxPermSize so classloading is given more room. See also http://wiki.eclipse.org/IRC_FAQ#I.27m_having_memory.2C_heap.2C_or_permgen_problems.2C_what_can_I_do.3F http://wiki.eclipse.org/IRC_FAQ#I.27m_having_memory.2C_heap.2C_or_permgen_problems.2C_what_can_I_do.3F *Q: My deployment need to be present when starting up the server, but it looks like my .sar archives are only deployed after the server is running. How do I make sure the server sees it while starting up ?* This is probably because the server adapter is deploying into a metadata location in the workspace and that metadata location is only added as a deployable location via JMX after bootup. You can still make your server deploy to a specific location inside the automatically-added location (aka the deploy folder) by opening the Server Editor (double-click the server) and changing the preferences there. Note: 90% of deployments don't need this but some others do, like some .sar deployments. *Q: Why are Eclipse buttons in dialogs and other places are not working for me on Linux* ? This was a problem in Eclipse 3.5.1. Setting GDK_NATIVE_WINDOWS=true worked around the issue. This bug was fixed in Eclipse 3.5.2 and 3.6.0 (JBoss Tools 3.1 3.2, respectively). See also http://wiki.eclipse.org/IRC_FAQ#Eclipse_buttons_in_dialogs_and_other_places_are_not_working_for_me_if_I_click_them_with_the_mouse._I_also_cannot_see_anything_in_the_tree_when_I_try_to_install_updates._What.27s_going_on.3F http://wiki.eclipse.org/IRC_FAQ#Eclipse_buttons_in_dialogs_and_other_places_are_not_working_for_me_if_I_click_them_with_the_mouse._I_also_cannot_see_anything_in_the_tree_when_I_try_to_install_updates._What.27s_going_on.3F -- Comment by going to Community [https://community.jboss.org/docs/DOC-10801] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Building JBoss Tools Documentation
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Building JBoss Tools Documentation To view the document, visit: https://community.jboss.org/docs/DOC-13341 -- *This document is out of date. See https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/build_documentation.md https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/build_documentation.md* You can download a folder with a plug-in either from a Anonymous SVN (http://anonsvn.jboss.org/repos/jbosstools) or a Committer SVN (https://svn.jboss.org/repos/jbosstools) ( if you have commiter rights) repositories . In the plug-in's folder you will find a directory with documentation.This instruction explains how you can build the documentation. h3. Prerequisites: Ensure you have the Maven building tool Ensure the Nexus repository and profile as defined here: https://community.jboss.org/docs/DOC-15170 http://community.jboss.org/wiki/MavenGettingStarted-Developers are in your *+settings.xml+* file, located in your *%M2_HOME%/conf/* or *%USER_HOME%/.m2/* folder. These settings are required in order to obtain the necessary jDocbook plug-ins that are required to build the JBoss Tools documentation h3. Building Steps So, you checked out the plug-in for which you want to build documentation and the documentation folder. And now you can proceed to building the documentation. 1.Find the +*pom.xml*+ file, that is responsible for building the documentation, in the plug-in folder you downloaded. Normally it’s located in “/docs/reference”. 2.Run *mvn clean install* command in the folder with *+pom.xml+* to start building the documentation. (nightly build docs are build by default) Example: user@user-desktop:/home/user/trunk/seam/docs/reference$ mvn clean install 3.If everything is configured correctly you will see a “BUILD SUCCESSFUL” message. You will also see a generated *+target+* folder that contains the built documentation. Example: To open the HTML version of the “Seam Dev Tools Reference Guide” guide you need to proceed to user@user-desktop:/home/user/trunk/seam/docs/seam/docs/reference/target/docbook/publish/en-US/html_single and open index.html file. h3. Documentation Profiles There are 3 profiles that you can build documentation with: *release* builds release documentation with “new” or “updated” markers next to the corresponding chapters and sections titles *releaseJBDS* builds release documentation with Jboss.com styles for commercial products Remember to redeploy jbosstools-jdocbook-style and jbosstools-docbook-xslt if it have been changed. In order to redeploy you should run 'mvn deploy' from the corresponding directory. You should also have the apropriate credentials to deploy to the http://snapshots.jboss.org/maven2 *diffmk* builds documentation with markers highlighting changes comparing to the previous release version and sets “new” or “updated” markers next to the corresponding chapters and sections titles.*Note:* Please make sure that you have the master_output.xml file (normally the file can be found in \pluginName\docs\reference\en\) as a new guide may not have such file since there's nothing to compare with. This command launches building documentation with a profile. mvn install -Pprofile_name By default, with no profile specified, Nightly Build docs are generated. In order to build all the guide from one place you need to have JBoss Tools trunk checked out then cd to JBoss_tools_trunk/documentation/jbds-docs/ to build JBDS guides with jboss.com styles or to JBoss_tools_trunk/documentation/jboss-tools-docs to build JBoss Tools guides. and run mvn assembly:assembly You can optionally use a profile in this command. mvn assembly:assembly -Pprofile_name -- Comment by going to Community [https://community.jboss.org/docs/DOC-13341] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ *Platforms, Runtimes Technologies* * * The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools JBDS. || Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || EAP (http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/) || SOA-P (http://www.redhat.com/products/jbossenterprisemiddleware/soa/) § (#soapnote) || AS (http://www.jboss.org/jbossas) / WildFly (http://wildfly.org/) || Seam (http://seamframework.org/) || JSF (http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html) || RichFaces (http://www.jboss.org/richfaces) (the latest supported version) || | 4.3/Kepler | 4.1 | 7.0 | 4.3, 5.0, 6.0, 6.1 | 6.0 Beta1+, 5.3, 5.2, 4.x | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0, 8.0 (WildFly) | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 4.2/Juno | 4.0 | 6.0 | 4.3, 5.0, 6.0 | 6.0 Alpha2, 5.3, 5.2, 4.x | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0 | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3, 5.0, 6.0 | 5.3, 5.2, 4.x | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0 | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.x | 4.3, 5.0 | 5.2, 4.x | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2, 2.0 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0 | 4.3, 5.0 | ? | 3.2, 4.0, 4.2, 5.0, 5.1 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2, 2.0 (in VPE) | 3.3.x | | 3.4/Ganymede | 3.0 | 2.1 | 4.3, 5.0 | ? | 3.2, 4.0, 4.2, 5.0 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1 | 4.3 | ? | 3.2, 4.0, 4.2, 5.0 | 1.2, 2.0 | 1.1, 1.2 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0 | 4.2 | ? | 3.2, 4.0, 4.2 | 1.2, 2.0 | 1.1, 1.2 | 3.1.0 | #+§ - SOA-P is based on EAP (https://access.redhat.com/site/articles/111773).+ *Operating Systems JDKs* * * This matrix shows what operating systems and JDKs are supported by Eclipse, JBoss Tools JBDS. || JDKs Supported by Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || Operating System || JDK || Supported? || Includes Visual Page Editor? || | %6% *4.3/Kepler* Win7 RHEL6: JDK 7 or 6 OSX: JDK 7 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_3.xml#target_environments) +*** - Eclipse only supports Win7+ +** - Eclipse only supports OS X 10.8 + | %6% 4.1 | %6% 7.0 | Windows 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 32-bit | 7, 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 64-bit | 7, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *4.2/Juno* Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) +*** - Eclipse.org only tested on Win7 and WinXP + +** - +Eclipse.org only tested on+ OS X 10.6+ | %6% 4.0 | %6% 6.0 | Windows XP, 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows XP, 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *3.7/Indigo* JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) +* - +Eclipse.org only tested on+ OS X 10.6+ | %6% 3.3 | %6% 5.0 | Windows XP or 7, 32-bit | 6, 32-bit | Yes | Yes | | Windows XP or 7, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %5% *3.6/Helios* WinXP and RHEL5
[jboss-user] [JBoss Tools] - JBosstoolsVisualEditorFAQ
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: JBosstoolsVisualEditorFAQ To view the document, visit: https://community.jboss.org/docs/DOC-10862 -- *Q: Which platforms are supported by* *Visual Editor?* *A:* The list of supported platforms (and their IDs): * Windows with Java 32-bit (win32.win32.x86) * Windows with Java 64-bit (win32.win32.x86_64) - Experimental support is available in JBoss Tools 4.1.0.Beta1/2 and JBoss Developer Studio 7.0.0.Beta1/2. To enable it, you need to install XULRunner from this update site:* http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulrunner/ http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulrunner/ (previously http://download.jboss.org/jbosstools/builds/staging/xulrunner-1.9.2_win64/all/repo/ http://download.jboss.org/jbosstools/builds/staging/xulrunner-1.9.2_win64/all/repo/ ) * If you cannot start Eclipse after this installation, you may use –Dorg.jboss.tools.vpe.loadxulrunner=false option as described in the next question. Please comment in https://issues.jboss.org/browse/JBIDE-2720 JBIDE-2720 if something went wrong. * Linux x86 (gtk.linux.x86) * Linux x86-64 (gtk.linux.x86_64) * Mac OS X Cocoa with Java 32-bit (cocoa.macosx.x86) * Mac OS X Carbon with Java 32-bit (carbon.macosx.x86) [not supported by JBoss Tools 3.3.0 and later, JBDS 5.0 and later] In brief, Java 64-bit is supported on Linux only, on all other systems Visual Editor requires Java 32-bit. *Q: Eclipse crashes when I use Visual Editor, what can I do?* *A:* This may happen in JBoss Tools 3.3.0.M2 and above with Eclipse 3.7.0 due to https://issues.jboss.org/browse/JBIDE-9144 the WebKit and XULRunner conflict. You can disable Visual Editor by adding the option –Dorg.jboss.tools.vpe.loadxulrunner=false to the eclipse.ini (or jbdevstudio.ini if you use JBoss Developer Studio). *Q: Visual Editor does not start under Linux* *A:* Linux users may need to do the following to get the visual editor to work correctly on their machines. * The Visual Page Editor (before JBoss Tools 3.1.0.M4) requires the library libstdc++.so.5. This library is contained in the compat-libstdc++-33.i386 package. * To install this package on Fedora Core or Red Hat Enterprise Linux run the following command: yum install compat-libstdc++-33.i386 ** On any other rpm based distributions download libstdc++.so.5 and run the following command: rpm -Uvh compat-libstdc++-33.i386 ** On Debian and Debian based distributions (e.g. Ubuntu) run the following command: apt-get install libstdc++5 * In case you have the library installed and you still have issue with starting the visual page editor then close all browser views/editors and leave one visual page editor open and restart eclipse. This should force a load of the right XULRunner viewer. *Q: Visual Editor doesn't start at any platform and shows message 'The VPE editor can't be run because your system environment needs to be changed slightly'* *A:* Check if you version of JBoss Developer Studio/JBoss Tools is compatible with you version of Eclipse, see the compatibility matrix https://community.jboss.org/docs/DOC-14297 http://www.jboss.org/community/wiki/MatrixofsupportedplatformsruntimesandtechnologiesinJBossToolsJBDS *Q: Visual Editor starts OK, but the following message dialog appears:* https://community.jboss.org/servlet/JiveServlet/showImage/102-10862-52-1955/messageNaturesInfo.PNG https://community.jboss.org/servlet/JiveServlet/downloadImage/102-10862-52-1955/310-120/messageNaturesInfo.PNG *A:* Some functionality of Visual Editor may not work if a project doesn't have org.jboss.tools.jsf.jsfnature or org.jboss.tools.jst.web.kb.kbnature in .project configuration. To fix this problem and turn off the message box execute next steps: * Right mouse button click on a project in Package Explorer. * Select +Configure - Add JSF Capabilities+ from the context menu. * Configure your project using +Add JSF Capabilities+ wizard and press Finish. *P.S.* If you are sure that your project does not need JSF capabilities, just disable this message box by checking +Do not show this dialog again!+ checkbox. *Q: Visual Part doesn't start and XPCOM error -2147467259 is shown* *A:* Something bad happened with buildin xulrunner. To check it you should: * Go to Eclipse - Help - About - Installation Details... - Configuration * find +org.eclipse.swt.browser.XULRunnerPath+ and open this path in terminal * try xulrunner.exe -version or ./xulrunner -version and it should show what is needed for XR to work -- Comment by going to Community [https://community.jboss.org/docs/DOC-10862] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128
Re: [jboss-user] [JBoss Tools] - JBosstoolsVisualEditorFAQ
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on the document JBosstoolsVisualEditorFAQ To view all comments on this document, visit: https://community.jboss.org/docs/DOC-10862#comment-12373 -- I've posted the staging content to a more stable integration URL here: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulrunner/ http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulrunner/ Doesn't mean it's any less experimental, just less likely to be accidentally deleted. :D -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Re: Beta1 cannot off-line install with Kepler RC2
Nick Boldt [https://community.jboss.org/people/nickboldt] created the discussion Re: Beta1 cannot off-line install with Kepler RC2 To view the discussion, visit: https://community.jboss.org/message/821726#821726 -- As you discovered, there are some things required by JBoss Tools which must be sourced from the internet - they're not included in the update site. We don't re-distribute org.eclipse.* stuff, but we DO mirror it as part of our target platform provisioning. Thus, the TP used by JBoss Tools 4.1.0.Beta1 (and JBoss Developer Studio 7.0.0.Beta1, too) contains both httpclient and httpclient4, as that's what's in the matching Kepler site from which we mirrored. -- If you want a completely offline way to get JBoss Tools, try JBoss Developer Studio, which ships as an installer jar. That jar (which can also be used as an update site), allows two ways to install JBT without needing an internet connection. The latest JBDS 7 is here: https://devstudio.jboss.com/earlyaccess/7.0/ https://devstudio.jboss.com/earlyaccess/7.0/ -- Reply to this message by going to Community [https://community.jboss.org/message/821726#821726] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ *Platforms, Runtimes Technologies* * * The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools JBDS. || Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || EAP (http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/) || AS (http://www.jboss.org/jbossas) / WildFly (http://wildfly.org/) || Seam (http://seamframework.org/) || JSF (http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html) || RichFaces (http://www.jboss.org/richfaces) (the latest supported version) || | 4.3/Kepler | 4.1 | 7.0 | 4.3, 5.0, 6.0, 6.1 | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0, 8.0 (WildFly) | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 4.2/Juno | 4.0 | 6.0 | 4.3, 5.0, 6.0 | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0 | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3, 5.0, 6.0 | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0, 7.0 | 1.2, 2.0, 2.1, 2.2, 2.3 | 1.1, 1.2, 2.0 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.x | 4.3, 5.0 | 3.2, 4.0, 4.2, 5.0, 5.1, 6.0 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2, 2.0 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0 | 4.3, 5.0 | 3.2, 4.0, 4.2, 5.0, 5.1 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2, 2.0 (in VPE) | 3.3.x | | 3.4/Ganymede | 3.0 | 2.1 | 4.3, 5.0 | 3.2, 4.0, 4.2, 5.0 | 1.2, 2.0, 2.1, 2.2 | 1.1, 1.2 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1 | 4.3 | 3.2, 4.0, 4.2, 5.0 | 1.2, 2.0 | 1.1, 1.2 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0 | 4.2 | 3.2, 4.0, 4.2 | 1.2, 2.0 | 1.1, 1.2 | 3.1.0 | *Operating Systems JDKs* * * This matrix shows what operating systems and JDKs are supported by Eclipse, JBoss Tools JBDS. || JDKs Supported by Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || Operating System || JDK || Supported? || Includes Visual Page Editor? || | %6% *4.3/Kepler* Win7 RHEL6: JDK 7 or 6 OSX: JDK 7 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_3.xml#target_environments) +*** - Eclipse only supports Win7+ +** - Eclipse only supports OS X 10.8 + | %6% 4.1 | %6% 7.0 | Windows 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 32-bit | 7, 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 64-bit | 7, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *4.2/Juno* Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) +*** - Eclipse.org only tested on Win7 and WinXP + +** - +Eclipse.org only tested on+ OS X 10.6+ | %6% 4.0 | %6% 6.0 | Windows XP, 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows XP, 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *3.7/Indigo* JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) +* - +Eclipse.org only tested on+ OS X 10.6+ | %6% 3.3 | %6% 5.0 | Windows XP or 7, 32-bit | 6, 32-bit | Yes | Yes | | Windows XP or 7, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %5% *3.6/Helios* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | %5% 3.2 | %5% 4.x | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes
[jboss-user] [JBoss Tools] - Re: JBOSS Tools and eclipse versions
Nick Boldt [https://community.jboss.org/people/nickboldt] created the discussion Re: JBOSS Tools and eclipse versions To view the discussion, visit: https://community.jboss.org/message/800195#800195 -- See table of compatible versions here: https://community.jboss.org/docs/DOC-14297 https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTechnologiesInJBossToolsJBDS -- Reply to this message by going to Community [https://community.jboss.org/message/800195#800195] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Tagging/branching of JBoss Tools Core subcomponents
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Tagging/branching of JBoss Tools Core subcomponents To view the document, visit: https://community.jboss.org/docs/DOC-48350 -- Our recent move to git caused some confusion on how we tag/branch components in JBoss Tools core components. h1. Current Tag/Branching strategy To avoid future confusion here are the short version of the current approach: 1. Each component has its own version in manifest.mf/pom.xml/feature.xml* This can be set quickly using mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.3-SNAPSHOT 2. The git repositories should use tag/branches based on jbosstools version:* Branches: jbosstools-version*x* (x used to differentiate a branch from a tag)* *Tags: jbosstools-version (no x suffix) 3. In Jira use the jbosstools version for reporting/targeting issues. The advantage of the above is that git jira use the same version. i.e. with a unified tag like jbosstools-4.1.0.Alpha1 you can find which version is used of a specific component for a specific jboss tools release easily. This means from git you always know which branch/tag to checkout for a component to get matching version to a specific jboss tools core build/release. With Jira we would need to introduce a project for each individual component since Jira does not support version per components and thus jira queries for knowing current status of JBIDE suddenly gets very complex. h1. Discussion about improvements/future tagging can be found https://community.jboss.org/docs/DOC-48351 https://community.jboss.org/wiki/FutureStrategyForTaggingJBossToolsCore -- Comment by going to Community [https://community.jboss.org/docs/DOC-48350] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - JBossToolsFAQ
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: JBossToolsFAQ To view the document, visit: https://community.jboss.org/docs/DOC-10796 -- General FAQs * https://community.jboss.org/docs/DOC-10797 JBoss Tools FAQ * https://community.jboss.org/docs/DOC-11753 JBoss Developer Studio FAQ * https://community.jboss.org/docs/DOC-10801 TroubleShooting * https://community.jboss.org/docs/DOC-14297 Matrix of supported platforms, runtimes and technologies in JBoss Tools/JBDS Installation * http://www.jboss.org/tools/download/installation.html JBoss Tools Installation Guide (see also https://community.jboss.org/docs/DOC-10044 Installing JBoss Tools) * https://community.jboss.org/docs/DOC-11754 JBoss Developer Studio Installation FAQ Feature FAQs * https://community.jboss.org/docs/DOC-18100 BrowserSim * https://community.jboss.org/docs/DOC-10862 Visual Editor Building and Testing * https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 Building JBoss Tools (Using Tycho//Maven to Build) * http://www.jboss.org/tools/docs/testing.html Testing JBoss Tools (Using PDE Debugger w/ a Tycho/Maven Build) -- Comment by going to Community [https://community.jboss.org/docs/DOC-10796] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ *Platforms, Runtimes Technologies* * * The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools JBDS. || Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || EAP (http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/) || AS (http://www.jboss.org/jbossas) || Seam (http://seamframework.org/) || JSF (http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html) || RichFaces (http://www.jboss.org/richfaces) (the latest supported version) || | 4.3/Kepler | 4.1 | 7.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0 , 1.2, 1.1 | 3.3.x, 4.0.x | | 4.2/Juno | 4.0 | 6.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0 , 1.2, 1.1 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.x | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | | 3.4/Ganymede | 3.0 | 2.1 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | *Operating Systems JDKs* * * This matrix shows what operating systems and JDKs are supported by Eclipse, JBoss Tools JBDS. || JDKs Supported by Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || Operating System || JDK || Supported? || Includes Visual Page Editor? || | %6% *4.3/Kepler* Win7 RHEL6: JDK 7 or 6 OSX: JDK 7 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_3.xml#target_environments) +*** - Eclipse only supports Win7+ +** - Eclipse only supports OS X 10.8 + | %6% 4.1 | %6% 7.0 | Windows 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 32-bit | 7, 32-bit | Yes | Yes | | OSX 10.8** Cocoa, 64-bit | 7, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *4.2/Juno* Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) +*** - Eclipse only supports Win7 and WinXP + +** - Eclipse only supports OS X 10.6+ | %6% 4.0 | %6% 6.0 | Windows XP, 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows XP, 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *3.7/Indigo* JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) +* - Eclipse only supports OS X 10.6+ | %6% 3.3 | %6% 5.0 | Windows XP or 7, 32-bit | 6, 32-bit | Yes | Yes | | Windows XP or 7, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %5% *3.6/Helios* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | %5% 3.2 | %5% 4.x | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit
Re: [jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on the document Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view all comments on this document, visit: https://community.jboss.org/docs/DOC-14297#comment-11398 -- Added link to Eclipse 4.3/Kepler's project plan w/ stated reference platforms/JDKs which they support. Assuming that since they don't support OSX 10.6 or 10.7 we're dropping support too. -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - What's In JBoss Tools / JBoss Developer Studio?
Nick Boldt [https://community.jboss.org/people/nickboldt] created the document: What's In JBoss Tools / JBoss Developer Studio? To view the document, visit: https://community.jboss.org/docs/DOC-48112 -- | | | Project | Version | TP | Central | | | Notes | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Juno SR0 | 201206270900-R | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Juno SR1 | 201209280900-R | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | BIRT | 4.2.0.v20120613 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | BIRT | 4.2.1.v20120912 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Eclipse | R-4.2-201206081400 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Eclipse | R-4.2.1-201209141800 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | WebTools | R-3.4.0-20120612174739 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | WebTools | R-3.4.1-20120917174803 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | m2e | 20120926-1337 | Y | | | | m2e/1.2.0.20120903-1050, m2e-wtp/0.16, m2e-apt/1.0.1-2012-09-20_03-20-41-H23, m2e-jdt-compiler/1.0.1-2012-09-20_05-03-18-H2, m2eclipse-buildhelper/0.15.0.201207090124, m2e-wro4j/1.0.1-2012-09-20_04-53-27-H4, m2e-extras/0.15.0.201206251206 | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Orbit | R20120526062928 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | SWTBot | 2.0.5 | Y | | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Atlassian | 3.0.6.v20120628 | Y | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | GWT | 3.1.0.v201208080121-rel-r42 | Y | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Eclipse Checkstyle | 5.6.0.201209221626 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | SR1 | FindBugs | 2.0.2.20121121 | | Y | | | | | JBoss Tools 4.0.1 / JBDS 6.0.1 | SR1a | FindBugs | 2.0.2.20121210 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | PMD | 3.2.6 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | SpringIDE | 2.7.2.201109122348 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | Subclipse | 1.8.16_1.7.5.v1 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | TestNG | 6.7.0.20120825_1316 | | Y | | | | | JBoss Tools 4.0.0 / JBDS 6.0.0 | | XulRunner | 1.9.216.Final-v20121126-2356-B155 | NO | NO | | | | | | | Project | Version | Reqs Mirror | Extras / Central | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Indigo SR2 | 201202240900-SR2 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | BIRT | 3.7.2.v20120214 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | BPMN2 Modeler | 201202231559 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | ECF | 3.5.4 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Eclipse | 3.7.2-201202080800 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | EGit | 1.2.0.201112131611 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | EMF | 2.7.2.v20120130-0943 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | GWT | 2.5.0.v201201120043-rel-r37 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | m2e | 20120531-1100 | Y | | | | m2e/1.0.100.20110804-1717, m2e-wtp/0.15.2.20120306-2040, m2e-apt/1.0.0.201205151950, m2e-jdt-compiler/1.0.0.20120208-1640, m2eclipse-buildhelper/0.15.0.201109290002, m2e archiver/0.15.0.201109290002 | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | m2e-apt | 1.0.0-2012-06-05_16-15-59-H16 | Y | | | | m2e-apt/1.0.0-2012-06-05_16-15-59-H16 | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | mylyn | 3.6.5.v20120215-0100 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Orbit | R20120119162704 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | SWTBot | 2.0.5 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | WebTools | 3.3.2-20120210195245 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | XulRunner | 1.9.2 | Y | | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Eclipse Checkstyle | 5.4.0.20110911 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | FindBugs | 1.3.9 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | SR1 | PMD | 3.2.4 | | Y | | | | | JBoss Tools 3.3.2 / JBDS 5.0.2 | SR1a | PMD | 3.2.6 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | SpringIDE | 2.7.2.201109122348 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Subclipse | 1.6_1.3 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | Subversive | 0.7.9_2.2.2_1.3 | | Y | | | | | JBoss Tools 3.3.1 / JBDS 5.0.1 | | TestNG | 6.1.1.20110823_1537 | | Y | | | | | | | Project | Version | Reqs Mirror | Extras | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | Helios SR2 | SR2 | Y | | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | BIRT | 2.6.2 | Y | | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | ECF | 3.4 | Y | | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | Eclipse | 3.6 | Y | | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | EMF | 2.6 | Y | | | | | | JBoss Tools 3.2.2 / JBDS 4.1.2 | | GWT
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools JBDS. || Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || EAP (http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/) || AS (http://www.jboss.org/jbossas) || Seam (http://seamframework.org/) || JSF (http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html) || RichFaces (http://www.jboss.org/richfaces) (the latest supported version) || | 4.2/Juno | 4.0 | 6.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0 , 1.2, 1.1 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.x | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | | 3.4/Ganymede | 3.0 | 2.1 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | This matrix shows what operating systems and JDKs are supported by Eclipse, JBoss Tools JBDS. || JDKs Supported by Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || Operating System || JDK || Supported? || Includes Visual Page Editor? || | %6% *4.2/Juno* Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) +*** - Eclipse only supports Win7 and WinXP + +** - Eclipse only supports OS X 10.6+ | %6% 4.0 | %6% 6.0 | Windows XP or 7 or 8***, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows XP or 7 or 8***, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.8** Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *3.7/Indigo* JDK 6 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) +* - Eclipse only supports OS X 10.6+ | %6% 3.3 | %6% 5.0 | Windows XP or 7, 32-bit | 6, 32-bit | Yes | Yes | | Windows XP or 7, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 - 10.7* Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %5% *3.6/Helios* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | %5% 3.2 | %5% 4.x | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 64-bit | 5, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %4% *3.5/Galileo* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5.xml#target_environments) | %4% 3.1 | %4% 3.0 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 Carbon or Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | %1,7% | | %4% *3.4/Ganymede* WinXP: JDK 6 or 5 Others: JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_4.html?view=corevision=1.3root=Eclipse_Website#TargetOperatingEnvironments) | %4% 3.0 | %4
Re: [jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on the document Matrix of supported platforms, runtimes and technologies in JBossTools JBDS To view all comments on this document, visit: https://community.jboss.org/docs/DOC-14297#comment-11293 -- For details regarding target platforms, requirement mirrors, or the contents of JBoss Central / Extras, see this spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AmGcQy-AtllqdG9XWEYxaldRTnZMVDA5bXprTndPbEE https://docs.google.com/spreadsheet/ccc?key=0AmGcQy-AtllqdG9XWEYxaldRTnZMVDA5bXprTndPbEE -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - It's Beta Time for JBoss Tools and Developer Studio
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the blog post: It's Beta Time for JBoss Tools and Developer Studio To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time-for-jboss-tools-and-developer-studio -- It's Beta time for JBoss Tools 4 and JBoss Developer Studio 6! https://community.jboss.org/servlet/JiveServlet/showImage/38-4854-18193/jbosstolsdevstudio.png https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4854-18193/jbosstolsdevstudio.png h4. Beta 1 Developer Studio: [ https://marketplace.eclipse.org/node/503834 Marketplace] [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ https://marketplace.eclipse.org/node/420896 Marketplace] [ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development/juno/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bbop=viewforumf=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter] JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution. JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation. If you are into doing your own bleeding edge eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that Just Works then JBoss Developer Studio is the way to go. h2. Installation +JBoss Developer Studio+ comes with everything pre-bundled in its installer. Simply http://devstudio.jboss.com/earlyaccess download it from our early access site and run it like this: java -jar jbdevstudio-installername.jar *Note:* if you are on Windows or Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory. +JBoss Tools+ requires a bit more: http://marketplace.eclipse.org/marketplace-client-intro?mpc_install=420896 https://devstudio.jboss.com/images/jbosstools-marketplace-download-now.png This release requires at least Eclipse 4.2 but we recommend using the http://www.eclipse.org/downloads/packages/release/juno/sr1 Eclipse 4.2 JEE Bundle since then you get most of the dependencies preinstalled. Once you have installed Eclipse, you either find us on https://marketplace.eclipse.org/node/420896 Eclipse Marketplace under JBoss Tools (Juno) or use our update site directly. The update site URL to use from Help Install New Software... is: http://download.jboss.org/jbosstools/updates/stable/juno/ http://download.jboss.org/jbosstools/updates/development/juno/ Note: SOA tooling for BPEL, Drools, Guvnor, jBPM, ESB, Modeshape, pi4soa, Savara, SwitchYard Teiid are no longer included in the JBoss Tools release. They will become available separately later. h2. Bring Your Own Eclipse This beta introduces JBoss Developer Studio BYOE (Bring Your Own Eclipse) which allow you to install the plugins provided and supported in JBoss Developer Studio to your own existing Eclipse installation from https://marketplace.eclipse.org/node/503834 Eclipse Marketplace. If unavailable soon from Help Eclipse Marketplace..., simply click the link above to browse the Marketplace entry, then drag the link there into your Eclipse. We are eager to hear how this BYOE option work for you and do please let us know ASAP if you spot issues with this new and more flexible way of installing Developer Studio! Thank you! h2. Multiple OpenShift Servers OpenShift now allows you to connect to multiple OpenShift servers, i.e. your own Origin server as well as hosted openshift. h2. And more... See the full list of changes in Alpha1, Alpha2 and now Beta1 at the http://docs.jboss.org/tools/whatsnew/ What's New and Noteworthy and of course a good bunch of bug fixes and adjustments for running well in Eclipse 4.2/Juno. Have fun! -- Comment by going to Community [https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time-for-jboss-tools-and-developer-studio] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - It's Beta Time for JBoss Tools and Developer Studio
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on It's Beta Time for JBoss Tools and Developer Studio To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time-for-jboss-tools-and-developer-studio#comment-11060 -- Eclipse Marketplace entry added above. Direct link: http://marketplace.eclipse.org/node/503834 http://marketplace.eclipse.org/node/503834 -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - It's Beta Time for JBoss Tools and Developer Studio
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on It's Beta Time for JBoss Tools and Developer Studio To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time-for-jboss-tools-and-developer-studio#comment-11061 -- Eclipse 4.2 is recommended. Is there a reason why you need to use 3.8 instead of 4.2? Personal preference or technical requirement? -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - It's Beta Time for JBoss Tools and Developer Studio
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on It's Beta Time for JBoss Tools and Developer Studio To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time-for-jboss-tools-and-developer-studio#comment-11042 -- AFAIK, Eclipse 3.8 doesn't really include UI, it's just the RCP underlayer. If you want an IDE, you should be using 4.2. Grab this: http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/junosr1 http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/junosr1 and you'll have everything you need to run JBoss Tools 4 or JBDS 6. -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - JBoss Tools 4 Alpha 2 - Stacks, OpenShift SSH, Hibernate Tools, Forge Debug and more...
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on JBoss Tools 4 Alpha 2 - Stacks, OpenShift SSH, Hibernate Tools, Forge Debug and more... To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/10/09/jboss-tools-4-alpha-2#comment-10942 -- Cannot reproduce. When I fire up Eclipse Juno SR1, and add the URL above, I get this: https://community.jboss.org/servlet/JiveServlet/showImage/105-10942-19724/eclipsejunosr1-jbosstools4alpha2.png https://community.jboss.org/servlet/JiveServlet/downloadImage/105-10942-19724/310-231/eclipsejunosr1-jbosstools4alpha2.png What JDK are you using with Eclipse? Is it 64-bit or 32-bit? Needs to be the same as the version of Eclipse you're using. And must be JDK 6 or 7 - if you're using 5 or earlier, that could be the problem. -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - JBoss Tools 4 Alpha 2 - Stacks, OpenShift SSH, Hibernate Tools, Forge Debug and more...
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on JBoss Tools 4 Alpha 2 - Stacks, OpenShift SSH, Hibernate Tools, Forge Debug and more... To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/10/09/jboss-tools-4-alpha-2#comment-10943 -- Also works when I load up the zip: https://community.jboss.org/servlet/JiveServlet/showImage/105-10943-19725/eclipsejunosr1-jbosstools4alpha2fromzip.png https://community.jboss.org/servlet/JiveServlet/downloadImage/105-10943-19725/310-198/eclipsejunosr1-jbosstools4alpha2fromzip.png -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Re: Problem updating tools in Eclipse
Nick Boldt [https://community.jboss.org/people/nickboldt] created the discussion Re: Problem updating tools in Eclipse To view the discussion, visit: https://community.jboss.org/message/764389#764389 -- When you select the discovery feature, the description states: *JBoss Central Discovery - do not install this feature; instead, it will be discovered and used with JBoss Central.* For future, we'll look at removing the feature entirely to avoid it being accidentally installed. https://issues.jboss.org/browse/JBIDE-12389 https://issues.jboss.org/browse/JBIDE-12389 -- Reply to this message by going to Community [https://community.jboss.org/message/764389#764389] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on the document Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2 To view all comments on this document, visit: https://community.jboss.org/docs/DOC-28772#comment-10738 -- Duplicated by https://community.jboss.org/message/758399#758399#758399 https://community.jboss.org/message/758399#758399 -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - Coping with versions in large multi-module osgi projects
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on Coping with versions in large multi-module osgi projects To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2011/09/17/coping-with-versions-in-large-multi-module-osgi-projects#comment-10717 -- Seems as though these no longer work -- at least for upversioning the jbpm plugins/features/tests in trunk, that is. mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=version and mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=version Thought it was related to having versionx.y.z-SNAPSHOT/version in pom.xml files rather than inheriting this value from parent, or that they'd changed something between 0.15.0 and 0.16.0-SNAPSHOT, but I can't for the life of me figure out why manifest.mf and feature.xml files aren't being automatically updated. -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Re: JBoss Tools 4 Alpha 1 - doesn't install
Nick Boldt [https://community.jboss.org/people/nickboldt] created the discussion Re: JBoss Tools 4 Alpha 1 - doesn't install To view the discussion, visit: https://community.jboss.org/message/760204#760204 -- Sorry gang, that was my fault. Forgot to update 2 composite*.xml files when I was publishing the bits. So... the site worked (pointing at Alpha1b) until I did the usual rename from Alpha1b to Alpha1, and works again when I realized I'd forgotten to ALSO update the metadata in http://download.jboss.org/jbosstools/updates/development/juno/ http://download.jboss.org/jbosstools/updates/development/juno/ to ALSO point at the Alpha1 (not Alpha1b) bits. Mea culpa. -- Reply to this message by going to Community [https://community.jboss.org/message/760204#760204] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools/JBDS. || Eclipse || JBoss Tools || JBDS || EAP || AS || Seam || JSF || RichFaces (the latest supported version) || | 4.2/Juno | 4.0 | 6.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0 , 1.2, 1.1 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.0.0/4.1.0 | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | | 3.4.2/Ganymede | 3.0 | 2.1.0 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1.0 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | This matrix shows what operating systems and JDKs are supported by JBoss Tools / JBDS. || JBoss Tools || Operating System || JDK || Supported? || Includes Visual Page Editor? || JDK(s) Supported by IDE || | %6% 4.0 | Windows 7 or XP, 32-bit | 7 or 6, 32-bit | Yes | Yes | %6% Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) | | Windows 7 or XP, 64-bit | 7 or 6, 64- or 32-bit | Yes | * - using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6, 64-bit | 6, 64- or 32-bit | Yes | * - using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %6% 3.3 | Windows 7 or XP, 32-bit | 6, 32-bit | Yes | Yes | %6% JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) | | Windows 7 or XP, 64-bit | 6, 64- or 32-bit | Yes | * - using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 Cocoa, 64-bit | 6, 64- or 32-bit | Yes | * - using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %5% 3.2 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | %5% WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 64-bit | 5, 64- or 32-bit | Yes | * - using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %4% 3.1 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | %4% WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5.xml#target_environments) | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 Carbon or Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | %4% 3.0 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | %4% WinXP: JDK 6 or 5 Others: JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_4.html?view=corevision=1.3root=Eclipse_Website#TargetOperatingEnvironments) | | Linux, 32-bit | 5, 32-bit | Yes | Yes | | Linux, 64-bit | 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 Carbon, 32-bit | 5, 32-bit | Yes | Yes | | %4% 2.x | Windows 7 32-bit | 5, 32-bit | Yes | Yes | %4% JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_3.html?view=coroot=Eclipse_Website#TargetOperatingEnvironments) | | Linux, 32-bit | 5, 32-bit | Yes | Yes | | Linux, 64-bit | 5, 64- or 32-bit | Yes | Yes | | OSX 10.4 Carbon, 32-bit | 5, 32-bit | Yes | Yes | -- Comment by going to Community [https://community.jboss.org/docs/DOC-14297] Create a new document in JBoss Tools at Community [https://community.jboss.org
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- +Note: this page is as up to date accurate as possible, but is subject to change.+ The following matrix shows what versions of platforms, runtimes and technologies are supported by JBoss Tools JBDS. || Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || EAP (http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/) || AS (http://www.jboss.org/jbossas) || Seam (http://seamframework.org/) || JSF (http://www.oracle.com/technetwork/java/javaee/javaserverfaces-139869.html) || RichFaces (http://www.jboss.org/richfaces) (the latest supported version) || | 4.2/Juno | 4.0 | 6.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0 , 1.2, 1.1 | 3.3.x, 4.0.x | | 3.7/Indigo | 3.3 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.3, 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x, 4.0.x | | 3.6/Helios | 3.2 | 4.x | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0, 1.2, 1.1 | 3.3.x | | 3.5/Galileo | 3.1 | 3.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | | 3.4/Ganymede | 3.0 | 2.1 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | | 3.3.2/Europa | 2.1.2 | 1.1 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | | 3.3.1.1/Europa | 2.0.1 | 1.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | This matrix shows what operating systems and JDKs are supported by Eclipse, JBoss Tools JBDS. || JDKs Supported by Eclipse (http://www.eclipse.org/downloads/) || JBoss Tools (http://www.jboss.org/tools) || JBDS (https://devstudio.jboss.com) || Operating System || JDK || Supported? || Includes Visual Page Editor? || | %6% *4.2/Juno* Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) | %6% 4.0 | %6% 6.0 | Windows 7 or XP, 32-bit | 7 or 6, 32-bit | Yes | Yes | | Windows 7 or XP, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 7 or 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 7 or 6, 64- or 32-bit | Yes | Yes | | OSX 10.6, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %6% *3.7/Indigo* JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) | %6% 3.3 | %6% 5.0 | Windows 7 or XP, 32-bit | 6, 32-bit | Yes | Yes | | Windows 7 or XP, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only | | RHEL6 or Fedora, 32-bit | 6, 32-bit | Yes | Yes | | RHEL6 or Fedora, 64-bit | 6, 64- or 32-bit | Yes | Yes | | OSX 10.6 Cocoa, 32-bit | 6, 32-bit | Yes | Yes | | OSX 10.6 Cocoa, 64-bit | 6, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %5% *3.6/Helios* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | %5% 3.2 | %5% 4.x | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | OSX 10.5 or 10.6 Cocoa, 64-bit | 5, 64- or 32-bit | Yes | Yes, using 32-bit JDK only - Details (https://issues.jboss.org/browse/JBDS-943) | | %1,7% | | %4% *3.5/Galileo* WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5.xml#target_environments) | %4% 3.1 | %4% 3.0 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 32-bit | 6 or 5, 32-bit | Yes | Yes | | RHEL5 or Fedora, 64-bit | 6 or 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 Carbon or Cocoa, 32-bit | 5, 32-bit | Yes | Yes | | %1,7% | | %4% *3.4/Ganymede* WinXP: JDK 6 or 5 Others: JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_4.html?view=corevision=1.3root=Eclipse_Website#TargetOperatingEnvironments) | %4% 3.0 | %4% 2.1 | Windows XP 32-bit | 6 or 5, 32-bit | Yes | Yes | | Linux, 32-bit | 5, 32-bit | Yes | Yes | | Linux, 64-bit | 5, 64- or 32-bit | Yes | Yes | | OSX 10.5 Carbon, 32-bit | 5
Re: [jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] commented on the document Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS To view all comments on this document, visit: https://community.jboss.org/docs/DOC-14297#comment-10568 -- See https://www.jboss.org/tools/download/installation/update_3_4 https://www.jboss.org/tools/download/installation/update_3_4 -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- h2. *This matrix is currently out of date, do not rely on it!* The following matrix explains what versions of platforms, runtimes and technologies are supported by what versions of JBoss Tools/JBDS. || Eclipse || JBoss Tools || JBDS || EAP || AS || Seam || JSF || RichFaces (the latest supported version) || JDK(s) Supported by IDE *(not runtimes)* || | 4.2/Juno | 4.0.0 | 6.0 | ? | ? | | | | Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) | | 3.7/Indigo | 3.3.0 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | | | | JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) | | 3.6/Helios | 3.2.0 | 4.0.0/4.1.0 | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | | | | WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | | 3.5/Galileo | 3.1.0 | 3.0.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5.xml#target_environments) | | 3.4.2/Ganymede | 3.0.x | 2.1.0 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | WinXP: JDK 6 or 5 Others: JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_4.html?view=corevision=1.3root=Eclipse_Website#TargetOperatingEnvironments) | | 3.3.2/Europa | 2.1.2 | 1.1.0 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_3.html?view=coroot=Eclipse_Website#TargetOperatingEnvironments) | | 3.3.1.1/Europa | 2.0.1 | 1.0.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_3.html?view=coroot=Eclipse_Website#TargetOperatingEnvironments) | -- Comment by going to Community [https://community.jboss.org/docs/DOC-14297] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS To view the document, visit: https://community.jboss.org/docs/DOC-14297 -- h2. *This matrix is currently out of date, do not rely on it!* The following matrix explains what versions of platforms, runtimes and technologies are supported by what versions of JBoss Tools/JBDS. || Eclipse || JBoss Tools || JBDS || EAP || AS || Seam || JSF || RichFaces (the latest supported version) || Supported JDK || | 4.2/Juno | 4.0.0 | 6.0 | ? | ? | | | | Win7, WinXP RHEL6: JDK 7 or 6 Others: JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#target_environments) | | 3.7/Indigo | 3.3.0 | 5.0 | 4.3,5.0,6.0 | 7.0,6.0,5.1, 5.0, 4.2, 4.0, 3.2 | | | | JDK 6 only - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments) | | 3.6/Helios | 3.2.0 | 4.0.0/4.1.0 | 4.3,5.0 | 6.0,5.1, 5.0, 4.2, 4.0, 3.2 | | | | WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments) | | 3.5/Galileo | 3.1.0 | 3.0.0 | 4.3, 5.0 | 5.1, 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 2.0 (in VPE), 1.2, 1.1 | 3.3.x | WinXP and RHEL5: JDK 6 or 5 Others: JDK5 - Details (http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5.xml#target_environments) | | 3.4.2/Ganymede | 3.0.x | 2.1.0 | 4.3, 5.0 | 5.0, 4.2, 4.0, 3.2 | 2.2, 2.1, 2.0, 1.2 | 1.2, 1.1 | 3.3.1 | WinXP: JDK 6 or 5 Others: JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_4.html?view=corevision=1.3root=Eclipse_Website#TargetOperatingEnvironments) | | 3.3.2/Europa | 2.1.2 | 1.1.0 | 4.3 | 5.0, 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.3.0 | JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_3.html?view=coroot=Eclipse_Website#TargetOperatingEnvironments) | | 3.3.1.1/Europa | 2.0.1 | 1.0.0 | 4.2 | 4.2, 4.0, 3.2 | 2.0, 1.2 | 1.2, 1.1 | 3.1.0 | JDK 5 - Details (http://dev.eclipse.org/viewcvs/viewvc.cgi/www/eclipse/development/eclipse_project_plan_3_3.html?view=coroot=Eclipse_Website#TargetOperatingEnvironments) | -- Comment by going to Community [https://community.jboss.org/docs/DOC-14297] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Building JBoss Tools Documentation
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: Building JBoss Tools Documentation To view the document, visit: https://community.jboss.org/docs/DOC-13341 -- You can download a folder with a plug-in either from a Anonymous SVN (http://anonsvn.jboss.org/repos/jbosstools) or a Committer SVN (https://svn.jboss.org/repos/jbosstools) ( if you have commiter rights) repositories . In the plug-in's folder you will find a directory with documentation.This instruction explains how you can build the documentation. h3. Prerequisites: Ensure you have the Maven building tool Ensure the Nexus repository and profile as defined here: https://community.jboss.org/docs/DOC-15170 http://community.jboss.org/wiki/MavenGettingStarted-Developers are in your *+settings.xml+* file, located in your *%M2_HOME%/conf/* or *%USER_HOME%/.m2/* folder. These settings are required in order to obtain the necessary jDocbook plug-ins that are required to build the JBoss Tools documentation h3. Building Steps So, you checked out the plug-in for which you want to build documentation and the documentation folder. And now you can proceed to building the documentation. 1.Find the +*pom.xml*+ file, that is responsible for building the documentation, in the plug-in folder you downloaded. Normally it’s located in “/docs/reference”. 2.Run *mvn clean install* command in the folder with *+pom.xml+* to start building the documentation. (nightly build docs are build by default) Example: user@user-desktop:/home/user/trunk/seam/docs/reference$ mvn clean install 3.If everything is configured correctly you will see a “BUILD SUCCESSFUL” message. You will also see a generated *+target+* folder that contains the built documentation. Example: To open the HTML version of the “Seam Dev Tools Reference Guide” guide you need to proceed to user@user-desktop:/home/user/trunk/seam/docs/seam/docs/reference/target/docbook/publish/en-US/html_single and open index.html file. h3. Documentation Profiles There are 3 profiles that you can build documentation with: *release* builds release documentation with “new” or “updated” markers next to the corresponding chapters and sections titles *releaseJBDS* builds release documentation with Jboss.com styles for commercial products Remember to redeploy jbosstools-jdocbook-style and jbosstools-docbook-xslt if it have been changed. In order to redeploy you should run 'mvn deploy' from the corresponding directory. You should also have the apropriate credentials to deploy to the http://snapshots.jboss.org/maven2 *diffmk* builds documentation with markers highlighting changes comparing to the previous release version and sets “new” or “updated” markers next to the corresponding chapters and sections titles.*Note:* Please make sure that you have the master_output.xml file (normally the file can be found in \pluginName\docs\reference\en\) as a new guide may not have such file since there's nothing to compare with. This command launches building documentation with a profile. mvn install -Pprofile_name By default, with no profile specified, Nightly Build docs are generated. In order to build all the guide from one place you need to have JBoss Tools trunk checked out then cd to JBoss_tools_trunk/documentation/jbds-docs/ to build JBDS guides with jboss.com styles or to JBoss_tools_trunk/documentation/jboss-tools-docs to build JBoss Tools guides. and run mvn assembly:assembly You can optionally use a profile in this command. mvn assembly:assembly -Pprofile_name -- Comment by going to Community [https://community.jboss.org/docs/DOC-13341] Create a new document in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - JBoss Tools and Developer Studio Candidate Release
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the blog post: JBoss Tools and Developer Studio Candidate Release To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/06/12/jboss-tools-and-developer-studio-candidate-release -- The release candidate of JBoss Tools and Developer Studio is now available - mainly with bugfixes but also a few nice improvements for AS 7, OpenShift and Maven integration. https://community.jboss.org/servlet/JiveServlet/showImage/38-4854-18193/jbosstolsdevstudio.png https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4854-18193/jbosstolsdevstudio.png h4. CR1 Developer Studio: [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bbop=viewforumf=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter] JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution. JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation. If you are into doing your own bleeding edge eclipse plugin assembly, JBoss tools is for you; if you are more into having something that Just Works then JBoss Developer Studio is the way to go. h2. Installation +JBoss Developer Studio+ comes with everything pre-bundled in its installer. Simply http://devstudio.jboss.com/earlyaccess download it and run it like this: java -jar jbdevstudio-installername.jar *Note:* if you are on Windows or Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory. +JBoss Tools+ requires a bit more: This release requires at least Eclipse 3.7.2 but we recommend using the http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/indigosr2 Eclipse 3.7.2 JEE Bundle since then you get most of the dependencies preinstalled. Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under JBoss Tools (Indigo) or use our update site directly. The update site URL to use from Help Install New Software... is: http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/ Note: SOA tooling for BPEL, Drools, Guvnor, jBPM, ESB, Modeshape, pi4soa, Savara, SwitchYard Teiid are no longer included in the JBoss Tools release. They will be available separately. h2. JBoss AS 7 The server adapter for JBoss AS 7 had a series improvements done in its handling of remote management and JMX connections. One thing that is relevant is that because of AS 7.1 https://community.jboss.org/community/tools/blog/2012/02/29/excited-about-jboss-as-71-part-ii-developer-friendly-security Secure by default approach when you launch remotely the management services are not autoatmically exposed. We keep that secure-by-default in the tools, but now also provides a simple checkbox to allow you to expose the management service when we launch it to actually remotely manage the server. https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png Of course just exposing the port does not make it fully available before you have added a user to the server. You can read about how to do that in https://community.jboss.org/community/tools/blog/2012/02/29/excited-about-jboss-as-71-part-ii-developer-friendly-security this blog. And finally the server adapter now works with IPv6, allows deploying outside of the deployments folder and it does not choke on a space in the server part - Hurray! h2. OpenShift, now faster and more patient One of the most common bug report we got in the Beta's (thank you for the feedback!) was that when creating OpenShift applications our wizard would time out and you would have to manually import the project again. We now have extended the timeout period to three minutes to accomodate for overloads, network latency etc. but also given you the option to wait some more for the OpenShift provisioning to be fully done. A new feature of the application creation wizard is also to be able to set the size of the Gear your application will run on and to enable scaling for your applications. http://docs.jboss.org/tools/whatsnew/openshift/images/gears-and-scaling.png http
[jboss-user] [JBoss Tools] - Running JBoss Developer Studio 4.x with JDK 7
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document: Running JBoss Developer Studio 4.x with JDK 7 To view the document, visit: http://community.jboss.org/docs/DOC-17191 -- When installing JBoss Developer Studio 4.x, if you attempt to set JDK 7 as the Java version to be used you will encounter an error and installation will not complete. JBoss Developer Studio 4.x is not supported with Java 7, however you can complete installation with Java 6 and then follow a few steps to allow it to work with Java 7; though it must be stressed that this is not supported. Java 7 will be supported for JBoss Developer Studio 5. To use Java 7 with JBoss Developer Studio 4.x: - Install JBoss Developer Studio using Java 6 - After installation, navigate to the /studio/ folder of your installation. - Open the *jbdevstudio.ini* file in a text editor - Add the following lines to the end of the file: *-vm* * JAVA_7_FOLDER/bin/java* - Replace *JAVA_7_FOLDER* with the path to your Java 7 installation - Save the file and exit your text editor When you next launch JBoss Developer Studio 4.x it will use Java 7. There are a number of other things you can configure in the *jbdevstudio.ini* file. See http://wiki.eclipse.org/Eclipse.ini http://wiki.eclipse.org/Eclipse.ini or http://wiki.eclipse.org/IRC_FAQ#How_do_I_start_Eclipse.3F http://wiki.eclipse.org/IRC_FAQ#How_do_I_start_Eclipse.3F -- Comment by going to Community [http://community.jboss.org/docs/DOC-17191] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - JBoss Tools vs Developer Studio
Nick Boldt [http://community.jboss.org/people/nickboldt] commented on the document JBoss Tools vs Developer Studio To view all comments on this document, visit: http://community.jboss.org/docs/DOC-13300#comment-7585 -- Note that the supported platforms / JDK versions for JBT/JBDS are most often the same as those of the underlying Eclipse supported platforms / JDK versions: http://www.eclipse.org/eclipse/development/readme_eclipse_3.7.html#TargetOperatingEnvironments http://www.eclipse.org/eclipse/development/readme_eclipse_3.7.html#TargetOperatingEnvironments http://www.eclipse.org/eclipse/development/readme_eclipse_3.6.2.html#TargetOperatingEnvironments http://www.eclipse.org/eclipse/development/readme_eclipse_3.6.2.html#TargetOperatingEnvironments http://www.eclipse.org/eclipse/development/readme_eclipse_3.5.2.html#TargetOperatingEnvironments http://www.eclipse.org/eclipse/development/readme_eclipse_3.5.2.html#TargetOperatingEnvironments -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - JBoss Tools vs Developer Studio
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document: JBoss Tools vs Developer Studio To view the document, visit: http://community.jboss.org/docs/DOC-13300 -- Below is a comparison matrix to illustrate what parts of JBoss Tools have been included in the various releases of Developer Studio and which additional out-of-the-box setup and software Developer Studio provides. It should be noted that JBoss Tools is a set of plugins that can be installed into Eclipse while Developer Studio makes the getting started out-of-the-box experience easier and simpler. This is evident in the matrix below with entries showing that Developer Studio has an installer that helps in configuring your runtimes, distributes Eclipse and WTP, and includes support for the supported platforms from JBoss (EAP, EWP, EWS, SOA, and EPP). || || *JBoss Tools 2.x* || *JBoss Tools 3.0.x* || *JBoss Tools 3.1* || JBoss Tools 3.2.x || JBoss Tools 3.3.x (Core SOA) || *Developer Studio 1.x* || *Developer Studio 2.x* || *Developer Studio 3.0.x* || *Developer Studio 4.0.x* || *Developer Studio 4.1.x* || Developer Studio 5.0.x (Core SOA) || | *Features:* | | | | | | | | | | | | | Hibernate | X | X | X | X | X | X | X | X | X | X | X | | Seam | X | X | X | X | X | X | X | X | X | X | X | | CDI (JSR-299) | | | X | X | X | | | X (Tooling Tech Preview) | X (Tech preview) | X (Tech preview) | X | | jBPM | X | X | X | X (v3 4) | X (SOA) | X | X | X | X (v3 only) | X (v3) | X (SOA) | | Visual Page Editor | X | X | X | X | X | X | X | X | X | X | X | | FreeMarker | X | X | X | X | X | X | X | X | X | X | X | | Struts | X | X | X | X | X | X | X | X | X | X | X | | JBoss AS | X | X | X | X | X | X | X | X | X | X | X | | Project Archives | X | X | X | X | X | X | X | X | X | X | X | | Drools | | X | X | X | X (SOA) | | X | X | X | X | X (SOA) | | Portlet | | X | X | X | X | | X | X | X | X | X | | ESB | | X | X | X | X (SOA) | | X | X | X | X | X (SOA) | | JBoss Webservices | | X | X | X | X | | X | X | X | X | X | | Smooks | | X | X | X | X (SOA) | | | X | X | X | | | Birt Integration | | X | X | X | X | | | | | | | | TPTP Integration | | X | X | X | (TPTP not part of Indigo) | | | X (requires TPTP to be installed) | X (requires TPTP to be installed) | X (requires TPTP to be installed) | (TPTP not part of Indigo) | | Maven | | | X (requires m2eclipse) | X (requires m2eclipse) | X (requires m2e) | | | | | | X | | Usage (tracking) | | | | X | X | | | | X | X | X | | Modeshape | | | | X | X (SOA) | | | | X | X | X (SOA) | | Teiid | | | | X | X (SOA) | | | | X | X | X (SOA) | | Delta Cloud | | | | X | X | | | | | | | | | | | | | | | | | | | | | *Setup:* | | | | | | | | | | | | | Zip | X | X | X (deprecated) | | | | | | | | | | Update site | X | X | X | X | X | | X (since 2.1) | X | X | X (+extras) | X (Core SOA) | | Archived Update Site | | | X | X | X | | | | (X) | | | | Installer | | | | | | X | X | X | X | X | X (Core) | | | | | | | | | | | | | | | *3rd Party plugins:* | | | | | | | | | | | | | Eclipse | | | | | X | X | X (3.4) | X (3.5) | X (3.6) | X (3.6+) | X (3.7) | | Web Tools | | | | | X | X | X | X | X | X | X | | SpringIDE | | | | | X | X | X | X | X | X | X (extras) | | TestNG | | | | | X | X | X | X | X | X | X (extras) | | | | | | | | | | | | | | | *Integrated Platforms:* | | | | | | | | | | | | | JBoss Enterprise Application Platform | | | | | | X (EAP 4) | X (EAP 4) | X (EAP 4) | X (EAP 5) | X (EAP 5) | X (EAP 6) | | JBoss SOA Platform | | | | | | | X (separate download) | X (separate download) | X (separate download) | X (seperate download) | X (seperate download) | | JBoss Enterprise Portal Platform | | | | | | | X (separate download) | X (separate download) | X (separate download) | X (separate download) | X (separate download) | | JBoss Enterprise Web Server | | | | | | | | X (separate download) | X (separate download) | X (seperate download) | X (seperate download) | -- Comment by going to Community [http://community.jboss.org/docs/DOC-13300] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Re: Update site broken for Maven Integration in Tools 3.2
Nick Boldt [http://community.jboss.org/people/nickboldt] created the discussion Re: Update site broken for Maven Integration in Tools 3.2 To view the discussion, visit: http://community.jboss.org/message/619297#619297 -- Whoops, looks like my fault. We're moving from m2e 0.12 to 1.0 in the next JBoss Tools 3.2.1 release for Helios (Eclipse 3.6.2), and I suppose I moved the requirements site [1] up too soon. [1] http://download.jboss.org/jbosstools/updates/helios/ http://download.jboss.org/jbosstools/updates/helios/ To resolve those dependencies, you can either add this URL to Eclipse to get the bits we used for building JBoss Tools 3.2.0 (m2e 0.12.1 and m2e-wtp 0.11.1): http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/0.12/ http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/0.12/ Or, use these sites to install the latest 0.12.x content: https://repository.sonatype.org/content/repositories/forge-sites/m2e/0.12.2/S/0.12.2.20110415-2017/ https://repository.sonatype.org/content/repositories/forge-sites/m2e/0.12.2/S/0.12.2.20110415-2017/ https://repository.sonatype.org/content/repositories/forge-sites/m2eclipse-wtp/0.12.0/S/0.12.0.20110421-1500/ https://repository.sonatype.org/content/repositories/forge-sites/m2eclipse-wtp/0.12.0/S/0.12.0.20110421-1500/ https://repository.sonatype.org/content/repositories/forge-sites/m2e-extras/0.12.1/N/0.12.1.201101250603/ https://repository.sonatype.org/content/repositories/forge-sites/m2e-extras/0.12.1/N/0.12.1.201101250603/ If you want to try our almost-but-not-quite 3.2.1 release, it's available here: http://download.jboss.org/jbosstools/updates/development/helios/ http://download.jboss.org/jbosstools/updates/development/helios/ Let me know if that solves the problem for you. -- Reply to this message by going to Community [http://community.jboss.org/message/619297#619297] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [JBoss Tools] - JBoss Tools Milestone for Eclipse 3.7 M6 (Indigo)
Nick Boldt [http://community.jboss.org/people/nickboldt] commented on JBoss Tools Milestone for Eclipse 3.7 M6 (Indigo) To view all comments on this blog post, visit: http://community.jboss.org/community/tools/blog/2011/05/12/jboss-tools-milestone-for-eclipse-37-m6-indigo#comment-6537 -- Because the Eclipse Indigo M6 release it no longer available, installing JBoss Tools 3.3.0.M1 is a bit more difficult that when we first released it. You will need to install Eclipse Classic SDK for your platform from here: http://download.eclipse.org/eclipse/downloads/drops/S-3.7M6-201103101119/index.php#EclipseSDK http://download.eclipse.org/eclipse/downloads/drops/S-3.7M6-201103101119/index.php#EclipseSDK then point Eclipse at the JBoss Tools Development milestone site: http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/ --- Alternatively, you can use a newer Eclipse or Indigo release: http://download.eclipse.org/eclipse/downloads/drops/S-3.7RC3-201105261708/index.php#EclipseSDK http://download.eclipse.org/eclipse/downloads/drops/S-3.7RC3-201105261708/index.php#EclipseSDK or http://www.eclipse.org/downloads/packages/release/indigo/rc2 http://www.eclipse.org/downloads/packages/release/indigo/rc2 then point it at this site to install a preview of the JBoss Tools 3.3.0.M2 release: http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/trunk/ Note that the nightly site is subject to change and will be replaced w/ new bits fairly frequently. If you install fails due to missing artifacts, simply try again. If you'd rather install a nightly from a snapshot, look here: http://download.jboss.org/jbosstools/builds/nightly/trunk/ http://download.jboss.org/jbosstools/builds/nightly/trunk/ (Choose a build, then enter the all/ folder to get the update site URL or download the zip.) -- ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Re: JBoss Tools 3.1 CR1 is out (comments)
Nick Boldt [http://community.jboss.org/people/nickboldt] created the discussion Re: JBoss Tools 3.1 CR1 is out (comments) To view the discussion, visit: http://community.jboss.org/message/600044#600044 -- Probably obvious to all, but since this article continues to get tons of pageviews I thought I'd mention that JBoss Tools 3.1.1 has been released. https://www.jboss.org/tools/download/stable/3_1_GA https://www.jboss.org/tools/download/stable/3_1_GA Also, if you'd like something newer, JBoss Tools 3.2.0 has also been released. https://www.jboss.org/tools/download/stable/3_2_GA https://www.jboss.org/tools/download/stable/3_2_GA -- Reply to this message by going to Community [http://community.jboss.org/message/600044#600044] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Manage SWTBot bits used by builds and developers
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document: Manage SWTBot bits used by builds and developers To view the document, visit: http://community.jboss.org/docs/DOC-16087 -- JBT/JBDS builds and JBT/JBDS SWTBot tests developers have to use the same version of SWTBot to ensure consistency. Current version of SWTBot release used is specified in the target platform definition files (*.target) stored in SVN repository here: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/. There are two files available. *Multiple.target* contains all the source URLs from whichc the target is built. *Unified.target* contains the same IUs (installable units) but swaps out the URLs for our own JBoss mirror, located here: http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/ Open the .target file in your favourite Text or XML Editor, and search (CTRL-F or /) for swtbot to find the relevant IUs and their versions. .feature.group means this feature and all its contained plugins. h5. Updating JBoss Tools Hudson Builds To The Latest SWTBot Release When SWTBot needs to be updated, verify your tests will still work with the latest release: 1. Compile complete SWTBot test suite in your workspace (using M2Eclipse) or via commandline (using Tycho) to verify updated SWTBot release does not break your tests.* If there are compilation errors, fix them or report them in JIRA. Test locally before committing changes to the tests back to SVN 2. Update SWTBot target file to specify proper SWTBot release version and commit it to SVN. 1. The easiest way to do this is to do a Maven build in the target-platform directory and generate the target platform repo locally. * cd ~/trunk/build/target-platform; mvn3 clean install -P get.*local.target* 2. This will fetch all the contents from the target platform, and update the .target files to use the versions found in the repo you generate locally. You can also update the .target files by hand, if you prefer, but the automated approach is easier and less error-prone. 3. As a result of running a build of the target platform locally, you can now *OPTIONALLY* use that repo instead of the remote one when running your builds. To activate this *local.target* repo, do this:* cd ~/trunk/build/parent; mvn3 clean install -P *local.target* * cd ~/trunk/build; mvn3 clean install -P*+componentToBuild+*,*local.target* (where +*componentToBuild*+ may be as, archives, esb, ... or as-bootstrap, archives-bootstrap, esb-bootstrap, ...) While a build will run automatically in response to your committed changes, you can also kick one manually to save time: * http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platform/build http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platform/build It's important to let others know that you've updated the SWTBot baseline against which everyone's tests will be run. Send an email to the mailing list here: * mailto:external-exadel-l...@redhat.com external-exadel-l...@redhat.com -- Comment by going to Community [http://community.jboss.org/docs/DOC-16087] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] - Manage SWTBot bits used by builds and developers
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document: Manage SWTBot bits used by builds and developers To view the document, visit: http://community.jboss.org/docs/DOC-16087 -- JBT/JBDS builds and JBT/JBDS SWTBot tests developers have to use the same version of SWTBot to ensure consistency. Current version of SWTBot release used is specified in the target platform definition files (*.target) stored in SVN repository here: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/. There are two files available. *Multiple.target* contains all the source URLs from whichc the target is built. *Unified.target* contains the same IUs (installable units) but swaps out the URLs for our own JBoss mirror, located here: http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/ Open the .target file in your favourite Text or XML Editor, and search (CTRL-F or /) for swtbot to find the relevant IUs and their versions. .feature.group means this feature and all its contained plugins. h5. Updating JBoss Tools Hudson Builds To The Latest SWTBot Release When SWTBot needs to be updated, verify your tests will still work with the latest release: 1. Compile complete SWTBot test suite in your workspace (using M2Eclipse) or via commandline (using Tycho) to verify updated SWTBot release does not break your tests.* If there are compilation errors, fix them or report them in JIRA. Test locally before committing changes to the tests back to SVN 2. Update SWTBot target file to specify proper SWTBot release version and commit it to SVN. 1. The easiest way to do this is to do a Maven build in the target-platform directory and generate the target platform repo locally. * cd ~/trunk/build/target-platform; mvn3 clean install -P get.*local.target* 2. This will fetch all the contents from the target platform, and update the .target files to use the versions found in the repo you generate locally. You can also update the .target files by hand, if you prefer, but the automated approach is easier and less error-prone. 3. As a result of running a build of the target platform locally, you can now *OPTIONALLY* use that repo instead of the remote one when running your builds. To activate this *local.target* repo, do this:* cd ~/trunk/build/parent; mvn3 clean install -P *local.target* * cd ~/trunk/build; mvn3 clean install -P*+componentToBuild+*,*local.target* (where +*componentToBuild*+ may be as, archives, esb, ... or as-bootstrap, archives-bootstrap, esb-bootstrap, ...) While a build will run automatically in response to your committed changes, you can also kick one manually to save time: * http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platform/build http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platform/build h5. Updating JBoss Developer Studio (Uberbuilder) Hudson Builds To The Latest SWTBot Release 1. Create a collection of new zips of the for the updated releases. 2. Create new md5sums. 3. Publish them somewhere that Hudson can see them 4. Update the properties file that JBDS uses to access them: * http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/requirements/swtbot/build.properties http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/requirements/swtbot/build.properties h5. Communication Strategy, or, Letting People Know About Changes It's important to let others know that you've updated the SWTBot baseline against which everyone's tests will be run. Send an email to the mailing list here: * mailto:external-exadel-l...@redhat.com external-exadel-l...@redhat.com -- Comment by going to Community [http://community.jboss.org/docs/DOC-16087] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2128] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools Development] - JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)
Nick Boldt [http://community.jboss.org/people/nickboldt] created the document: JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools) To view the document, visit: http://community.jboss.org/docs/DOC-15755 -- *+This document is a work in progress and subject to change.+* In order to build JBoss Tools in your workspace (or on your local machine, if not in Eclipse), you need to have its dependencies available. There are a number of ways to accomplish this, depending on your needs and how much manual effort you'd like to expend. *1. Build Parent Pom + Target Platform With Tycho + Maven 3* Build the parent pom [1] + target platform [2], then build against that with maven3 (commandline) or m2eclipse (and don't use PDE anymore when building in Eclipse) cd /tmp; \ svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build; \ cd /tmp/build/parent; \ mvn3 clean install Then... cd /tmp; \ svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; \ cd /tmp/tests; \ mvn3 clean install (etc.) This is how the Hudson builds run - compile the parent (which compiles the target platform), then build whatever component(s) you then want. If you have the entire JBoss Tools tree on disk, you can also do multi-component builds even simpler like this: cd /tmp; \ svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/ http://anonsvn.jboss.org/repos/jbosstools/trunk; \ cd /tmp/trunk/build/component; \ mvn3 clean install -f seam.xml *2. Load Target Platform in Eclipse* Attempt to get the target platform file [2] to load in Eclipse, then click 'set as target platform' in the top right corner of the editor when it's open in the Target Platform editor. This should resolve everything in the target, and install it into your Eclipse. When it works. The editor is kinda flaky. When it completes (and it may take a significant amount of time during which your Eclipse may be unstable / unusable), you should have everything you need to develop JBoss Tools. *3. Manual Install from Update Sites (p2 Repos)* Read through either [1] or [2] and install - by hand - what you need from the various update sites against which we install. The sites are listed in two places [1], [2]. The target platform file lists the features/plugins you need to include when installing; the parent pom only lists the update sites. YMMV. *4. Manually Download and Unpack Runnable Zips* Pull down the SDKs/runtime zips [3] and dump them into your eclipse's dropins/ folder. This is the way the old uberbuilder works, and is deprecated, but should still work. [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml [2] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36-wtp32.target http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36-wtp32.target [3] http://download.jboss.org/jbosstools/requirements/helios/README.txt http://download.jboss.org/jbosstools/requirements/helios/README.txt, http://download.jboss.org/jbosstools/requirements/helios/ http://download.jboss.org/jbosstools/requirements/helios/ (GWT is missing, but the collection should otherwise be complete) -- Comment by going to Community [http://community.jboss.org/docs/DOC-15755] Create a new document in JBoss Tools Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102containerType=14container=2129] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools Development] - How to Build JBoss Tools with Maven3
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
How to Build JBoss Tools with Maven3
To view the document, visit: http://community.jboss.org/docs/DOC-15513
--
Current trunk version of JBoss Tools can be built with maven 3 and make it
faster and easier for everyone.
+*If you're trying to compile JBoss Tools within Eclipse for plugin
development,
https://community.jboss.org/wiki/JBossToolsTargetPlatformProvisioningorhowtoresolvemissingdependencieswhencompilingJBossTools
read this to get all the dependencies installed.*+
h2. Prerequisites
1. Java 1.6 SDK
2. Maven 3.beta1
3. About 6 GB of free disk space if you want to run all integration tests for
(JBoss AS, Seam and Web Services Tools)
4. subversion client 1.6.X (should work with lower version as well)
h2. Environment Setup
h3. Maven and Java
Make sure your maven 3 is available by default and Java 1.6 is used.
mvn -version
should print out something like
Apache Maven 3.0-beta-2 (r983206; 2010-08-07 07:00:51-0400)
Java version: 1.6.0_18
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux version: 2.6.32.14-127.fc12.i686 arch: i386 Family: unix
h3. Sources
Checkout sources from anonymous SVN like
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk jbosstools-trunk
This will take some time dependent on your bandwidth
h2. Build Strategies
All commands below is assuming that commands are executed in jbosstools-src
folder after sources checked out as it suggested above.
There are several strategies to chose from building everything to build
particular component or part of it like all plug-ins, all tests, all features,
particular plugin/feature.
Target platform and parent pom should be built first like
mvn clean install -f build/parent/pom.xml
If you want to just compile the modules, tests can be skipped by adding
system property *-Dmaven.test.skip=true* and you should be able to faster
verify compile issues.
h3. Build/Test Everything
Current version cannot be build without local changes because of problem with
with drools component, so to go with this scenario you need to remove drools
references from pom.xml and site/site.xml. After that to build/test everything
use:
mvn clean install
h3. Build/Test Particular Component with Dependencies
For convenience there are aggregator projects defined for each component. It
provides a simple way to build/test components with dependencies.
mvn clean install -f build/component/${component.name}.xml
where ${component.name} is component you want to build/test. Currently
build/component folder contains aggregator projects for:
1. tests
2. jmx
3. archives
4. as
5. common
6. seam
7. vpe
8. archives
9. as
More are coming soon. To know the order in which to build prerequisite
components for your component, see
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
h3. Build/Test Single Component
Be aware that to get this work all dependencies for this component must be
installed in maven repo. It can be done by build everything first or by build
component and its dependencies using aggregated project as it explained above.
You can skip tests for this build and then enable them back when you run single
component build.
To build single component use pom.xml in component's folder like it is shown
below.
mvn clean install -f ${component.name}/pom.xml
where ${component.name} is component's root folder name. For instance to build
jmx component use command below
mvn clean install -f jmx/pom.xml
or, if you prefer, you can build a series of components in order (with tests
skipped using *-Dmaven.test.skip=true*):
for d in tests jmx archives as; do \
pushd $d; mvn clean install -Dmaven.test.skip=true; popd; \
done
h3. Adding a Plugin To An Existing Component
Now that you can build your component, you can easily add a new plugin to that
component. Here's how.
0. Make sure your new plugin compiles in your workspace. Ensure your
MANIFEST.MF contains all references/includes/requirements you need. Be sure to
set the correct Bundle-RequireExecutionEnvironment (eg., JDK5 or JDK6).
1. When you are satisfied, you can commit your new plugin project to SVN.
cd ~/trunk/as/plugins; \
svn add org.jboss.ide.eclipse.as.rse.core; \
svn ci -m JBIDE-123456 Initial commit of new as.rse.core plugin
org.jboss.ide.eclipse.as.rse.core
2. Next, add a pom.xml file to the root of your new project.
You can use m2eclipse to help w/ this if you have it installed; otherwise copy
from another existing plugin project and edit appropriately. The version of the
pom should match the version in the manifest.mf. Note that 3.2.0.qualifier (in
MANIFEST.MF) is equivalent to 3.2.0-SNAPSHOT in the pom.xml.
3. Build your plugin:
cd ~/trunk/as/plugins
[jboss-user] [JBoss Tools Development] - How to Build JBoss Tools with Maven3
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
How to Build JBoss Tools with Maven3
To view the document, visit: http://community.jboss.org/docs/DOC-15513
--
Current trunk version of JBoss Tools can be built with maven 3 and make it
faster and easier for everyone.
h2. Prerequisites
1. Java 1.6 SDK
2. Maven 3.beta1
3. About 6 GB of free disk space if you want to run all integration tests for
(JBoss AS, Seam and Web Services Tools)
4. subversion client 1.6.X (should work with lower version as well)
h2. Environment Setup
h3. Maven and Java
Make sure your maven 3 is available by default and Java 1.6 is used.
$mvn -version
should print out something like
Apache Maven 3.0-beta-2 (r983206; 2010-08-07 07:00:51-0400)
Java version: 1.6.0_18
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux version: 2.6.32.14-127.fc12.i686 arch: i386 Family: unix
h3. Sources
Checkout sources from anonymous SVN like
$svn co http://anonsvn.jboss.org/repos/jbosstools/trunk jbosstools-src
This will take some time dependent on your bandwidth
h2. Build Strategies
All commands below is assuming that commands are executed in jbosstools-src
folder after sources checked out as it suggested above.
There are several strategies to chose from building everything to build
particular component or part of it like all plug-ins, all tests, all features,
particular plugin/feature.
Target platform and parent pom should be built first like
$mvn clean install -f build/parent/pom.xml
If you want to just compile the modules, tests can be skipped by adding
system property *-Dmaven.test.skip=true* and you should be able to faster
verify compile issues.
h3. Build/Test Everything
Current version cannot be build without local changes because of problem with
with drools component, so to go with this scenario you need to remove drools
references from pom.xml and site/site.xml. After that to build/test everything
use:
$mvn clean install
h3. Build/Test Particular Component with Dependencies
For convenience there are aggregator projects defined for each component. It
provides a simple way to build/test components with dependencies.
$mvn clean install -f build/component/${component.name}.xml
where ${component.name} is component you want to build/test. Currently
build/component folder contains aggregator projects for:
1. tests
2. jmx
3. archives
4. as
5. common
6. seam
7. vpe
8. archives
9. as
More are coming soon. To know the order in which to build prerequisite
components for your component, see
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
h3. Build/Test Single Component
Be aware that to get this work all dependencies for this component must be
installed in maven repo. It can be done by build everything first or by build
component and its dependencies using aggregated project as it explained above.
You can skip tests for this build and then enable them back when you run single
component build.
To build single component use pom.xml in component's folder like it is shown
below.
$mvn clean install -f ${component.name}/pom.xml
where ${component.name} is component's root folder name. For instance to build
jmx component use command below
$mvn clean install -f jmx/pom.xml
or :if you prefer, you can build a series of components in order (with tests
skipped using *-Dmaven.test.skip=true*):
$for d in tests jmx archives as; do \
pushd $d; mvn clean install *-Dmaven.test.skip=true*; popd; \
done
--
h3. Adding a Plugin To An Existing Component
Now that you can build your component, you can easily add a new plugin to that
component. Here's how.
0. Make sure your new plugin compiles in your workspace. Ensure your
manifest.mf contains all references/includes/requirements you need. Be sure to
set the correct Bundle-RequireExecutionEnvironment (eg., JDK5 or JDK6).
1. When you are satisfied, you can commit your new plugin project to SVN.
cd ~/trunk/as/plugins
svn add org.jboss.ide.eclipse.as.rse.core
svn ci -m JBIDE-123456 Initial commit of new
org.jboss.ide.eclipse.as.rse.core plugin org.jboss.ide.eclipse.as.rse.core
2. Next, add a pom.xml file to the root of your new project.
You can use m2eclipse to help w/ this if you have it installed; otherwise copy
from another existing plugin project and edit appropriately. The version of the
pom should match the version in the manifest.mf. Note that 3.2.0.qualifier (in
manifest.mf) is equivalent to 3.2.0-SNAPSHOT in the pom.xml.
3. Build your plugin:
cd ~/trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core
mvn3 clean install
4. If your component's new plugin builds successfully, you can commit the
pom.xml file, and add a reference to the new plugin
[jboss-user] [JBoss Tools Development] - How to Build JBoss Tools with Maven3
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
How to Build JBoss Tools with Maven3
To view the document, visit: http://community.jboss.org/docs/DOC-15513
--
Current trunk version of JBoss Tools can be built with maven 3 and make it
faster and easier for everyone.
h2. Prerequisites
1. Java 1.6 SDK
2. Maven 3.beta1
3. About 6 GB of free disk space if you want to run all integration tests for
(JBoss AS, Seam and Web Services Tools)
4. subversion client 1.6.X (should work with lower version as well)
h2. Environment Setup
h3. Maven and Java
Make sure your maven 3 is available by default and Java 1.6 is used.
mvn -version
should print out something like
Apache Maven 3.0-beta-2 (r983206; 2010-08-07 07:00:51-0400)
Java version: 1.6.0_18
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux version: 2.6.32.14-127.fc12.i686 arch: i386 Family: unix
h3. Sources
Checkout sources from anonymous SVN like
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk jbosstools-trunk
This will take some time dependent on your bandwidth
h2. Build Strategies
All commands below is assuming that commands are executed in jbosstools-src
folder after sources checked out as it suggested above.
There are several strategies to chose from building everything to build
particular component or part of it like all plug-ins, all tests, all features,
particular plugin/feature.
Target platform and parent pom should be built first like
mvn clean install -f build/parent/pom.xml
If you want to just compile the modules, tests can be skipped by adding
system property *-Dmaven.test.skip=true* and you should be able to faster
verify compile issues.
h3. Build/Test Everything
Current version cannot be build without local changes because of problem with
with drools component, so to go with this scenario you need to remove drools
references from pom.xml and site/site.xml. After that to build/test everything
use:
mvn clean install
h3. Build/Test Particular Component with Dependencies
For convenience there are aggregator projects defined for each component. It
provides a simple way to build/test components with dependencies.
mvn clean install -f build/component/${component.name}.xml
where ${component.name} is component you want to build/test. Currently
build/component folder contains aggregator projects for:
1. tests
2. jmx
3. archives
4. as
5. common
6. seam
7. vpe
8. archives
9. as
More are coming soon. To know the order in which to build prerequisite
components for your component, see
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
h3. Build/Test Single Component
Be aware that to get this work all dependencies for this component must be
installed in maven repo. It can be done by build everything first or by build
component and its dependencies using aggregated project as it explained above.
You can skip tests for this build and then enable them back when you run single
component build.
To build single component use pom.xml in component's folder like it is shown
below.
mvn clean install -f ${component.name}/pom.xml
where ${component.name} is component's root folder name. For instance to build
jmx component use command below
mvn clean install -f jmx/pom.xml
or :if you prefer, you can build a series of components in order (with tests
skipped using *-Dmaven.test.skip=true*):
for d in tests jmx archives as; do \
pushd $d; mvn clean install -Dmaven.test.skip=true; popd; \
done
h3. Adding a Plugin To An Existing Component
Now that you can build your component, you can easily add a new plugin to that
component. Here's how.
0. Make sure your new plugin compiles in your workspace. Ensure your
MANIFEST.MF contains all references/includes/requirements you need. Be sure to
set the correct Bundle-RequireExecutionEnvironment (eg., JDK5 or JDK6).
1. When you are satisfied, you can commit your new plugin project to SVN.
cd ~/trunk/as/plugins; \
svn add org.jboss.ide.eclipse.as.rse.core; \
svn ci -m JBIDE-123456 Initial commit of new as.rse.core plugin
org.jboss.ide.eclipse.as.rse.core
2. Next, add a pom.xml file to the root of your new project.
You can use m2eclipse to help w/ this if you have it installed; otherwise copy
from another existing plugin project and edit appropriately. The version of the
pom should match the version in the manifest.mf. Note that 3.2.0.qualifier (in
MANIFEST.MF) is equivalent to 3.2.0-SNAPSHOT in the pom.xml.
3. Build your plugin:
cd ~/trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core; \
mvn3 clean install
4. If your component's new plugin builds successfully, you can commit the
pom.xml file, and add a reference to the new plugin (module) in the container
pom:
vi ~/trunk/as/plugins/pom.xml
5. To ensure
[jboss-user] [JBoss Tools] New message: Re: Problem creating local mirror of JBoss Tools for 3.1 final
User development, A new message was posted in the thread Problem creating local mirror of JBoss Tools for 3.1 final: http://community.jboss.org/message/532654#532654 Author : Nick Boldt Email : nbo...@redhat.com Profile : http://community.jboss.org/people/nickboldt Message: -- Rather than pulling down pieces of the site, why not grab the whole archive in a single zip, then unpack it (if needed - you don't have to unzip the update site to use it) and use that? Here's the whole update site in a single download: http://downloads.sourceforge.net/jboss/JBossTools-Update-3.1.0.v201003050540R-H56-GA.zip -- To reply to this message visit the message page: http://community.jboss.org/message/532654#532654 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Tools] New message: Re: jbt manual installation in dropins folder
User development, A new message was posted in the thread jbt manual installation in dropins folder: http://community.jboss.org/message/531832#531832 Author : Nick Boldt Email : nbo...@redhat.com Profile : http://community.jboss.org/people/nickboldt Message: -- We no longer provide a runnable zip of all of JBoss Tools for install-by-unzip into dropins, because installation that way is error-prone (particularly on Windows) and doesn't bring in third-party dependencies like birt, maven, or svn, so things you've installed are not activated and you have no idea why (or how to diagnose why). There are still some individual components' zips available [1], but they are being phased out too, and are not recommended for use. The p2 repo site or zip is the best approach. [1] http://www.jboss.org./tools/download/stable/3_1_GA.html If you cannot use a p2 repo site or zip to do your installation (because you want to automate it via script or do so via commandline) you can do one of three things: a) convert the p2 repo site zip into a runnable zip [2], then unpack that into dropins. Not recommended, but doable. (Basically the process involves unzipping all the features and some of the the plugins (those marked unpack=true in their containing feature's feature.xml). repo2runnable also handles use of unpack200 to unpack packed jars, and therefore requires a 5.0 or 6.0 JDK) b) mirror the p2 repo site (or zip) into a folder [3] on your disk, then use p2 to install from there (or see (a) above). Not recommended but certainly doable. c) use a script to run the p2 director [4] to do the install for you headlessly. Recommended, if required. [2]http://wiki.eclipse.org/Equinox/p2/Ant_Tasks#Repo2Runnable, http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.common.releng/tools/scripts/p2repoFormatToRunnableSDKFormat.xml?root=Technology_Projectview=markup [3]http://wiki.eclipse.org/Equinox/p2/Ant_Tasks/Partial_Mirroring/Example, http://wiki.eclipse.org/Equinox/p2/Ant_Tasks#Partial_Mirroring [4]https://www.jboss.org/tools/download/installation/update_3_1.html#fromscript -- To reply to this message visit the message page: http://community.jboss.org/message/531832#531832 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
