[JBoss JIRA] (JBDS-4530) Work to remove all upstream 3rd party deps in the devstudio 11.1 rpm
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4530?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4530.
------------------------------
> Work to remove all upstream 3rd party deps in the devstudio 11.1 rpm
> ---------------------------------------------------------------------
>
> Key: JBDS-4530
> URL: https://issues.jboss.org/browse/JBDS-4530
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.1.0.GA
>
>
> This is a wrapper issue for a number of subtasks and linked issues related to eliminating the 3rd party plugins in the devstudio copr rpm, so that it can ultimately be built w/ brew.
> Tasks include:
> * add rpms already in Fedora to SCL/DevTools (eg., Datatools, WTP Dali/JPT)
> * create new rpms in Fedora (buildship, recommenders/snipmatch, sapphire[1], m2e & extras[2], m2e-wtp & extras[3], tern.java)
> * removal of old/duplicate versions in the target platform (javax.activation, guava, jetty, asm, aries
> * ensure we're using the latest linuxtools/docker tools (including new features/plugins added for 6.1/6.1.1)
> [1] may require contributing a Maven/Tycho build upstream to that project so we can then consume it in Koji/Brew
> [2] m2e extras include: buildhelper, egit, mavenarchiver
> [3] m2e.wtp extras include: jaxrs, jpa, jsf
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including buildhelper, egit, mavenarchiver, maven importer, & tycho
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4532.
------------------------------
> RPM should depend on upstream m2e rpms, including buildhelper, egit, mavenarchiver, maven importer, & tycho
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4532
> URL: https://issues.jboss.org/browse/JBDS-4532
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.1.0.GA
>
>
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including buildhelper, egit, mavenarchiver, maven importer, & tycho
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4532:
------------------------------------
Verified, DevTools repo includes packages mentioned in description/comments. Also versions match. DevStudio RPM depends on m2e packages:
{code}
rpm -qpR rh-eclipse47-devstudio-11.1-0.20171026.1132.el7.x86_64.rpm | grep m2e
rh-eclipse47-eclipse-m2e-core
rh-eclipse47-eclipse-m2e-workspace
rh-eclipse47-eclipse-m2e-buildhelper
rh-eclipse47-eclipse-m2e-egit
rh-eclipse47-eclipse-m2e-mavenarchiver
rh-eclipse47-eclipse-m2e-tycho
rh-eclipse47-eclipse-m2e-wtp
{code}
Issue JBDS-4589 doesn't exists, you probably meant JBDS-4612.
> RPM should depend on upstream m2e rpms, including buildhelper, egit, mavenarchiver, maven importer, & tycho
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4532
> URL: https://issues.jboss.org/browse/JBDS-4532
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.1.0.GA
>
>
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25315) Include Fuse CI job update for job configuration update
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-25315:
---------------------------------------
Summary: Include Fuse CI job update for job configuration update
Key: JBIDE-25315
URL: https://issues.jboss.org/browse/JBIDE-25315
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Affects Versions: 4.5.1.Final
Reporter: Aurélien Pupier
Attachments: image-2017-11-02-09-23-36-305.png
the CI jobs on Fuse Ci are often not synchronized with modifications done on other jboss tools project such as TARGET_PLATFORM version.
for instance today again:
!image-2017-11-02-09-23-36-305.png|thumbnail!
it would be useful to include the update of the FUSE CI jobs in the process to update the jobs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4408) DevSuite 1.4 Installer document how to clean up after a failed install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4408?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4408:
--------------------------------
Sprint: (was: devex #139 October 2017)
> DevSuite 1.4 Installer document how to clean up after a failed install
> ----------------------------------------------------------------------
>
> Key: JBDS-4408
> URL: https://issues.jboss.org/browse/JBDS-4408
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.GA
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: doc, ui
> Fix For: 11.x
>
>
> There should be a document/faq that indicates how to clean-up / recover after a failed install.
> On Windows there is the Uninstalli Dev Studio menu entry. But that doesn't clean up everything.
> It prompts to delete everything in the installation directory C:\DeveloperSuite but doesn't actually delete everything.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months