[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23370:
------------------------------------
Build done. Assigning back to Martin to test, verify, and eventually submit a new PR for your final bits (before Nov 23).
> Update RedDeer in TP for JBT 4.4.2.AM3
> --------------------------------------
>
> Key: JBIDE-23370
> URL: https://issues.jboss.org/browse/JBIDE-23370
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.2.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released.
> We will want to update RedDeer in the TP to include the latest from
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP.
> So please let me know when you're ready for this task and then I can create the update site immediately.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23370:
----------------------------------
Assignee: Martin Malina (was: Nick Boldt)
> Update RedDeer in TP for JBT 4.4.2.AM3
> --------------------------------------
>
> Key: JBIDE-23370
> URL: https://issues.jboss.org/browse/JBIDE-23370
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.2.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released.
> We will want to update RedDeer in the TP to include the latest from
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP.
> So please let me know when you're ready for this task and then I can create the update site immediately.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-948:
----------------------------------
Ok - now I see the issue. Definitely not a blocker. Does this happen with the devstudio stand-alone installer too? It can't have anything to do with the supplemental runtimes.
{code}
[pleacu@pleacu-2-laptop crap]$ java -jar ~/install/devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar InstallConfigRecord.xml
[ Starting automated installation ]
[INFO] Selected JVM Information
[INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-1.b14.fc24.x86_64
[INFO] Vendor : Oracle Corporation
[INFO] Version : 1.8.0_102
[INFO] Arch : 64-bit
[ Starting to unpack ]
[ Processing package: P2 Director Application (1/4) ]
[ Processing package: Red Hat JBoss Developer Studio 10.1.0.GA (2/4) ]
[ Processing package: Red Hat JBoss Developer Studio 10.1.0.GA Metadata Generation (3/4) ]
[ Processing package: Processing Supplemental Runtimes (4/4) ]
[ Unpacking finished ]
[ Creating shortcuts .. done. ]
[ Add shortcuts to uninstaller .. done. ]
[ Writing the uninstaller data ... ]
[ Automated installation done ]
{code}
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
> ----------------------------------------------------------------------------------------
>
> Key: JBTIS-948
> URL: https://issues.jboss.org/browse/JBTIS-948
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}.
> The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBTIS-949) Rename the name of the installer with runtime
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-949?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-949.
------------------------------
Fix Version/s: 10.0.0.GA
Resolution: Done
Updated Jenkins job as requested
> Rename the name of the installer with runtime
> ---------------------------------------------
>
> Key: JBTIS-949
> URL: https://issues.jboss.org/browse/JBTIS-949
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 10.0.0.GA
>
>
> Rename the name of the installer with runtime. I suggest
> {code}
> devstudio-integration-stack-10.0.0.CR1-runtime-installer.jar
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23399) clean up email generation to avoid invalid addresses
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23399?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23399:
------------------------------------
I believe the problem here was that I was using
{code}sender="Nick Boldt <nboldt(a)redhat.com>" {code}
which became:
{code} /bin/mail -s 'Ready for JBT 4.4.2.AM2' 'people at redhat.com' -c nboldt at redhat.com -- '-fNick Boldt <nboldt(a)redhat.com>'{code}
instead of
{code} /bin/mail -s 'Ready for JBT 4.4.2.AM2' 'people at redhat.com' -c nboldt at redhat.com -- -f"Nick Boldt <nboldt(a)redhat.com>"{code}
So, I've fixed that by not trying to pass in a name alias to the -f flag.
> clean up email generation to avoid invalid addresses
> ----------------------------------------------------
>
> Key: JBIDE-23399
> URL: https://issues.jboss.org/browse/JBIDE-23399
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> Last batch of notification emails re: JBT 4.4.2.AM2 release (and the previous ones for staging too) all had these recipients:
> {code}
> -nboldt(a)redhat.com,
> Boldt(a)redhat.com,
> -fNick(a)redhat.com,
> --(a)redhat.com,
> -c(a)redhat.com{code}
> Seems like a problem with quotes / commandline.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months