[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18815:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Include freemarker.jar in FreeMarker IDE as maven dependency
> ------------------------------------------------------------
>
> Key: JBIDE-18815
> URL: https://issues.jboss.org/browse/JBIDE-18815
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19183) Constant AssertionFailedExceptions from FreeMarker Editor
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19183?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19183:
----------------------------------
Fix Version/s: 4.3.0.Beta1
> Constant AssertionFailedExceptions from FreeMarker Editor
> ---------------------------------------------------------
>
> Key: JBIDE-19183
> URL: https://issues.jboss.org/browse/JBIDE-19183
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.3.0.Alpha1
> Environment: Eclipse 4.4.1
> Linux
> Reporter: Eric Sirianni
> Fix For: 4.3.0.Beta1
>
>
> I get constant "assertion failed" errors in the freemarker editor. The error is associated with the following stack trace in my eclipse log:
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2015-02-06 12:28:37.974
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.jface.text.Position.setLength(Position.java:185)
> at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634)
> at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430)
> at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431)
> at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451)
> at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569)
> at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567)
> at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227)
> at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830)
> at org.eclipse.jface.text.TextViewer.invalidateTextPresentation(TextViewer.java:3501)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.resetRange(Editor.java:282)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.highlightRelatedRegions(Editor.java:257)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.handleCursorPositionChanged(Editor.java:174)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.mouseUp(Editor.java:200)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> {noformat}
> This happens across multiple FreeMarker templates, all with very basic syntax.
> I am using version 1.4.1.Final of the FreeMarker plugin.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19183) Constant AssertionFailedExceptions from FreeMarker Editor
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19183?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19183:
----------------------------------
Affects Version/s: 4.3.0.Alpha1
> Constant AssertionFailedExceptions from FreeMarker Editor
> ---------------------------------------------------------
>
> Key: JBIDE-19183
> URL: https://issues.jboss.org/browse/JBIDE-19183
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.3.0.Alpha1
> Environment: Eclipse 4.4.1
> Linux
> Reporter: Eric Sirianni
> Fix For: 4.3.0.Beta1
>
>
> I get constant "assertion failed" errors in the freemarker editor. The error is associated with the following stack trace in my eclipse log:
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2015-02-06 12:28:37.974
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.jface.text.Position.setLength(Position.java:185)
> at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634)
> at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430)
> at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431)
> at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451)
> at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569)
> at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567)
> at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227)
> at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830)
> at org.eclipse.jface.text.TextViewer.invalidateTextPresentation(TextViewer.java:3501)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.resetRange(Editor.java:282)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.highlightRelatedRegions(Editor.java:257)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.handleCursorPositionChanged(Editor.java:174)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.mouseUp(Editor.java:200)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> {noformat}
> This happens across multiple FreeMarker templates, all with very basic syntax.
> I am using version 1.4.1.Final of the FreeMarker plugin.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3208:
-------------------------------------------
I do not follow the need/wish to change the schema from what was agreed on. what am I missing here ?
If I read it right this now means /builds is *under* updatesite urls instead of being *next* to it. why do we want that ?
and we have nothing against having pre-GA point to the empty stable folder - thats what we agreed on a while ago since that makes it much simpler.
I've never thought we should have the p2.inf in there - its a broken concept. We have a jira on improving this situation by letting ide.properties tell eclipse to
suggest user to add a dev updatesite until GA is out.
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
[~mickael_istria] got a bugzilla or jira for that issue we can link to this as known issue?
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3208:
----------------------------------
FYI, I've shortformed the URLs for JBDS update sites.
Instead of devstudio.redhat.com/9.0/stable/updates/ and devstudio.redhat.com/9.0/development/updates/ we can drop the additional "/updates/" segment and just composite from the parent folder. Thus:
* devstudio.redhat.com/9.0/development/
* devstudio.redhat.com/9.0/stable/
Should people ( [~maxandersen] [~burrsutter] [~mickael_istria] [~dgolovin] ) want to simplify further, we could make devstudio.redhat.com/9.0/ a composite of devstudio.redhat.com/9.0/stable/ to drop another path segment.
Details: https://github.com/jbdevstudio/jbdevstudio-product/pull/297
If we don't mind having the pre-GA builds point to the empty /stable/ site during the development of the milestones, we could drop out all the cruft in the p2.inf file [1] and just simplify things further. But it means that users will have to manually need to add the /development/ site to their JBDS Alpha or Beta build to get updates before we GA.
[1] https://github.com/nickboldt/jbdevstudio-product/blob/JBDS-3208_fixUpdate...
FYI to [~pleacu] - when it's time to stage the JBDS IS stuff, look in /9.0/staging/ not /updates/9.0-staging/ for your stuff.
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3208:
--------------------------------
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
CDW release: + (was: ?)
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3208:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: +
CDW qa_ack: ?
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 9.0.0.GA
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19386) Content assist for <* class=""> in Batch Job XML files.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19386:
-----------------------------------
Description:
Works for all class="" attributes.
For example:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<job id="myJob" xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="1.0">
<step id="step1">
<chunk>
<retryable-exception-classes>
<exclude class="excepT"/>
</retryable-exception-classes>
<no-rollback-exception-classes>
<exclude class="runtimee"/>
</no-rollback-exception-classes>
<skippable-exception-classes>
<include class="java.lang.Excep"/>
</skippable-exception-classes>
</chunk>
</step>
</job>
{code}
Limitations:
- Content assist doesn't work for empty strings. You have to type at least the first character in the class="<any_character>" before invoke the content assist.
- Content assist may not show all available classes if java indexing is not completed yet.
!scr.png!
was:!scr.png!
> Content assist for <* class=""> in Batch Job XML files.
> -------------------------------------------------------
>
> Key: JBIDE-19386
> URL: https://issues.jboss.org/browse/JBIDE-19386
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: scr.png
>
>
> Works for all class="" attributes.
> For example:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <job id="myJob" xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="1.0">
> <step id="step1">
> <chunk>
> <retryable-exception-classes>
> <exclude class="excepT"/>
> </retryable-exception-classes>
> <no-rollback-exception-classes>
> <exclude class="runtimee"/>
> </no-rollback-exception-classes>
> <skippable-exception-classes>
> <include class="java.lang.Excep"/>
> </skippable-exception-classes>
> </chunk>
> </step>
> </job>
> {code}
> Limitations:
> - Content assist doesn't work for empty strings. You have to type at least the first character in the class="<any_character>" before invoke the content assist.
> - Content assist may not show all available classes if java indexing is not completed yet.
> !scr.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-18950:
----------------------------------
Attachment: BatchArtifactWizBan.png
BatchArtifact.png
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: BatchArtifact.png, BatchArtifactWizBan.png
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3285:
--------------------------------------
Thanks [~nickboldt] and [~gercan] for fixing the integration with Thym.
Unfortunately, a NPE prevents the integration with EGit to work. The issue is now fixed in last snapshot of the importer framework, but it isn't in JBT/JBDS TP. So the only way to run when using branch builds is to clone the Git repo in one step (from CLI for example), and to import the folder in another step...
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15108) "Failed while installing JPA 2.0" during importing multi-module maven project
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15108?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-15108.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.2.x)
Resolution: Cannot Reproduce Bug
Can't reproduce with latest m2e-wtp/JBDS version. Please reopen if you bump into that bug
> "Failed while installing JPA 2.0" during importing multi-module maven project
> -----------------------------------------------------------------------------
>
> Key: JBIDE-15108
> URL: https://issues.jboss.org/browse/JBIDE-15108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Beta2, 4.2.0.Beta1
> Environment: JBDS 7.0.Beta2
> Reporter: Marek Schmidt
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> "Failed while installing JPA 2.0." occurs when importing a multi-module maven project.
> """
> Failed while installing JPA 2.0.
> org.osgi.service.prefs.BackingStoreException: Resource '/jboss-as-ejb-in-ear/ejb/.settings' does not exist.
> """
> The error goes away after subsequent import, as, presumably, the error doesn't occur after the .settings file already exists.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-19338.
------------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Beta1)
Resolution: Cannot Reproduce Bug
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Alpha2
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19425) Error when loading projects in Central with Java 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19425:
--------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Error when loading projects in Central with Java 9
> --------------------------------------------------
>
> Key: JBIDE-19425
> URL: https://issues.jboss.org/browse/JBIDE-19425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Labels: Java9
> Fix For: LATER
>
>
> Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central.
> When I started JBDS, I immediately got an error window pop up:
> {code}
> Refreshing JBoss Tutorials... has encountered a problem.
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> javax/xml/bind/JAXBException
> {code}
> This is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 5 more
> {code}
> I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9:
> {code}
> nattura:9.0.0 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b53)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode)
> {code}
> The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found".
> Note: When I installed the same JBDS with Java 8, there was no error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-2945) Unable to import Maven project from Git perspective
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2945?page=com.atlassian.jira.plugin.... ]
Fred Bricon closed JBDS-2945.
-----------------------------
Resolution: Duplicate Issue
This issue is superseded by JBDS-3285 (Easymport)
> Unable to import Maven project from Git perspective
> ---------------------------------------------------
>
> Key: JBDS-2945
> URL: https://issues.jboss.org/browse/JBDS-2945
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 7.1.0.GA
> Reporter: Jozef Hartinger
> Fix For: LATER
>
>
> I am roughly following these steps https://community.jboss.org/wiki/AdvancedJavaEELabjaro2014 to import a project from a Git repository.
> I firstly use the Git perspective to clone a remote repository.
> Then, still in the Git perspective when I right-click on the "Working directory" there is an option to "Import projects". However, this option only allows for eclipse or general projects to be imported. A Maven project is not recognized.
> I am aware of other ways of importing the Maven project. However, I think that Maven should be supported consistently across all the "import-project-like" dialogs, not only some of them.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18837.
---------------------------------
Assignee: Nick Boldt (was: Fred Bricon)
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
Resolution: Done
PR applied in master
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: generated-vs-soource-zip.png
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19627) OpenShift features disable workspace selection
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19627:
----------------------------------------
Thw following experiment shows that this issue comes with OpenShift:
1. Get fresh Mars M6 JEE, start => it asks for workpsace
2. Install all JBoss Tools Abriged except OpenShift features, close IDE, restart (manually) => it asks for workspace
3 Additionally, install OpenShift features, close IDE, restart (manually) => it doesn't ask for workspace and selects automatically $HOME/workspace.
[~adietish] [~jcantrill] Enjoy!
> OpenShift features disable workspace selection
> ----------------------------------------------
>
> Key: JBIDE-19627
> URL: https://issues.jboss.org/browse/JBIDE-19627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, Mac OS X
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X.
> This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 .
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19350:
-------------------------------------
Yes, I know... but I haven't replicated such a bug yet.
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3414) remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3414?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3414:
-----------------------------
Steps to Reproduce: (was: Steps to Verify:
1. EXECUTE: Install/Start JBDS
2. ASSERT: Welcome screen is present
3. ASSERT: Help -> About JBoss Developer Studio menu is presen
4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text
5. ASSERT: JBDS Icon present in installed features icons list)
> remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
> -----------------------------------------------------------------------------
>
> Key: JBDS-3414
> URL: https://issues.jboss.org/browse/JBDS-3414
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> p2.inf files were created to support name change from com.jboss.jbds.product.feature.source to com.jboss.devstudio.core.feature.source and support name change from com.jboss.jbds.product.feature to com.jboss.devstudio.core.feature. Since we're on JBDS 9 and it can't be updated from 8, this instruction is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3414) remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3414?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3414:
-----------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 8.0.0.Alpha2)
> remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
> -----------------------------------------------------------------------------
>
> Key: JBDS-3414
> URL: https://issues.jboss.org/browse/JBDS-3414
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> p2.inf files were created to support name change from com.jboss.jbds.product.feature.source to com.jboss.devstudio.core.feature.source and support name change from com.jboss.jbds.product.feature to com.jboss.devstudio.core.feature. Since we're on JBDS 9 and it can't be updated from 8, this instruction is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3414) remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3414?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3414:
-----------------------------
Fix Version/s: 9.0.0.Beta1
(was: 9.0.0.Alpha2)
> remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)
> -----------------------------------------------------------------------------
>
> Key: JBDS-3414
> URL: https://issues.jboss.org/browse/JBDS-3414
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> p2.inf files were created to support name change from com.jboss.jbds.product.feature.source to com.jboss.devstudio.core.feature.source and support name change from com.jboss.jbds.product.feature to com.jboss.devstudio.core.feature. Since we're on JBDS 9 and it can't be updated from 8, this instruction is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-355:
----------------------------------
It's probably better to iron out any EM issues now - then we can just update things when Fuse Tooling is released. Plus SwitchYard is now separate from Fuse so there will be 2 more releases after 8.0.1.
I'll clear out the path parameter from the category XML feature definition.
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19590:
------------------------------------
Set component, fixversion and assignee because jiralint.
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, website
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.x
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19590:
-------------------------------
Component/s: build
website
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, website
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Fix For: 4.3.x
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19590:
-------------------------------
Fix Version/s: 4.3.x
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, website
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Fix For: 4.3.x
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19590:
----------------------------------
Assignee: Max Rydahl Andersen
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, website
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.x
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-355:
----------------------------------
I thought you wanted to wait until JBDSIS 8.0.2 was live, with the complete stack available.
Also, you can remove path="..." from your category.xml files as they provide no value to Tycho when building. Not 100% sure what happens when you refer to things OUTSIDE the local folder, but fairly sure that Tycho can find them in the reactor or the local ~/.m2/repo.
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBDS-3249:
--------------------------------
Assignee: Paul Leacu
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 8.1.0.GA, 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-355:
----------------------------------
[~nickboldt] - these two hidden container features are now available (B*MS and JDV) in JBDSIS 8.0.1.GA:
{code}
<feature id="com.jboss.devstudio.integration-stack.bpr.feature" path="../../devstudio/site-ga/com.jboss.devstudio.integration-stack.bpr.feature"/>
<feature id="com.jboss.devstudio.integration-stack.ds.feature" path="../../devstudio/site-ga/com.jboss.devstudio.integration-stack.ds.feature"/>
{code}
*at your convenience* - can we see what it will take to get thse in Eclipse Marketplace? Thkx
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBDS-3393.
----------------------------
Resolution: Rejected
Not a bug - the EA banner does not show up when performing just the released/ production install.
> Early Access Enabled banner appears w/out EA content installed
> --------------------------------------------------------------
>
> Key: JBDS-3393
> URL: https://issues.jboss.org/browse/JBDS-3393
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.1.0.CR1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Attachments: ss1.png, ss2.png, x1.png
>
>
> 1. Start w/ Eclipse JEE Luna SR2
> 2. Install JBDS 8.0.2
> 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1
> Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and
> in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png
> Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't
> yet enabled early access. ref ss2.png. The plugin.xmls are here:
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19632) Use of default server for a new OpenShift connection does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19632?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19632:
----------------------------------
Summary: Use of default server for a new OpenShift connection does not work (was: Use default server for a new OpenShift connection does not work)
> Use of default server for a new OpenShift connection does not work
> ------------------------------------------------------------------
>
> Key: JBIDE-19632
> URL: https://issues.jboss.org/browse/JBIDE-19632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Labels: connection_wizard
>
> There is a checkbox to use default server for a new OpenShift connection in new connection wizard. Previously, after checking it the field with default server has become uneditable and default server was set there.
> Currently after checking the checkbox for default server, its field is uneditable (grayed), but the old value stay there. After filling credentials (username, password) and using checked default server the connection is not established, because there is used value from text field which is inactive and not default server.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19632) Use default server for a new OpenShift connection does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-19632:
-------------------------------------
Summary: Use default server for a new OpenShift connection does not work
Key: JBIDE-19632
URL: https://issues.jboss.org/browse/JBIDE-19632
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Marián Labuda
There is a checkbox to use default server for a new OpenShift connection in new connection wizard. Previously, after checking it the field with default server has become uneditable and default server was set there.
Currently after checking the checkbox for default server, its field is uneditable (grayed), but the old value stay there. After filling credentials (username, password) and using checked default server the connection is not established, because there is used value from text field which is inactive and not default server.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19632) Use default server for a new OpenShift connection does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19632?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19632:
----------------------------------
Labels: connection_wizard (was: )
> Use default server for a new OpenShift connection does not work
> ---------------------------------------------------------------
>
> Key: JBIDE-19632
> URL: https://issues.jboss.org/browse/JBIDE-19632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Labels: connection_wizard
>
> There is a checkbox to use default server for a new OpenShift connection in new connection wizard. Previously, after checking it the field with default server has become uneditable and default server was set there.
> Currently after checking the checkbox for default server, its field is uneditable (grayed), but the old value stay there. After filling credentials (username, password) and using checked default server the connection is not established, because there is used value from text field which is inactive and not default server.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ]
Jiri Peterka edited comment on JBIDE-19190 at 4/17/15 7:12 AM:
---------------------------------------------------------------
[~max]. No problem to change a repo structure. However Max, right now VWatch contains additional JBDS installation scripts. Is it ok to keep them in jbosstools repo? If not then jenkins jobs will have to clone two repositories, one for VWatch and one for JBDS scripts.
was (Author: jpeterka):
[~max]. No problem to change a repo structure. However Max, right now VWatch contains additional JBDS installation scripts. Is it ok to keep them in jbosstools repo? If not then jenkins jobs will have to clone two repositories, one for VWatch and one for JBDS scripts?
> migrate VersionWatch to jbosstools-* repo
> -----------------------------------------
>
> Key: JBIDE-19190
> URL: https://issues.jboss.org/browse/JBIDE-19190
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly.
> 1. remove all refs to QA Jenkins file paths to make this more generic
> 2. migrate those internal file paths into jenkins config.xml files
> 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19190:
--------------------------------------
[~max]. No problem to change a repo structure. However Max, right now VWatch contains additional JBDS installation scripts. Is it ok to keep them in jbosstools repo? If not then jenkins jobs will have to clone two repositories, one for VWatch and one for JBDS scripts?
> migrate VersionWatch to jbosstools-* repo
> -----------------------------------------
>
> Key: JBIDE-19190
> URL: https://issues.jboss.org/browse/JBIDE-19190
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly.
> 1. remove all refs to QA Jenkins file paths to make this more generic
> 2. migrate those internal file paths into jenkins config.xml files
> 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19350:
---------------------------------------------
if there is a bug in the libraries we are using (wildfly client jars) our responsibility is at least to report them so they can become aware and potentially fix it.
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17814) Empty editor is opened instead of Central editor
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17814?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-17814:
------------------------------------
I tried it again with JBDS 9 nightly (Alpha2-v20150414-2227-B2953) and issue is still present. I'm not sure it it's worth it to spend any more time on this as Central will be refactored in Beta1.
> Empty editor is opened instead of Central editor
> ------------------------------------------------
>
> Key: JBIDE-17814
> URL: https://issues.jboss.org/browse/JBIDE-17814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta3
> Environment: Fedora 20
> Reporter: Radim Hopp
> Assignee: Radim Hopp
> Fix For: 4.2.x, 4.3.0.Alpha2
>
> Attachments: central2.ogv
>
>
> I seems to appear only with repetitive closing/opening Central editor.
> Screencast: http://youtu.be/Z_X_Eo76wV8
> I can reproduce this issue even with GTK2.
> There is no error in error log nor in console output.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19496) docker run wizard
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-19496:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> docker run wizard
> -----------------
>
> Key: JBIDE-19496
> URL: https://issues.jboss.org/browse/JBIDE-19496
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Beta1
>
> Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png
>
>
> should have a docker wizard to easily run images.
> The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases.
> For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-19564:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Use background job to detect default connection settings
> --------------------------------------------------------
>
> Key: JBIDE-19564
> URL: https://issues.jboss.org/browse/JBIDE-19564
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Beta1
>
>
> In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19338:
-------------------------------------
Unable to replicate on the same environment I used when reporting this Jira. Seems that my PC was in some strange conditions now it works fine. Probably we can mark this one as Unable to replicate.
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19338:
-------------------------------------
Unable to replicate on Fedora 21 Gnome with JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19607) Offline quickstarts not working - Could not calculate build plan
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19607?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-19607.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
I could reproduce while running the script with a Maven version different from the Maven embedder version, used by m2e. This version mismatch causes plugins dependencies to be missing when running in Eclipse.
In order to mitigate the problem, I forced the script to use the maven wrapper, which, for now, uses the same Maven version as m2e (3.3.1). I'll try to make it more robust later.
> Offline quickstarts not working - Could not calculate build plan
> ----------------------------------------------------------------
>
> Key: JBIDE-19607
> URL: https://issues.jboss.org/browse/JBIDE-19607
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0 nightly build Alpha2-v20150414-2227-B2953
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> After running offline script and configuring JBDS to use that (without internet connectivity) I'm unable to import any of quickstarts. Some (as HTML5 project archetype for example) throw error into error log right after wizard startup:
> {noformat:title=Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final}
> org.eclipse.core.runtime.CoreException: Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:776)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:753)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
> After hitting Finish on wizard, the imported project (if it was imported) cannot be build, because it cannot resolve maven-resources-plugin. Error log:
> {noformat:title=Errors occurred during the build.}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build.
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:498)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: Errors running builder 'Maven Project Builder' on project 'jboss-greeter'.
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 30 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> Contains: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> {noformat}
> Note, that all artifacts that eclipse cannot resolve (maven-resources-plugin, HTML5 archetype, ...) I have in my local repository (were downloaded by offline script correctly). I checked few sha1 checksums and they are correct.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19350.
---------------------------------
Resolution: Done
So long as this bug was mostly about not being able to cancel, and frozen progress monitors, I'd say it's fixed.
If there's a bug regarding the transfer itself freezing, I guess another bug should be opened, but I'm not really sure that's my responsibility, since I just use their API client jars and stuff...
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19350:
-------------------------------------
https://github.com/jbosstools/jbosstools-server/pull/339
I've been seriously completely unable to replicate any actual freezing in terms of the transfer stopping, despite several hours of trying. Obviously the progress monitor froze, but I can't replicate the transfer itself freezing.
Either way, this PR now allows for more cancels and an infinite-progress-bar during the transfer portion.
Pushing to 4.3.0.Alpha2 for further consumption but as far as I can tell it works for me.... and I tested on a deployment that was 1.7 gigabytes, though I did test with a local docker image (so tools thought was remote).
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19613) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19613?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19613.
------------------------------
Resolution: Done
Thanks for branching, [~rob.stryker]. Can you also close your JIRAs when they're done? kthxbai.
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-19613
> URL: https://issues.jboss.org/browse/JBIDE-19613
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19613) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19613?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19613:
----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-19613
> URL: https://issues.jboss.org/browse/JBIDE-19613
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-3354:
-----------------------------------
What is keeping us from removing Seam 3 tools?
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3404:
--------------------------------
CDW devel_ack: + (was: ?)
CDW qa_ack: + (was: ?)
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3404:
-----------------------------
CDW release: + (was: ?)
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3404:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: +
CDW qa_ack: ?
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3404:
--------------------------------
CDW release: ?
Status: New (was: New)
Target Release: 9.0.0.GA
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19616) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-19616.
------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift]
> --------------------------------------------------------
>
> Key: JBIDE-19616
> URL: https://issues.jboss.org/browse/JBIDE-19616
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3354:
-----------------------------------
Alpha2 no longer has the bulk of Seam plugins, but still contains org.jboss.tools.jsf.vpe.seam.
This is caused by the org.jboss.tools.jsf.feature referencing it. We should severe that dependency and move org.jboss.tools.jsf.vpe.seam under the seam module for Beta1
We also still need to decide what to do with seam3 tools
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3354:
------------------------------
Fix Version/s: 9.0.0.Beta1
(was: 9.0.0.Alpha2)
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years