[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-15481:
-------------------------------------------
Summary: 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
Reporter: Max Rydahl Andersen
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ]
Jiri Peterka edited comment on JBIDE-15468 at 9/11/13 10:08 AM:
----------------------------------------------------------------
Ok, I see this resolved, reopen if needed.
was (Author: jpeterka):
Ok, I see this resoved, reopen if needed.
> Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15468
> URL: https://issues.jboss.org/browse/JBIDE-15468
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Affects Versions: 4.1.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Blocker
> Fix For: 4.1.1.Alpha1
>
> Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png, version-ok.png
>
>
> This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown.
> !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Jiri Pallich (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Jiri Pallich updated JBDS-2623:
-------------------------------
Component/s: requirements
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.x
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months