[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:
-------------------------------
Fix Version/s: 4.4.4.AM3
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1066) Release JBTIS 4.4.2.Final/ DevstudioIS 10.2.0.GA
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1066:
---------------------------------
Summary: Release JBTIS 4.4.2.Final/ DevstudioIS 10.2.0.GA
Key: JBTIS-1066
URL: https://issues.jboss.org/browse/JBTIS-1066
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Affects Versions: 4.4.2.Final, 10.2.0.GA
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.4.2.Final, 10.2.0.GA
Release JBTIS 4.4.2.Final/ DevstudioIS 10.2.0.GA
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24129?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24129:
----------------------------------
Assignee: Pavol Srna (was: Nick Boldt)
> download-devstudio profile breaks component builds
> --------------------------------------------------
>
> Key: JBIDE-24129
> URL: https://issues.jboss.org/browse/JBIDE-24129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Priority: Critical
> Fix For: 4.4.4.AM2
>
>
> We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently.
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24129?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24129 at 3/27/17 12:12 PM:
--------------------------------------------------------------
Since the parent pom [1] profile *download-devstudio* points at devstudioRepository = https://devstudio.redhat.com/10.0/snapshots/updates/ to perform repository resolution, you may encounter situations where the test is running and the upstream site CHANGES during the test.
[1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
For example, the error you're seeing talks about
{code}org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]'{code}
But in the site the current version is newer:
{code}org.jboss.ide.eclipse.as.feature.feature.group 3.2.4.v20170324-1941{code}
So... do you need to depend on the latest STAGING site for stability? Or just trigger the job to run again, if it fails?
was (Author: nickboldt):
Since the parent pom profile *download-devstudio* points at devstudioRepository = https://devstudio.redhat.com/10.0/snapshots/updates/ to perform repository resolution, you may encounter situations where the test is running and the upstream site CHANGES during the test.
For example, the error you're seeing talks about
{code}org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]'{code}
But in the site the current version is newer:
{code}org.jboss.ide.eclipse.as.feature.feature.group 3.2.4.v20170324-1941{code}
So... do you need to depend on the latest STAGING site for stability? Or just trigger the job to run again, if it fails?
> download-devstudio profile breaks component builds
> --------------------------------------------------
>
> Key: JBIDE-24129
> URL: https://issues.jboss.org/browse/JBIDE-24129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.4.AM2
>
>
> We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently.
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24129?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24129:
------------------------------------
Since the parent pom profile *download-devstudio* points at devstudioRepository = https://devstudio.redhat.com/10.0/snapshots/updates/ to perform repository resolution, you may encounter situations where the test is running and the upstream site CHANGES during the test.
For example, the error you're seeing talks about
{code}org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]'{code}
But in the site the current version is newer:
{code}org.jboss.ide.eclipse.as.feature.feature.group 3.2.4.v20170324-1941{code}
So... do you need to depend on the latest STAGING site for stability? Or just trigger the job to run again, if it fails?
> download-devstudio profile breaks component builds
> --------------------------------------------------
>
> Key: JBIDE-24129
> URL: https://issues.jboss.org/browse/JBIDE-24129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.4.AM2
>
>
> We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently.
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4328) Move 'Detection is in progress' indicator in the middle of the screen and make it easy to see
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4328:
-----------------------------------
Summary: Move 'Detection is in progress' indicator in the middle of the screen and make it easy to see
Key: JBDS-4328
URL: https://issues.jboss.org/browse/JBDS-4328
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.4.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.4.0.AM3
With scrolling in place it is not easy to notice that detection is in progress. It should be always in the middle of the windows, it should be bigger and easy to see.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4327) DevStudio Detection
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4327:
-----------------------------------
Summary: DevStudio Detection
Key: JBDS-4327
URL: https://issues.jboss.org/browse/JBDS-4327
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.4.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 11.0.0.AM1
Installer should detect installed DevStudio, detect and validate it's version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3635:
--------------------------------
Epic Name: Installed Components Detection
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc, ui
> Fix For: 10.4.0.AM2
>
> Attachments: Technologies 5.pdf, pdkinstaller.png
>
>
> Generic rules for detection and validation are:
> 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio;
> 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition.
> vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems;
> virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning;
> jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning;
> 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location;
> 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use.
> 5. When location for required software set manually installer try will try detect version and verify it using (2);
> 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning.
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years