[JBoss JIRA] (JBTIS-1076) cannot install Fuse Tools - bad URL in discovery site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1076?page=com.atlassian.jira.plugin... ]
Nick Boldt updated JBTIS-1076:
------------------------------
Attachment: jbtis-dev-site-links-to-staging-site-which-has-been-moved.png
> cannot install Fuse Tools - bad URL in discovery site
> -----------------------------------------------------
>
> Key: JBTIS-1076
> URL: https://issues.jboss.org/browse/JBTIS-1076
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, Fuse IDE
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Attachments: jbtis-dev-site-links-to-staging-site-which-has-been-moved.png
>
>
> 1. install eclipse Neon.3 JEE bundle.
> 2. install everything from JBT staging site (4.4.4.AM2):
> http://download.jboss.org/jbosstools/neon/staging/updates/
> 3. Enable early access, then install everything from Central.
> 4. On restart, JBoss Fuse Development connector is not installed. Select it and attempt to install:
> {code}
> Problems occurred while performing installation: The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...)
> The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...
> Also got this:
> {code}
> No repository found at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1076) cannot install Fuse Tools - bad URL in discovery site
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1076?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1076:
---------------------------------
Assignee: Paul Leacu
> cannot install Fuse Tools - bad URL in discovery site
> -----------------------------------------------------
>
> Key: JBTIS-1076
> URL: https://issues.jboss.org/browse/JBTIS-1076
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, Fuse IDE
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> 1. install eclipse Neon.3 JEE bundle.
> 2. install everything from JBT staging site (4.4.4.AM2):
> http://download.jboss.org/jbosstools/neon/staging/updates/
> 3. Enable early access, then install everything from Central.
> 4. On restart, JBoss Fuse Development connector is not installed. Select it and attempt to install:
> {code}
> Problems occurred while performing installation: The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...)
> The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...
> Also got this:
> {code}
> No repository found at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1076) cannot install Fuse Tools - bad URL in discovery site
by Nick Boldt (JIRA)
Nick Boldt created JBTIS-1076:
---------------------------------
Summary: cannot install Fuse Tools - bad URL in discovery site
Key: JBTIS-1076
URL: https://issues.jboss.org/browse/JBTIS-1076
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution, Fuse IDE
Affects Versions: 4.4.2.Final
Reporter: Nick Boldt
1. install eclipse Neon.3 JEE bundle.
2. install everything from JBT staging site (4.4.4.AM2):
http://download.jboss.org/jbosstools/neon/staging/updates/
3. Enable early access, then install everything from Central.
4. On restart, JBoss Fuse Development connector is not installed. Select it and attempt to install:
{code}
Problems occurred while performing installation: The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...)
The following connectors are not available: JBoss Fuse Development (id=org.fusesource.ide.camel.editor.feature.feature.group, org.fusesource.ide.core.feature.feature.group, org.fusesource.ide.jmx.feature.feature.group, org.fusesource.ide.server.extensions.feature.feature.group, org.jboss.tools.fuse.transformation.feature.feature.group, org.switchyard.tools.feature.feature.group, org.switchyard.tools.bpel.feature.feature.group, org.switchyard.tools.bpmn2.feature.feature.group, site=http://download.jboss.org/jbosstools/neon/development/updates/integr...
Also got this:
{code}
No repository found at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ]
Paul Leacu resolved JBTIS-1067.
-------------------------------
Resolution: Done
Updated stable site and Jenkins jobs.
> Clean update site files for stable/development/staging branch
> -------------------------------------------------------------
>
> Key: JBTIS-1067
> URL: https://issues.jboss.org/browse/JBTIS-1067
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.2.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Please clean update site files in stable/development/staging branch so that there are only html and p2 files at
> {code}
> /www_htdocs/devstudio/10.0/stable/updates/integration-stack/
> {code}
> and all binaries are in relevant folders such as
> {code}
> /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/
> {code}
> Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following
> || What we are working on? || Obsolete files || Files I'd like to keep ||
> | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA|
> EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24135:
-------------------------------
Sprint: devex #130 April 2017 (was: devex #129 March 2017)
> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
> Key: JBIDE-24135
> URL: https://issues.jboss.org/browse/JBIDE-24135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.4.4.AM3
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created.
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24025) AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24025?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24025:
-------------------------------------
Fix Version/s: 4.5.0.AM1
> AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder
> ---------------------------------------------------------------------
>
> Key: JBIDE-24025
> URL: https://issues.jboss.org/browse/JBIDE-24025
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.4.4.AM3, 4.5.0.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDefaultDeployFolder(ExpressServerUtils.java:292)
> at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:264)
> at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:260)
> at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection.initWidgets(ExpressServerEditorSection.java:122)
> at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection$1.run(ExpressServerEditorSection.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.1.v20160907-0248 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.9.0.v201610211907 |
> | org.jboss.tools.openshift.express.core | 3.1.0.Final-v20160414-0041-B272 | 3.3.2.v20170119-1710 |
> | org.jboss.tools.openshift.express.ui | 3.1.0.Final-v20160414-0041-B272 | 3.3.1.v20161003-1104 |
> Operating Systems:
> | Linux | 3.13.0 | 3.13.0 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/56df0c0fe4b0e0c18a6... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years