[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15481:
-------------------------------
Description:
1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
usecases:
* find missing/weird versions
* duplicate components
* get list of potential unnecessary plugins in TP
2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
http://download.jboss.org/jbosstools/updates/scripted-installation/
https://devstudio.redhat.com/download/scripted-install/
3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes?
was:
1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
usecases:
* find missing/weird versions
* duplicate components
* get list of potential unnecessary plugins in TP
2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
http://download.jboss.org/jbosstools/updates/scripted-installation/
https://devstudio.redhat.com/download/scripted-install/
3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
> setup of vwatch for jboss tools installations
> ---------------------------------------------
>
> Key: JBIDE-15481
> URL: https://issues.jboss.org/browse/JBIDE-15481
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide15481.png
>
>
> 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
> usecases:
> * find missing/weird versions
> * duplicate components
> * get list of potential unnecessary plugins in TP
> 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
> 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15481:
-------------------------------
Description:
1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
usecases:
* find missing/weird versions
* duplicate components
* get list of potential unnecessary plugins in TP
2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
http://download.jboss.org/jbosstools/updates/scripted-installation/
https://devstudio.redhat.com/download/scripted-install/
3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
was:
use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
usecases:
* find missing/weird versions
* duplicate components
* get list of potential unnecessary plugins in TP
> setup of vwatch for jboss tools installations
> ---------------------------------------------
>
> Key: JBIDE-15481
> URL: https://issues.jboss.org/browse/JBIDE-15481
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide15481.png
>
>
> 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
> usecases:
> * find missing/weird versions
> * duplicate components
> * get list of potential unnecessary plugins in TP
> 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-416.
----------------------------
Fix Version/s: 8.0.1.GA
Resolution: Done
Updated docs looks good.
> Need to doc split of SOA Development between release and early access
> ---------------------------------------------------------------------
>
> Key: JBTIS-416
> URL: https://issues.jboss.org/browse/JBTIS-416
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 8.0.1.GA, 4.2.1.Final
> Reporter: Paul Leacu
> Assignee: Misha Ali
> Fix For: 8.0.1.GA
>
> Attachments: ss0.png, ss1.png
>
>
> Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA).
> To address this issue I've done the following:
> JBDSIS 8.0.1.GA:
> site-ga: (released)
> JBoss Business Process and Rules Development
> *All features available
> JBoss Data Virtualization Development
> *All features available
> JBoss Integration and SOA Development
> *All features except Fuse Tooling and SwitchYard
> JBoss SOA 5.x Development
> *All features available
>
> site-ea: (early access)
> JBoss Fuse Development
> *All features available
> JBoss Integration and SOA Development
> *Fuse Tooling and SwitchYard only available
> To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window.
> The community JBTIS install will do something similar.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months