[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3249:
----------------------------------
I've reopened this to set the correct fix version of 9.0.0.GA (not the CVE patch fix version). Also set pm_ack to negative.
For future work related to making it easier to install JBDS IS offline, see: JBDS-3565
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3249:
--------------------------------
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3249:
-----------------------------
Fix Version/s: 9.0.0.GA
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3249:
-----------------------------
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3249:
-----------------------------
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBDS-3249.
----------------------------
Fix Version/s: 9.0.0.CVE-2015-7501-GA
(was: 9.1.0.Beta1)
Resolution: Done
Marketplace has been supported now since Luna (8.x). After careful consideration it has been decided to not release a JBDSIS stand-alone installer. The general consensus was that creating a separate stand-alone JBDSIS installer does not provide enough user value-add. So the supported JBDSIS installation methods are:
- JBoss Central
- Standard Eclipse update site (p2)
- Eclipse Marketplace
- Offline installation (JBDSIS zip file in CSP)
I have retained the ability to build a JBDSIS stand-alone installer within a profile in the JBDSIS devstudio POM so we can turn this back on easily if we change our minds or circumstances dictate.
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.CVE-2015-7501-GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21267:
------------------------------------
build-ci DOES release maven artifacts to Nexus. That's why I'm asking about doing a release.
https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/p... -->
https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
Related: JBIDE-20900
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21267
> URL: https://issues.jboss.org/browse/JBIDE-21267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBTIS-538) Update Mars JBTIS TP to pick up JBDS TP w/ latest forge 3.0.0.Alpha2 runtime
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-538?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-538:
-----------------------------
Fix Version/s: 4.3.1.Final-TP
> Update Mars JBTIS TP to pick up JBDS TP w/ latest forge 3.0.0.Alpha2 runtime
> ----------------------------------------------------------------------------
>
> Key: JBTIS-538
> URL: https://issues.jboss.org/browse/JBTIS-538
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.0.Final-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.Final-TP
>
>
> *Reason:* Update Mars JBTIS TP to pick up JBDS TP w/ org.jboss.tools.forge w/ latest forge 3.0.0.Alpha2 runtime
> *Project page/sources:*
> *Version:* 4.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBDSIS
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.jboss.tools.community.central [2.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.common [3.7.0.Final-v20150924-2213-B38]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples.cheatsheet [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.central.feature.feature.group [2.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.project.examples [3.0.0.Final-v20151001-1531-B45]
> > org.jboss.tools.community.project.examples [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.common [3.7.1.Beta1-v20151207-2136-B58]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.community.central [2.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta1-v20151116-2016-B57]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 11 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 11 unique IUs
> < org.jboss.tools.community.central [2.0.0.Final-v20151001-1531-B45]
> < org.eclipse.emf.compare.edit [4.1.0.201509010903]
> < org.eclipse.emf.compare.doc [3.2.1.201509010903]
> < org.eclipse.emf.compare.ide.ui [4.1.1.201509010903]
> < org.eclipse.emf.compare.ide.ui.feature.group [3.1.1.201509010903]
> < org.eclipse.emf.compare [3.2.0.201509010903]
> < org.eclipse.emf.compare.feature.jar [3.1.1.201509010903]
> < org.eclipse.emf.compare.rcp.ui [4.1.1.201509010903]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.0.Final-v20151001-1531-B45]
> < org.eclipse.emf.compare.ide [3.2.1.201509010903]
> < org.eclipse.emf.compare.rcp [2.3.1.201509010903]
> < org.eclipse.emf.compare.ide.ui.feature.jar [3.1.1.201509010903]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.central.feature.feature.group [2.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples.cheatsheet [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.0.Final-v20151001-1531-B45]
> < org.jboss.tools.project.examples [3.0.0.Final-v20151001-1531-B45]
> < org.eclipse.emf.compare.feature.group [3.1.1.201509010903]
> < org.jboss.tools.community.project.examples [3.0.0.Final-v20151001-1531-B45]
> > org.eclipse.emf.compare.ide [3.2.1.201509120604]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare.rcp [2.3.1.201509120604]
> > org.eclipse.emf.compare.rcp.ui [4.1.1.201509120604]
> > org.eclipse.emf.compare.ide.ui.feature.jar [3.1.1.201509120604]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare.ide.ui [4.1.1.201509120604]
> > org.eclipse.emf.compare.feature.jar [3.1.1.201509120604]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare.feature.group [3.1.1.201509120604]
> > org.jboss.tools.project.examples [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare.doc [3.2.1.201509120604]
> > org.jboss.tools.community.project.examples [3.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.community.central [2.0.1.Beta1-v20151116-2016-B57]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare [3.2.0.201509120604]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta1-v20151116-2016-B57]
> > org.eclipse.emf.compare.ide.ui.feature.group [3.1.1.201509120604]
> > org.eclipse.emf.compare.edit [4.1.0.201509120604]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta1-v20151116-2016-B57]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 21 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 21 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer support
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBDS-3276.
----------------------------
Fix Version/s: (was: 9.1.0.Beta2)
Resolution: Won't Fix
Given Max's comments below and the general consensus from usability testing that creating a separate stand-alone JBDSIS installer does not provide enough user value-add, I'm closing this issue. I have retained the ability to build a JBDSIS stand-alone installer within a profile in the JBDSIS devstudio POM so we can turn this back on easily if we change our minds or circumstances dictate.
[~crobson] [~maxandersen]
> JBDS-IS Installer support
> -------------------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Paul Leacu
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months