[JBoss JIRA] (JBDS-3986) support building devstudio on windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3986?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3986:
----------------------------------
If we remove the need to build a sources zip entirely ( https://trello.com/c/OhNmvELX/4-remove-jbds-sources-zip-from-list-of-deli... ) then we can disable the step that fetches the upstream github zips to package them into a sources zip.
That would eliminate the problem of the '\tmp\jbdevstudio-product-bd00bc238f6d35b895b182cdfe07da5e6b62a215.zip' stuff.
I tried to remove this for 10.0 and it confused PgM so it remained. Then for 10.1 release-engineering decided to do the same thing that was done for 10.0 - provide a link to github AND the sources zip.
Do we want to push to have the source zip removed for 10.2? or 11.0?
> support building devstudio on windows
> -------------------------------------
>
> Key: JBDS-3986
> URL: https://issues.jboss.org/browse/JBDS-3986
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 10.1.0.AM3
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> Support building devstudio on windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4076?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4076:
-----------------------------
Fix Version/s: 10.2.0.AM2
> "RPM release" mismatch between src.rpm and x86_64.rpm
> -----------------------------------------------------
>
> Key: JBDS-4076
> URL: https://issues.jboss.org/browse/JBDS-4076
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> This is an issue with upcoming rh-eclipse46-devstudio.rpm.
> Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains:
> rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files.
> The SOURCERPM info in the RPM is broken as well:
> {{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-430) Support insecure connection to pull an image [EBZ#504069]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-430:
---------------------------------------
Summary: Support insecure connection to pull an image [EBZ#504069]
Key: ERT-430
URL: https://issues.jboss.org/browse/ERT-430
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Priority: Trivial
When you are in a VPN, the security check might be disabled and we need to activate --insecure-registry.
it would be nice to add the option in "Add registry account" to avoid modifying the docker daemon (which is quite complicated)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-846) Productize the JBDSIS/DevstudioIS stand-alone installers
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-846?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-846:
-----------------------------
Description:
The Integration Stack devstudio pom can now build a stand-alone installer in addition to update site ZIP files. Modify any/all Jenkins jobs, product.yml, CSP RCM ticket instructions to handle the productization of the installer.
Mars:
https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... (MD5)
*Release Engineering CSP update instructions - Developer Studio Integration Stack 9.0.2.GA:*
{code}
Please remove earlier versions of Red Hat JBoss Developer Studio Integration Stack update site zips.
When pushed, please reply so that QE can review the CSP pages & CDN/Download Manager files for push to production.
_________________________________________________________________________________________
Please add the following stand-alone installer [1] to the 9.1.0 JBoss Developer Studio product pulldown in the CSP Software Downloads page [2].
[1] https://devstudio.redhat.com/9.0/stable/builds/installer/integration-stac... [Open URL] (MD5)
[2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...
Associated JIRA: https://issues.jboss.org/browse/JBTIS-846
Descriptive copy to associate w/ the CSP entry:
-----------------------------------------------
Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Stand-Alone Installer
Detailed Description
This installer contains JBoss Developer Studio 9.1.0.GA and JBoss Developer Studio Integration Stack tooling 9.0.2.GA.
Manual Instructions
java -jar jboss-devstudio-is-9.0.2.GA-installer-standalone.jar
_________________________________________________________________________________________
Please add the following update site zip file to the JBoss Developer Studio product pulldown in the CSP Software Downloads page:
https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... [Open URL] (MD5)
Descriptive copy to associate w/ the CSP entry:
-----------------------------------------------
Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Update Site Zip
Detailed Description
This release zip has been certified for JBoss Developer Studio 9.1.0.GA.
Manual Instructions
1. Start jbdevstudio
2. Select the Help > Install New Software...
3. Select Add...
4. Select Archive...
5. Supply the zip file location as the repository archive.
{code}
was:
The Integration Stack devstudio pom can now build a stand-alone installer in addition to update site ZIP files. Modify any/all Jenkins jobs, product.yml, CSP RCM ticket instructions to handle the productization of the installer.
Mars:
https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... (MD5)
*Release Engineering CSP update instructions - Developer Studio Integration Stack 9.0.2.GA:*
{code}
Please remove earlier versions of Red Hat JBoss Developer Studio Integration Stack update site zips.
When pushed, please reply so that QE can review the CSP pages & CDN/Download Manager files for push to production.
_________________________________________________________________________________________
Please add the following stand-alone installer [1] to the 9.1.0 JBoss Developer Studio product pulldown in the CSP Software Downloads page [2].
[1] https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... [Open URL] (MD5)
[2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...
Associated JIRA: https://issues.jboss.org/browse/JBTIS-846
Descriptive copy to associate w/ the CSP entry:
-----------------------------------------------
Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Stand-Alone Installer
Detailed Description
This installer contains JBoss Developer Studio 9.1.0.GA and JBoss Developer Studio Integration Stack tooling 9.0.2.GA.
Manual Instructions
java -jar jboss-devstudio-is-9.0.2.GA-installer-standalone.jar
_________________________________________________________________________________________
Please add the following update site zip file to the JBoss Developer Studio product pulldown in the CSP Software Downloads page:
https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... [Open URL] (MD5)
Descriptive copy to associate w/ the CSP entry:
-----------------------------------------------
Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Update Site Zip
Detailed Description
This release zip has been certified for JBoss Developer Studio 9.1.0.GA.
Manual Instructions
1. Start jbdevstudio
2. Select the Help > Install New Software...
3. Select Add...
4. Select Archive...
5. Supply the zip file location as the repository archive.
{code}
> Productize the JBDSIS/DevstudioIS stand-alone installers
> --------------------------------------------------------
>
> Key: JBTIS-846
> URL: https://issues.jboss.org/browse/JBTIS-846
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.2.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.2.GA
>
>
> The Integration Stack devstudio pom can now build a stand-alone installer in addition to update site ZIP files. Modify any/all Jenkins jobs, product.yml, CSP RCM ticket instructions to handle the productization of the installer.
> Mars:
> https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... (MD5)
> *Release Engineering CSP update instructions - Developer Studio Integration Stack 9.0.2.GA:*
> {code}
> Please remove earlier versions of Red Hat JBoss Developer Studio Integration Stack update site zips.
> When pushed, please reply so that QE can review the CSP pages & CDN/Download Manager files for push to production.
> _________________________________________________________________________________________
> Please add the following stand-alone installer [1] to the 9.1.0 JBoss Developer Studio product pulldown in the CSP Software Downloads page [2].
> [1] https://devstudio.redhat.com/9.0/stable/builds/installer/integration-stac... [Open URL] (MD5)
> [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...
> Associated JIRA: https://issues.jboss.org/browse/JBTIS-846
> Descriptive copy to associate w/ the CSP entry:
> -----------------------------------------------
> Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Stand-Alone Installer
> Detailed Description
> This installer contains JBoss Developer Studio 9.1.0.GA and JBoss Developer Studio Integration Stack tooling 9.0.2.GA.
> Manual Instructions
> java -jar jboss-devstudio-is-9.0.2.GA-installer-standalone.jar
> _________________________________________________________________________________________
> Please add the following update site zip file to the JBoss Developer Studio product pulldown in the CSP Software Downloads page:
> https://devstudio.redhat.com/9.0/stable/updates/integration-stack/devstud... [Open URL] (MD5)
> Descriptive copy to associate w/ the CSP entry:
> -----------------------------------------------
> Red Hat JBoss Developer Studio Integration Stack 9.0.2.GA Update Site Zip
> Detailed Description
> This release zip has been certified for JBoss Developer Studio 9.1.0.GA.
> Manual Instructions
> 1. Start jbdevstudio
> 2. Select the Help > Install New Software...
> 3. Select Add...
> 4. Select Archive...
> 5. Supply the zip file location as the repository archive.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23289) ServerProfileModel.getController fails to find publish controller for wf10 [aeri]
by Jeff Headley (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23289?page=com.atlassian.jira.plugi... ]
Jeff Headley commented on JBIDE-23289:
--------------------------------------
I got an automated email that said this bug report was created for a problem I had encountered. My environment is a Macbook Pro running MacOS Sierra and the latest Java 8. 102 I think. We still have some old legacy Seam 2 apps running on JBoss 5.1.0.GA and that is why we use JBoss Tools. Hopefully that helps.
> ServerProfileModel.getController fails to find publish controller for wf10 [aeri]
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23289
> URL: https://issues.jboss.org/browse/JBIDE-23289
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
>
> I hesitated to make a bug report here. On the one hand, this is simply a log message, and the environment still has a chance to recover.
> However, it does seem extremely strange that the publish subsystem is not being found for wf10. Our unit tests indicate it is found. The fact that this is still being replicated in astools 3.2.x is puzzling to me. But I simply cannot imagine what environment is causing this. Subsystem and profile mappings are done in the same plugin the subsystems are declared for the most part.
> The following problem was reported via the automated error reporting:
> Message: No subsystem found for servertype org.jboss.ide.eclipse.as.wildfly.100 and system type publish
> {noformat}
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel.getController(ServerProfileModel.java:187)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ProfileServerBehavior.getController(ProfileServerBehavior.java:59)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.getPublishController(CachedPublisherProfileBehavior.java:35)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297)
> at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218)
> at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:273)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367)
> at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349)
> at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372)
> at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
> | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.2.1.v20160711-1757 |
> Operating Systems:
> | Linux | 3.10.0.28 | 4.6.7.fc24 |
> | MacOSX | 10.10.5 | 10.12.0 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56f024b6e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4087) Mars as invalid Vagrant versions known to be not working
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4087:
-------------------------------------
Summary: Mars as invalid Vagrant versions known to be not working
Key: JBDS-4087
URL: https://issues.jboss.org/browse/JBDS-4087
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Affects Versions: 1.1.0.GA
Reporter: Aurélien Pupier
Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version.
For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6.
When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBDS-4050?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik commented on JBDS-4050:
-----------------------------------------
For the record, I ran into this one as well. Could not figure out, what the reason was until talking to [~budhrg]. There is no indication whatsoever on what goes wrong on the installer side. By know I also know there is a note in the trouble shooting section of the installer, but I am surprised that this was sufficient. IMO we should have modified the installer to check whether this required package is installed and if not put up a warning. That's my 0.02$ on this one.
Also makes we wonder how we test the installer on Windows 10? Do we have a test instance which gets re-created on each run?
> CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915
> ---------------------------------------------------------
>
> Key: JBDS-4050
> URL: https://issues.jboss.org/browse/JBDS-4050
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Environment: **Operating System**
> Windows 10 Pro 64 Bit
> **Devsuite version**
> Devsuite 1.1.0-GA-20160915-140
> Reporter: Budh Ram Gurung
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM1
>
> Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install-iteration1.log, install.log, vagrant-up-debug-log.txt
>
>
> After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message.
> Check the attached screenshots.
> I also tried to add vagrant box through cygwin shell but getting some `eventmachine.so` related error.
> *NOTE*: I am able to successfully add the cdk box on Vagrant 1.7.4 version.
> Other information, I had following things pre-installed before running the installer:
> - Docker toolbox (probably it remain there when I was trying it last time)
> - Vagrant 1.8.1
> - Cygwin
> - VirtualBox 5.0.26
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months