August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4505) Fuse on Karaf does not have a public facing download URL and doesn't trigger account page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4505?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4505: -------------------------------- Summary: Fuse on Karaf does not have a public facing download URL and doesn't trigger account page (was: Fuse on Karaf does not have a public facing download URL and does't trigger account page) > Fuse on Karaf does not have a public facing download URL and doesn't trigger account page > ----------------------------------------------------------------------------------------- > > Key: JBDS-4505 > URL: https://issues.jboss.org/browse/JBDS-4505 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 11.0.0.GA > > > Fuse platform on karaf only has a vpn accessible URL defined. Needs a public facing one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4505) Fuse on Karaf does not have a public facing download URL and does't trigger account page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4505?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4505: -------------------------------- Summary: Fuse on Karaf does not have a public facing download URL and does't trigger account page (was: Fuse on Karaf does not have a public facing download URL) > Fuse on Karaf does not have a public facing download URL and does't trigger account page > ---------------------------------------------------------------------------------------- > > Key: JBDS-4505 > URL: https://issues.jboss.org/browse/JBDS-4505 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 11.0.0.GA > > > Fuse platform on karaf only has a vpn accessible URL defined. Needs a public facing one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24795) Add Minishift Home field to New server dialog for cdk 3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24795?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-24795. ----------------------------------- Fix Version/s: 4.5.0.Final Resolution: Rejected OK, I guess I'm overruled ;) > Add Minishift Home field to New server dialog for cdk 3 > ------------------------------------------------------- > > Key: JBIDE-24795 > URL: https://issues.jboss.org/browse/JBIDE-24795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > > Somewhat related to JBIDE-24447 which is about allowing different minishift home set via MINISHIFT_HOME. > When you create your cdk runtime manually, you should have a way of setting a custom Minishift home. Currently the dialog only contains the Minishift Binary field. > So if you're using a directory other than ~/.minishift, you will have to create the cdk server first and then change this in the server editor. It would be desirable to have this field present in the New Server dialog. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24805) N&N for 4.5.0.Final is not aggregated properly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24805?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24805. --------------------------------- I'm satisfied. Closing. > N&N for 4.5.0.Final is not aggregated properly > ---------------------------------------------- > > Key: JBIDE-24805 > URL: https://issues.jboss.org/browse/JBIDE-24805 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Something's fishy here. > http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.5.0.Fina... > It says at the top: > This is a summary page of all New & Noteworthy for 4.5.0.AM2 and 4.5.0.AM1 > But it's not true. For example this one is not included: > http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.5.0.AM2.... > Freemarker component deprecation > In the past the aggregation didn't happen unless the Final version was defined in the products.yml. See JBIDE-22199 and this commit: > https://github.com/jbosstools/jbosstools-website/commit/a5a0763d35c33c399... > If you look at the current state of products.yml in master, the 4.5.0.Final version is not there yet: > https://github.com/jbosstools/jbosstools-website/blob/b8e750b5e027a0c3260... > And yet, the page already shows it as Coming soon, which should only happen when you have that definition (without a release date). > Am I missing something? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24841) Remove findbugs plugin from Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24841?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24841: --------------------------------------- [~nickboldt] I didn't mean we rush to make the change before GA date. I meant that if we agree to remove it, this could be done for devstudio 11 retrospectively because this is loaded from the server and not included in the built devstudio / jbosstools bits. But yeah, we can also just do this for the future releases. +1 on reviewing other 3rd party plugins in Central as well. > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBIDE-24841 > URL: https://issues.jboss.org/browse/JBIDE-24841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update, target-platform, updatesite, upstream > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24843) Update description of org.jboss.tools.cdi.xml and xml.ui plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24843?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24843: ------------------------------- Component/s: updatesite > Update description of org.jboss.tools.cdi.xml and xml.ui plugins > ---------------------------------------------------------------- > > Key: JBIDE-24843 > URL: https://issues.jboss.org/browse/JBIDE-24843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, updatesite > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > This is a followup of JBDS-4495 . We deprecated seam 3 and moved it to central. We wanted to keep cdi itself still in the coretools feature. > But there are these two plugins: > org.jboss.tools.cdi.xml.ui_1.8.100.v20170801-1456.jar > org.jboss.tools.cdi.xml_1.8.100.v20170801-1421.jar > They don't have seam in the name, but their descriptions say: > JBoss Tools Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Jeff checked the code and it doesn't seem like this has anything to do with Seam, so we should change the description. > I'm not sure myself what to call them -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24843) Update description of org.jboss.tools.cdi.xml and xml.ui plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24843?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24843: ------------------------------- Sprint: devex #136 August 2018 > Update description of org.jboss.tools.cdi.xml and xml.ui plugins > ---------------------------------------------------------------- > > Key: JBIDE-24843 > URL: https://issues.jboss.org/browse/JBIDE-24843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, updatesite > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > This is a followup of JBDS-4495 . We deprecated seam 3 and moved it to central. We wanted to keep cdi itself still in the coretools feature. > But there are these two plugins: > org.jboss.tools.cdi.xml.ui_1.8.100.v20170801-1456.jar > org.jboss.tools.cdi.xml_1.8.100.v20170801-1421.jar > They don't have seam in the name, but their descriptions say: > JBoss Tools Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Jeff checked the code and it doesn't seem like this has anything to do with Seam, so we should change the description. > I'm not sure myself what to call them -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24841) Remove findbugs plugin from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24841?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24841: ------------------------------- Component/s: central-update target-platform updatesite upstream (was: central) > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBIDE-24841 > URL: https://issues.jboss.org/browse/JBIDE-24841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update, target-platform, updatesite, upstream > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24841) Remove findbugs plugin from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24841?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24841: ------------------------------------ I'd prefer to not have to change the discovery site this close to GA, unless this is considered a blocker. As this is an OPTIONAL 3rd party install, I don't consider this a blocker. And since the suggested change is not to simply REMOVE but to REPLACE, this is too big a change to squeeze out this week. I've set fixversion 4.5.1.AM1, and will wait for approval from [~rpdavis]. Perhaps one goal for 4.5.1 / 11.1 would be to review the contents of Central and either update or remove other components? > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBIDE-24841 > URL: https://issues.jboss.org/browse/JBIDE-24841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24843) Update description of org.jboss.tools.cdi.xml and xml.ui plugins

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24843?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24843: --------------------------------------- [~nickboldt] exactly, I could do a PR myself, but we just need to know what to call it. Hopefully Jeff can suggest something. I'm fine with your suggestions. > Update description of org.jboss.tools.cdi.xml and xml.ui plugins > ---------------------------------------------------------------- > > Key: JBIDE-24843 > URL: https://issues.jboss.org/browse/JBIDE-24843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > This is a followup of JBDS-4495 . We deprecated seam 3 and moved it to central. We wanted to keep cdi itself still in the coretools feature. > But there are these two plugins: > org.jboss.tools.cdi.xml.ui_1.8.100.v20170801-1456.jar > org.jboss.tools.cdi.xml_1.8.100.v20170801-1421.jar > They don't have seam in the name, but their descriptions say: > JBoss Tools Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Seam XML > https://github.com/jbosstools/jbosstools-javaee/blob/master/cdi/plugins/o... > Jeff checked the code and it doesn't seem like this has anything to do with Seam, so we should change the description. > I'm not sure myself what to call them -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 August 2017