December 2013 - jbosstools-issues

[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 commented on JBDS-2623: ------------------------------------ Hi, I am on PTO, I will be back in the office on 2014-Jan-03. In urgent cases please call me on my phone: +420 775 158 118. For Middleware issues please contact Anne-Louise Tangring. For PSB issues please contact Satish Mohan or Suman Guha. Cheers, Jiri > 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.0.GA > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2623. ---------------------------- Resolution: Done With the release of http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3... (also into Nexus) this is done. Closing. > 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.0.GA > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10541) Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10541: ------------------------------------- Assignee: (was: Andre Dietisheim) > Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: 4.2.x > > Attachments: committed-changes-to-publish.png > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10541) Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10541: ------------------------------------- Estimated Difficulty: High > Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: 4.2.x > > Attachments: committed-changes-to-publish.png > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13407: ------------------------------- Fix Version/s: LATER (was: 4.2.0.Alpha1) > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > Attachments: dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13407: ------------------------------------ Moved to LATER, until we get some hardware in place. (TBD in 2014.) > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > Attachments: dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13730) Server Adapter: state [Republish] although Repository is uptodate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13730: ------------------------------------- Estimated Difficulty: Low > Server Adapter: state [Republish] although Repository is uptodate > ----------------------------------------------------------------- > > Key: JBIDE-13730 > URL: https://issues.jboss.org/browse/JBIDE-13730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Labels: server_adapter > Fix For: 4.2.x > > Attachments: republishsync.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10695) Application wizard: provide some doc/context for users to know what they do

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10695?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10695: ------------------------------------- Estimated Difficulty: High > Application wizard: provide some doc/context for users to know what they do > --------------------------------------------------------------------------- > > Key: JBIDE-10695 > URL: https://issues.jboss.org/browse/JBIDE-10695 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.x > > Attachments: cartridge-description.png > > > currently cartridges are just listed with their (verbose) name, either in the application type combo or in the list of embeddable cartridges. The names are now verbose but we're still missing descriptions as provided in the Web-UI: > !cartridge-description.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13730) Server Adapter: state [Republish] although Repository is uptodate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13730: ------------------------------------- Assignee: (was: Andre Dietisheim) > Server Adapter: state [Republish] although Repository is uptodate > ----------------------------------------------------------------- > > Key: JBIDE-13730 > URL: https://issues.jboss.org/browse/JBIDE-13730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Labels: server_adapter > Fix For: 4.2.x > > Attachments: republishsync.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14395) Application wizard: should enable scaling by default in UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14395?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14395: ------------------------------------- Estimated Difficulty: Low > Application wizard: should enable scaling by default in UI > ---------------------------------------------------------- > > Key: JBIDE-14395 > URL: https://issues.jboss.org/browse/JBIDE-14395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Labels: application_wizard > Fix For: LATER > > Attachments: scaling.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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013