[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3605 at 6/9/16 1:52 PM:
----------------------------------------------------------
Nope, not until all the child/linked tasks are done. There are currently 13 unresolved linked/child tasks in this Epic, so it will likely remain open through the next sprints and release.
was (Author: nickboldt):
Nope, not until all the child/linked tasks are done.
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, RevisedIcons.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3605:
----------------------------------
Nope, not until all the child/linked tasks are done.
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, RevisedIcons.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3940) use new logo in icon for Development Suite installer .exe
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3940?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3940:
----------------------------------
Awaiting approval from [~tmancini].
> use new logo in icon for Development Suite installer .exe
> ---------------------------------------------------------
>
> Key: JBDS-3940
> URL: https://issues.jboss.org/browse/JBDS-3940
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Catherine Robson
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.0.GA
>
> Attachments: dpinstaller-new-icon-and-properties-2.png, dpinstaller-new-icon-and-properties.png, icons.png, RedHatDeveloperStudio_Logo_Installer.ico
>
>
> Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22305:
-------------------------------
Attachment: git.diff.txt
For build #8, which contains a simpler change, the git diff looks reasonable:
[^git.diff.txt]
However, looks like the tp provisioning failed to produce target platform folders, so a p2diff was impossible.
{code}
P2diff:
An error has occurred. See the log file
/qa/services/hudson/static_build_env/devstudio/p2diff/x86_64/configuration/1465480297502.log.
-->
$ cat /qa/services/hudson/static_build_env/devstudio/p2diff/x86_64/configuration/1465480292314.log
!SESSION 2016-06-09 09:51:32.001 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_91
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... file:///mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-create-diff/jbosstools/multiple/target/jbosstools-multiple.target.repo/
Command-line arguments: -os linux -ws gtk -arch x86_64 http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... file:///mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-create-diff/jbosstools/multiple/target/jbosstools-multiple.target.repo/
!ENTRY org.eclipse.osgi 4 0 2016-06-09 09:51:36.799
!MESSAGE Application error
!STACK 1
org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:///mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-create-diff/jbosstools/multiple/target/jbosstools-multiple.target.repo/.
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.example.p2diff.P2Diff.createP2Diff(P2Diff.java:59)
at org.eclipse.equinox.p2.example.p2diff.Application.start(Application.java:42)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
> automate process for fetching latest target platform mirrors
> ------------------------------------------------------------
>
> Key: JBIDE-22305
> URL: https://issues.jboss.org/browse/JBIDE-22305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.4.0.Final
>
> Attachments: git.diff.txt
>
>
> Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names.
> Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace.
> Thus for webtools we might simply define:
> webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do...
> and we'd end up with:
> http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8....
> * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr
> 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p...
> 2. when all children are done, a downstream job can runs TP update & validation against new .target files
> * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> * parse that into a list of URLs
> * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files
> * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs
> * resulting edited .target files will remain in the workspace, and we can then run
> * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> * when done if success:
> * ideally, generate a PR and attach link in email to jbosstools-dev@
> * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR
> * email should includes boilerplate text to send mail to list announcing new change for review
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ]
SJ Cox updated JBDS-3609:
-------------------------
Attachment: devstudio_assets_revised.zip
[~nickboldt], [~dgolovin], I've rettached the assets to be the correct formats and renamed all the files to match the current names. Please let me know if these work, thanks!
[^devstudio_assets_revised.zip]
> update splashscreen, about gfx, start icon for developers.redhat.com
> --------------------------------------------------------------------
>
> Key: JBDS-3609
> URL: https://issues.jboss.org/browse/JBDS-3609
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: James Cobb
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, devstudio_assets_revised.zip, launcher-icons-jbds10.png, splash-jbds10.png
>
>
> update splashscreen, about gfx, start icon for developers.redhat.com
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ]
SJ Cox updated JBDS-3609:
-------------------------
Attachment: (was: RedHat_JBDS.zip)
> update splashscreen, about gfx, start icon for developers.redhat.com
> --------------------------------------------------------------------
>
> Key: JBDS-3609
> URL: https://issues.jboss.org/browse/JBDS-3609
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: James Cobb
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, launcher-icons-jbds10.png, splash-jbds10.png
>
>
> update splashscreen, about gfx, start icon for developers.redhat.com
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-744) JBTIS Target Platform - Neon - sync with 4.60.0.Final-SNAPSHOT
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-744:
--------------------------------
Summary: JBTIS Target Platform - Neon - sync with 4.60.0.Final-SNAPSHOT
Key: JBTIS-744
URL: https://issues.jboss.org/browse/JBTIS-744
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: target-platform
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.4.0.Alpha1-TP
*Reason:* sytnc with 4.60.0.Final-SNAPSHOT
*Project page/sources:*
*Version:* 4.4.0.Alpha1-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* .DevstudioIS components
*Include in JBDS:* Yes (DevstudioIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months