[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2869 at 7/3/14 10:05 PM:
-----------------------------------------------------------
Changes (compared to 4.40.0.Beta1)
=======
In the category "Fix dependencies" (after the cleanup of previous release)
* JBIDE-16910: Fix some dependencies for Atlassian (Mylyn)
* JBIDE-16960: Removed GWT
* JBIDE-17019: Add m2eclipse-egit
* JBDS-3003: Add TestNG (JBDS only)
* JBIDE-17160, JBIDE-17317: Add Tern.java
* JBIDE-17254: Move to Luna M7
* JBIDE-17266: Remove Birt (temporary; added new version shortly thereafter)
---
VJET will soon be removed from the JBT Central target platform, and moved to a new one for Early Access stuff. See JBIDE-16375.
was (Author: nickboldt):
Changes (compared to 4.40.0.Beta1)
=======
In the category "Fix dependencies" (after the cleanup of previous release)
* JBIDE-16910: Fix some dependencies for Atlassian (Mylyn)
* JBIDE-16960: Removed GWT
* JBIDE-17019: Add m2eclipse-egit
* JBDS-3003: Add TestNG (JBDS only)
* JBIDE-17160, JBIDE-17317: Add Tern.java
* JBIDE-17254: Move to Luna M7
* JBIDE-17266: Remove Birt (hopefully temporary)
---
VJET will soon be removed from the JBT Central target platform, and moved to a new one for Early Access stuff. See JBIDE-16375.
> 3rd party certification for JBDS 8.0.0.GA
> -----------------------------------------
>
> Key: JBDS-2869
> URL: https://issues.jboss.org/browse/JBDS-2869
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 8.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible.
> Upstream question about JDK 7 support:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> Connectors we could update:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100
> * m2e-wro4j 1.0.2 connector
> * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP)
> * pmd/4.0.1
> * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP)
> * VJET/0.10.0.201309201624
> * eclipsecs/5.6.1.201306282206
> * springide/3.4.0.201310051539-RELEASE
> * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP)
> * subclipse/1.10.3_1.8.0.r10086_v20131126_1344/
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16695:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Add marker/quick fix if test contains non static deployment method
> ------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2869:
----------------------------------
Changes (8) compared to previous:
* JBIDE-17603 - Move to Luna R in JBT/JBDS/Central/EA TP
* JBDS-3032 - add m2e.jdt back into JBDS TP
* JBDS-3082 - add org.eclipse.core.runtime.compatibility.auth 3.2.300.v20120523-2004 to JBT/JBDS TP
* JBDS-3079 - move org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, org.jboss.tools.common.mylyn.feature out of JBDS update site and into Central TP
* JBIDE-17748 - Update Tern.java to 0.4.0.20140703 in JBT & EA TP
* JBIDE-17749 - Update AngularJS to 0.4.0.20140703 in EA TP
* JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP
* JBIDE-17742 - Remove EGit from Central Discovery
> 3rd party certification for JBDS 8.0.0.GA
> -----------------------------------------
>
> Key: JBDS-2869
> URL: https://issues.jboss.org/browse/JBDS-2869
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 8.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible.
> Upstream question about JDK 7 support:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> Connectors we could update:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100
> * m2e-wro4j 1.0.2 connector
> * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP)
> * pmd/4.0.1
> * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP)
> * VJET/0.10.0.201309201624
> * eclipsecs/5.6.1.201306282206
> * springide/3.4.0.201310051539-RELEASE
> * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP)
> * subclipse/1.10.3_1.8.0.r10086_v20131126_1344/
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17630) Duplicate/missing seam runtimes when there are 2 or more of the same version
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17630?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17630:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Duplicate/missing seam runtimes when there are 2 or more of the same version
> ----------------------------------------------------------------------------
>
> Key: JBIDE-17630
> URL: https://issues.jboss.org/browse/JBIDE-17630
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, seam2
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2c B130
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> When you detect runtimes in EAP 5.1 and then EAP 5.2, you end up with just one seam runtime in the IDE (both have Seam 2.2). When you then start with a new workspace and select to add just one of the runtimes, both get added.
> I hope you don't mind me combining two issues into one since they are closely related.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16863) Runtime detection add unchecked servers
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16863?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16863:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Runtime detection add unchecked servers
> ---------------------------------------
>
> Key: JBIDE-16863
> URL: https://issues.jboss.org/browse/JBIDE-16863
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 20, JBDS 8.0.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> When runtime detection detects multiple same servers (when one path is subpath of another)on of them is correctly unchecked, but when I uncheck the other one, the server is still added.
> I made a little screencast of this behaviour: http://youtu.be/e4OrN0s6SUg
> In this screencast I added /home/rhopp/runtimes where i have all my runtimes and then I added /home/rhopp/runtimes/jboss-as-7.1.1.Final and /home/rhopp/runtimes/jboss-eap-6.2
> When I click "Search" and want to add just EAP 6.1 runtime, AS 7.1.1 and EAP 6.2 are added also, even though they are unchecked.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16891) Add hover text to requirements table in New Project Example wizard
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16891?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16891:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Add hover text to requirements table in New Project Example wizard
> ------------------------------------------------------------------
>
> Key: JBIDE-16891
> URL: https://issues.jboss.org/browse/JBIDE-16891
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples
> Affects Versions: 4.2.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> It would be nice to have on hover popup on Description column in Requirements table showing whole text of that column.
> Text in Dscription column is often longer than default column width with important part on the end (e.g. supported runtimes enumeration) and extending width manually is annoying. I think on hover popup would be ideal solution to this.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17748) Update TP with Tern.java v.0.4.0.201407021311
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17748?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17748:
------------------------------------
Merged https://github.com/jbosstools/jbosstools-discovery/pull/184 in master.
> Update TP with Tern.java v.0.4.0.201407021311
> ---------------------------------------------
>
> Key: JBIDE-17748
> URL: https://issues.jboss.org/browse/JBIDE-17748
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Fix For: 4.2.0.Beta3
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.3.0. It contains few important fixes regarding cintent assist initialization and Node.js preferences like:*
> - https://github.com/angelozerr/tern.java/pull/72 -NPE in ImageResource.registerImageDescriptor()
> - https://github.com/angelozerr/tern.java/pull/80 - An embedded install of Node.js should be used by default
> - https://github.com/angelozerr/tern.java/pull/87 - Find a way to configure Tern Modules that are default for Nature Adapters defined on a project
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:*
> http://oss.opensagres.fr/tern.repository/0.4.0-SNAPSHOT/
> *JBoss mirror:*
> http://downloads.jboss.org/jbosstools/updates/requirements/tern.java-0.4....
> *Sources:*
> https://github.com/angelozerr/tern.java
> *Affected projects:*
> jbosstools-jst
> jbosstools-aerogear
>
> *Include in JBDS:*
> No
> *Type of dependency:*
> distribution
> *List of bundles added/removed:*
> TBD: need to update PR to use features
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17438) Verify source classpath api still fulfills requirements
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17438?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17438:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Verify source classpath api still fulfills requirements
> -------------------------------------------------------
>
> Key: JBIDE-17438
> URL: https://issues.jboss.org/browse/JBIDE-17438
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> The code resolving various runtimes' classpath has been changed to now check overlay and layer folders. Please verify that this still fulfills your needs with regards to the source jars use case, and that it works as expected for patched builds (ie wf8.1 patched, or eap6.2.2 patched)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17768) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Portlet]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17768?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-17768.
---------------------------------
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Portlet]
> -----------------------------------------------------
>
> Key: JBIDE-17768
> URL: https://issues.jboss.org/browse/JBIDE-17768
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: portal-gatein
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Portlet]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta3x
> git push origin jbosstools-4.2.0.Beta3x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2991) Non-fatal error logged when starting JBDS 8.0.beta1
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2991?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2991:
--------------------------------
Fix Version/s: 8.0.0.Beta3
(was: 8.0.0.CR1)
Sprint: Sprint to Beta3 Release
> Non-fatal error logged when starting JBDS 8.0.beta1
> ---------------------------------------------------
>
> Key: JBDS-2991
> URL: https://issues.jboss.org/browse/JBDS-2991
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 8.0.0.Beta1
> Environment: JBDS 8.0.beta1
> Java7 or Java8
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Fix For: 8.0.0.Beta3
>
>
> !ENTRY org.eclipse.core.runtime 2 0 2014-03-27 14:37:10.053
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by osgi.identity; osgi.identity="org.eclipse.core.runtime"; type="osgi.bundle"; version:Version="3.10.0.v20140221-2027"; singleton:="true"
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:259)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3748)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3396)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months