[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4377:
-------------------------------------
But I am really curious, why it is working with GUI installer and does-not working with automated approach
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4377:
-------------------------------------
that works!
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4377:
----------------------------------
Try installing 3 IUs:
{code} ... -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.common_core_EBZ511793.feature.patch.feature.group ... {code}
> installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4377
> URL: https://issues.jboss.org/browse/JBDS-4377
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: build, installer, target-platform
> Affects Versions: 10.4.0.AM3
> Environment: Windows: DevSuite Installer v1.4 AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: devstudio104am3-installer-missing-unpatched-plugin.png
>
>
> Denis reports a problem using the installer jar in automated mode (using .xml script).
> Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script.
> Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well.
> !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail!
> So we need to figure out how to include BOTH versions in the installer jar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4362:
----------------------------------
Thanks, Jeff. The only projects in the github jbdevstudio org that's not already public are:
* https://github.com/jbdevstudio/jbdevstudio-artwork - branding & artwork used in the installer. No real reason to keep it private other than "because we do". Same images are also in jbdevstudio-product repo, which is public.
* https://github.com/jbdevstudio/jbdevstudio-qa - QE tests - could maybe be public if we wanted (I'm not sure if there's anything in there that contains internal infrastructure details)
* https://github.com/jbdevstudio/jbdevstudio-ci - Jenkins job configs (contains internal infrastructure details so should remain private)
So... as to the SOURCES for devstudio ... at this point it's all public and open source.
Dropping the EAP bundle of devstudio means everything we *BUILD* is also public & open source, as there's no EAP license requirement.
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24324) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24324?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-24324.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24324
> URL: https://issues.jboss.org/browse/JBIDE-24324
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4321 at 4/26/17 2:48 PM:
-----------------------------------------------------------
Cannot reproduce.
I had this version of devstudio rpm installed:
Then I installed everything from Central, including the Early Access stuff:
!rpm-installed-everything-from-central.png|thumbnail!
However, I did get a lot of use-constraint violations.
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt] (filtered log)
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt] (full log)
So I updated all the rh-eclipse46* packages:
[^rpm-installed-everything-from-central.update.rpm.deps.txt]
I'm still getting errors, but probably only because I'm on F24, not RHEL7.
Biggest problem seems to be that on F24, com.googlecode.javaewah 0.8.4 is installed, but the latest jgit 4.6.1 requires 1.1.6:
{code}Unresolved requirement: Import-Package: com.googlecode.javaewah; version="[1.1.6,2.0.0)"{code}
was (Author: nickboldt):
Cannot reproduce.
I had this version of devstudio rpm installed:
Then I installed everything from Central, including the Early Access stuff:
!rpm-installed-everything-from-central.png|thumbnail!
However, I did get a lot of use-constraint violations.
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt] (filtered log)
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt] (full log)
So I updated all the rh-eclipse46* packages:
[^rpm-installed-everything-from-central.update.rpm.deps.txt]
I'm still getting errors, but probably only because I'm on F24, not RHEL7.
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4321:
----------------------------------
Cannot reproduce.
I had this version of devstudio rpm installed:
Then I installed everything from Central, including the Early Access stuff:
!rpm-installed-everything-from-central.png|thumbnail!
However, I did get a lot of use-constraint violations.
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt] (filtered log)
* [^rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt] (full log)
So I updated all the rh-eclipse46* packages:
[^rpm-installed-everything-from-central.update.rpm.deps.txt]
I'm still getting errors, but probably only because I'm on F24, not RHEL7.
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4362:
----------------------------------
+1 for 11 target. Regarding the OSS nature of the stuff, my understanding is that some of the image (used in the installer or in DevStudio) are not OSS, that's why some repos in the jbdevstudio GitHub organisation are private
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months