July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3465) Consider using SpringIDE 3.7 (or 3.6.4?)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3465: ------------------------------------- Quality of both SpringIDE builds seem to be similar. There are bugs in the plugin, but those bugs are for both versions and they seem to be upstream. Which one to choose? Well, depends. We can be sure what is broken and not working for released SpringIDE and we should not be surprised (only in case that something break SpringIDE plugin, what happens some time). With the nightly build there is a risk of badly broken build of SpringIDE. We can't ensure, that every nightly SpringIDE build will work for users. On the other hand, there is a change that existing bugs will be fixed (but there can also raise new bugs). >From my point of view, using release is much safer, even there are some nasty bugs. > Consider using SpringIDE 3.7 (or 3.6.4?) > ---------------------------------------- > > Key: JBDS-3465 > URL: https://issues.jboss.org/browse/JBDS-3465 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Marián Labuda > Fix For: 9.0.0.Beta2 > > Attachments: install-spring-all-features.png, install-spring-sites.png > > > There are new versions of SpringIDE available: > {code:title=http://dist.springsource.com/release/TOOLS/update/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.6.4.201503051146-RELEASE{code} > {code:title=http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.7.0.201506181755-CI-B262{code} > Which would we like to include in Central? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19990: ------------------------------------------------ I mean Eclipse Browser preferences(General->Web Browser), not Visual Engine preferences. This bug appears only if external web browser + default system web browser is selected(internal web browser will not be available). Otherwise everything will work fine. > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11436: ------------------------------------ If you're going to undo a change I made, because "+1 on not having it categorized since its rather pointless to install on its own", please do so in BOTH JBT and JBDS: https://github.com/jbosstools/jbosstools-build-sites/commit/3a1be4b56da6a... https://github.com/jbdevstudio/jbdevstudio-product/commit/1a31943c1ee4f37... > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3479: ---------------------------------- Also, the Red Ball has never been used there. Why not either the old red logo (JBDS 7 and earlier) [1] or I can make a numberless version with the the new white branding from JBDS 8+ ? !https://devstudio.redhat.com/images/devstudio_logo_132x95.png! - [1] https://devstudio.redhat.com/images/devstudio_logo_132x95.png > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 9.0.0.Beta1 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid loss of full stats rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3479: ---------------------------------- Wondering if we want to mention the versions of Eclipse that we support in these multiple-version entries, like for example how m2e does it: http://marketplace.eclipse.org/content/maven-integration-eclipse-luna-and... > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 9.0.0.Beta1 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid loss of full stats rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3464) Consider using Subclipse 1.10.9 with svnkit 1.8.10.r10446_v20150526_1454/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3464?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3464: ---------------------------------- That's just for the last 30 days: http://marketplace.eclipse.org/metrics/successful_installs/last30days Overall/alltime shows SVN installs beat Subclipse as well (1.28M vs. 1.15M): http://marketplace.eclipse.org/metrics/successful_installs I guess either way as long as we bundle w/ the latest SVNKit installation from Central will be a 1-step process (rather than the 2-step process shown on the Subversive marketplace entry): https://www.eclipse.org/subversive/installation-instructions.php > Consider using Subclipse 1.10.9 with svnkit 1.8.10.r10446_v20150526_1454/ > ------------------------------------------------------------------------- > > Key: JBDS-3464 > URL: https://issues.jboss.org/browse/JBDS-3464 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 9.0.0.Beta2 > > > I've pulled a new Subclipse/SVNKit mirror: > http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... > This would replace the current one we have in JBDS 9 Beta1: > http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... > Please review. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11436: ---------------------------------------- Feature uncategorized: https://github.com/jbosstools/jbosstools-build-sites/commit/cf860c25d5236... > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-458) Missing SOA 5.x features from JBDS-IS 8.0.2.GA in marketplace

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-458: --------------------------------------- Summary: Missing SOA 5.x features from JBDS-IS 8.0.2.GA in marketplace Key: JBTIS-458 URL: https://issues.jboss.org/browse/JBTIS-458 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.2.GA Reporter: Andrej Podhradsky The following features are missing org.jboss.tools.esb.feature_1.5.530.Final-v20150310-1957-B70 org.jboss.tools.jbpm3.feature_4.5.200.Final-v20130815-1941-B2008 org.jboss.tools.jbpm.common.feature_4.5.200.Final-v20130815-1941-B2008 org.jboss.tools.jbpm.convert.feature_4.5.200.Final-v20130815-1941-B2008 org.jboss.tools.runtime.esb.detector.feature_1.5.530.Final-v20150310-1957-B70 org.jbpm.gd.jpdl.feature_4.5.200.Final-v20130815-1941-B2008 which are a part of SOA 5.x development. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11436: --------------------------------------------- I was wondering same thing - seemed wrong to have it in the updatesite, but needed since it can't just be a bundle. But +1 on not having it categorized since its rather pointless to install on its own. > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20171: --------------------------------------------- We have a requirement for 7 years to know the exact tag our products are built from. Let us ignore the past for a bit look at current situation. Right now buildinfo.json does not have that info nor does the xulrunner if we don't tag it. I've suggested we at least make the tag and would like to do it in an automated fashion so we don't have to go hunt that info manually. Please let me know how you want to fulfill that for our builds going forward. > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 July 2015