July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20181) Add m2e nature to o.j.openshift.client and o.j.openshift.client projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20181?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20181. ------------------------------------ closing since nothing for QE to verify > Add m2e nature to o.j.openshift.client and o.j.openshift.client projects > ------------------------------------------------------------------------ > > Key: JBIDE-20181 > URL: https://issues.jboss.org/browse/JBIDE-20181 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > This is required in relation to JBIDE-19590 to avoid additional steps after importing project from freshly cloned git repository. There is no lib repository until project built at least once, hence after import I have to manually convert it to maven project and update maven project model to download required libraries and update project classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20181) Add m2e nature to o.j.openshift.client and o.j.openshift.client projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20181?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20181: ------------------------------------------ merged and pushed to upstream/master > Add m2e nature to o.j.openshift.client and o.j.openshift.client projects > ------------------------------------------------------------------------ > > Key: JBIDE-20181 > URL: https://issues.jboss.org/browse/JBIDE-20181 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > This is required in relation to JBIDE-19590 to avoid additional steps after importing project from freshly cloned git repository. There is no lib repository until project built at least once, hence after import I have to manually convert it to maven project and update maven project model to download required libraries and update project classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20024: ------------------------------------ Renaming is definitely better since old links to the ID will still work and it means less work for whoever gets saddled with the manual copy-and-paste keywhackery. #wishThereWasAnAPI That said, the links for the marketplace entries for this last Beta use the content/name instead of node/ID: https://github.com/jbosstools/jbosstools-website/blob/master/_config/prod... https://github.com/jbosstools/jbosstools-website/blob/master/_config/prod... So, here's a PR to fix that: https://github.com/jbosstools/jbosstools-website/pull/431 [~maxandersen] when you said "But yes, lets create a new JBoss Tools and Developer Studio entry and get them under one." Do you mean you want TWO new entries (or ideally, just two renamed ones), or that we should COMBINE the existing JBoss Tools and Developer Studio entries into a SINGLE one? I'm going to assume you meant "But yes, [let's] create a *[pair of]* new JBoss Tools and Developer Studio *[entries]* and get [all the old versions merged] under one [connector for JBT and one for JBDS]." Do you agree that renaming is better and that you want TWO merged entries [JBoss Tools, Devstudio], not just ONE [JBoss Tools + Devstudio] ? > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 > * 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20070: ---------------------------------------- I pushed a patch upstream that should have those issues fixed: https://git.eclipse.org/r/#/c/51352/ > Fix minor issues in RedDeer import > ---------------------------------- > > Key: JBIDE-20070 > URL: https://issues.jboss.org/browse/JBIDE-20070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: dialog.png > > > When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not). > List of minor issues: > - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there > - features has listed "Maven" but plugins and tests have "Maven, Java" > - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20024: ------------------------------- Attachment: spring-marketplace-different-updates.png Verified, installing the Spring connector into Luna vs. Mars results in a different source URL, so embedding multiple versions into the same connector would work for us too. [^spring-marketplace-different-updates.png] > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 > * 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20171: ------------------------------------ [~maxandersen] I've already mocked up a buildinfo.json [1] file you can use, but I can't embed it where the JBT aggregator can find it (or else the mojo will fail as above). If you want the SHA used to build back on 2012-11-26_18-50-16, it's here: 2edce933f7d64efbb4d7a5b16be8dadae8de766e [1] http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... So, yes, there's no need to rebuild if all you need to know is which SHA we used. Can I close this issue as Rejected? Do you want the buildinfo_*.json file moved somewhere ? > 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)

10 years, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3465: ----------------------------- Attachment: install-spring-all-features.png install-spring-sites.png * bundle org.json is here: http://download.jboss.org/jbosstools/updates/requirements/orbit/R20150519... (not not yet in our TP) * package org.eclipse.mylyn.internal.java.ui is in bundle org.eclipse.mylyn.ui, which is here: http://download.eclipse.org/mylyn/releases/mars or http://download.eclipse.org/releases/mars (not yet in our TP) So we need to add more stuff to our JBDS TP to enable Spring to be easily installed as part of Central. But I had no problem installing Spring 3.7.1 into Eclipse 4.5, using these sites: !install-spring-sites.png! !install-spring-all-features.png! {code} http://download.eclipse.org/releases/mars http://download.eclipse.org/tools/ajdt/45/dev/update/ http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5 http://dist.springsource.com/release/TOOLS/update/e4.5 {code} Just make sure you check the box for "Contact all update sites" > 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)

10 years, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3465 at 7/3/15 10:07 AM: ----------------------------------------------------------- * bundle org.json is here: http://download.jboss.org/jbosstools/updates/requirements/orbit/R20150519... (not not yet in our TP) * package org.eclipse.mylyn.internal.java.ui is in bundle org.eclipse.mylyn.ui, which is here: http://download.eclipse.org/mylyn/releases/mars or http://download.eclipse.org/releases/mars (not yet in our TP) So we need to add more stuff to our JBDS TP to enable Spring to be easily installed as part of Central. But I had no problem installing Spring 3.7.1 into Eclipse 4.5, using these sites: {code} http://download.eclipse.org/releases/mars http://download.eclipse.org/tools/ajdt/45/dev/update/ http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5 http://dist.springsource.com/release/TOOLS/update/e4.5 {code} [^install-spring-sites.png] Just make sure you check the box for "Contact all update sites" [^install-spring-all-features.png] was (Author: nickboldt): * bundle org.json is here: http://download.jboss.org/jbosstools/updates/requirements/orbit/R20150519... (not not yet in our TP) * package org.eclipse.mylyn.internal.java.ui is in bundle org.eclipse.mylyn.ui, which is here: http://download.eclipse.org/mylyn/releases/mars or http://download.eclipse.org/releases/mars (not yet in our TP) So we need to add more stuff to our JBDS TP to enable Spring to be easily installed as part of Central. But I had no problem installing Spring 3.7.1 into Eclipse 4.5, using these sites: !install-spring-sites.png! !install-spring-all-features.png! {code} http://download.eclipse.org/releases/mars http://download.eclipse.org/tools/ajdt/45/dev/update/ http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5 http://dist.springsource.com/release/TOOLS/update/e4.5 {code} Just make sure you check the box for "Contact all update sites" > 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)

10 years, 9 months

1
0
0 / 0

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

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-19990 at 7/3/15 9:53 AM: ------------------------------------------------------------- It's working for me with JBDS 9.0.0.Beta1 which doesn't include your patch so I can't verify if your fix actually fixes the issue. Fedora 22 KDE Plasma 64bit. Either JSF or HTML5 support enabled. was (Author: vpakan): It's working for me with JBDS 9.0.0.Beta1 which doesn't include your patch so I can't verify if your fix actually fixes the issue. Fedora 22 KDE Plasma 64bit. JSF support enabled. > "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)

10 years, 9 months

1
0
0 / 0

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

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-19990 at 7/3/15 9:51 AM: ------------------------------------------------------------- It's working for me with JBDS 9.0.0.Beta1 which doesn't include your patch so I can't verify if your fix actually fixes the issue. Fedora 22 KDE Plasma 64bit. JSF support enabled. was (Author: vpakan): It's working for me with JBDS 9.0.0.Beta1 which doesn't include your patch so I can't verify if your fix actually fixes the issue. Fedora 22 KDE Plasma 64bit. > "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)

10 years, 9 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 July 2015