January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-1243) Investigate use of Groovy Eclipse Plugin in JBT/JBDS Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1243?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-1243. ------------------------------------- Resolution: Rejected This was requested a few years ago in a PRD but was rejected since the groovy plugin requires a modified JDT. something we couldn't safely support and we also didn't have any requests for it afaik. If Fuse and others need it that shuold be opened in separate issue with reasons and we can work from there. > Investigate use of Groovy Eclipse Plugin in JBT/JBDS Central > ------------------------------------------------------------ > > Key: JBDS-1243 > URL: https://issues.jboss.org/browse/JBDS-1243 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Reporter: Max Rydahl Andersen > Fix For: LATER > > > 3rd party cert: Groovy -- 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-340) Intro/Welcome screen cleanup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-340?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen resolved JBDS-340. -------------------------------------- Resolution: Out of Date > Intro/Welcome screen cleanup > ---------------------------- > > Key: JBDS-340 > URL: https://issues.jboss.org/browse/JBDS-340 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: LATER > > > SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there. > If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism > and hopefully create a JBDS branded version. -- 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-2849) Document Offline Usage

by Jim Rigsbee (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Jim Rigsbee commented on JBDS-2849: ----------------------------------- >From training org: We cannot always assume that we are connected to the Internet when we install and use JBDS in our facilities and particularly when we conduct onsite training. Some customers will not allow access to their network. As a matter of policy, we do not allow Internet access in our Virtual and Self-Paced learning environments for liability reasons. A particular problem is when the project wizards cannot get access to a archetype. We've been caching the version of the archetype we want the student to use in a local Maven repo. We may not be able to work around this since JBDS versions and Fuse, SwitchYard, etc. versions cannot be tied together as those products may evolve to higher and higher versions while JBDS remains static for a while. > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Michelle Murray > > Working with the Training team, document how JBDS is to be used in an offline state. -- 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-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16355: --------------------------------------------- "It is simpler from a users' perspective to be provided with a ready made query than being told how to build their own." ...but the docs does not provide a link. It tells you how to build one. Here is what I see: "To view information about issues resolved in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following search query as one line: (project in (JBDS) AND affectedVersion <= "7.0.1.GA" AND fixVersion >= "7.1.0.Alpha1" AND fixVersion <="7.1.0.GA" OR project in (JBIDE) AND affectedVersion <= "4.1.0.1.Final" AND fixVersion >= "4.1.1.Alpha1" AND fixVersion <="4.1.1.Final") AND type in (Bug) AND resolution in (Done)" That is explaining how to manually do the query via jira query UI instead of simply having a direct link to the jira query. > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- 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-16375) Allow to extend Central extensions catalog with "Beta" stuff

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16375: -------------------------------------- Summary: Allow to extend Central extensions catalog with "Beta" stuff Key: JBIDE-16375 URL: https://issues.jboss.org/browse/JBIDE-16375 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, discovery Reporter: Mickael Istria Fix For: 4.2.0.Beta1 In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries. Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels. The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...). -- 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-14742) Investigate using or forking eclipse release train repo cheks

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14742?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14742: ----------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.x) > Investigate using or forking eclipse release train repo cheks > ------------------------------------------------------------- > > Key: JBIDE-14742 > URL: https://issues.jboss.org/browse/JBIDE-14742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Alpha2 > > > http://build.eclipse.org/simrel/kepler/reporeports/ > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_FAQ > Seems like very useful tool to run against and updatesite. -- 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-14742) Investigate using or forking eclipse release train repo cheks

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14742?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-14742: -------------------------------------- Assignee: Mickael Istria > Investigate using or forking eclipse release train repo cheks > ------------------------------------------------------------- > > Key: JBIDE-14742 > URL: https://issues.jboss.org/browse/JBIDE-14742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > http://build.eclipse.org/simrel/kepler/reporeports/ > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_FAQ > Seems like very useful tool to run against and updatesite. -- 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-14742) Investigate using or forking eclipse release train repo cheks

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14742?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14742: ----------------------------------- Priority: Major (was: Minor) > Investigate using or forking eclipse release train repo cheks > ------------------------------------------------------------- > > Key: JBIDE-14742 > URL: https://issues.jboss.org/browse/JBIDE-14742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > > http://build.eclipse.org/simrel/kepler/reporeports/ > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_FAQ > Seems like very useful tool to run against and updatesite. -- 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-16309) Move inter-JBT dependencies to component poms

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16309: ------------------------------------- Central done > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- 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-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-2874: -------------------------------------- I don't think this is a must-have feature and QE discussion around testing or any concerns they have should be addressed before we agree to include it for 8.0.0. From a support perspective it adds complication but that's not to say it's not useful for customers and we shouldn't support it. However, if it there's a risk it could break or cause issues with our tools (due to incompatibility issues a year from now) then we should address them now. TL;DR: Let's ask QE and get their thoughts on it. Mus > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? -- 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 January 2014