[JBoss JIRA] (JBDS-2989) Non-fatal error displayed in shell when starting JBDS8.0.beta1 with Java8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2989?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2989:
--------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Beta3)
> Non-fatal error displayed in shell when starting JBDS8.0.beta1 with Java8
> -------------------------------------------------------------------------
>
> Key: JBDS-2989
> URL: https://issues.jboss.org/browse/JBDS-2989
> 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
> java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: discuss
> Fix For: 8.0.0.CR1
>
>
> The error displayed is:
> ./jbdevstudio
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
--
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.CR1
(was: 8.0.0.Beta3)
> 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.CR1
>
>
> !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
[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 commented on JBDS-2991:
-------------------------------------
org.eclipse.core.runtime.compatibility.auth is available form luna repository and version is 3.2.300.v20120523-2004.
> 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.CR1
>
>
> !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
[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-16640:
---------------------------------------
[~maxandersen],
is this issue still relevant now that Luna has been released ? I understand that next time I should be more careful with the dependency version bump, for sure.
> Avoid bumping dependencies versions unless it is required
> ---------------------------------------------------------
>
> Key: JBIDE-16640
> URL: https://issues.jboss.org/browse/JBIDE-16640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.2.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6)
> Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803)
> Only one of the following can be installed at once:
> Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656)
> Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453)
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803)
> To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803]
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803)
> To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000)
> To: org.eclipse.ui.browser [3.4.100.v20130527-1656]
> Cannot satisfy dependency:
> From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6)
> To: bundle org.eclipse.ui.browser 3.4.200
> Cannot satisfy dependency:
> From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6)
> To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6]
> {code}
> AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-16640:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Avoid bumping dependencies versions unless it is required
> ---------------------------------------------------------
>
> Key: JBIDE-16640
> URL: https://issues.jboss.org/browse/JBIDE-16640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.2.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6)
> Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803)
> Only one of the following can be installed at once:
> Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656)
> Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453)
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803)
> To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803]
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803)
> To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000)
> To: org.eclipse.ui.browser [3.4.100.v20130527-1656]
> Cannot satisfy dependency:
> From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6)
> To: bundle org.eclipse.ui.browser 3.4.200
> Cannot satisfy dependency:
> From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6)
> To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6]
> {code}
> AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200.
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17748?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17748:
---------------------------------------
Created https://github.com/angelozerr/tern.java/pull/95
> 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-17766) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17766?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-17766:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Arquillian]
> --------------------------------------------------------
>
> Key: JBIDE-17766
> URL: https://issues.jboss.org/browse/JBIDE-17766
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Arquillian]: 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 Arquillian 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] (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 reassigned JBIDE-17768:
-------------------------------------
Assignee: Snjezana Peco
> 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] (JBIDE-17762) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17762?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-17762:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Birt]
> --------------------------------------------------
>
> Key: JBIDE-17762
> URL: https://issues.jboss.org/browse/JBIDE-17762
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Birt]: 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 Birt 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