April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21210) bump currentversion.properties to latest JBT versions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21210?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21210. --------------------------------- Verified in the master repo as well as in JBDS 10.0.0.Alpha1 B5251 > bump currentversion.properties to latest JBT versions > ----------------------------------------------------- > > Key: JBIDE-21210 > URL: https://issues.jboss.org/browse/JBIDE-21210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Per https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versio... it's time to update the values of default.version in foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21382?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21382. --------------------------------- I verified that the dependency to org.eclipse.core.runtime.compatibility is removed from org.jboss.tools.common.model.ui in JBDS 10.0.0.Alpha1 B5251. (I also checked and it was present in JBDS 9.1.0.GA.) Closing. > remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21382 > URL: https://issues.jboss.org/browse/JBIDE-21382 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs: > * o.j.t.common.model.ui, > * o.e.platform.feature, > * o.e.m2e.feature, > * o.e.datatools.oda.cshelp, > * o.aspectj.ajde, > * o.e.wst.xml.xpath.core, and > * o.e.birt.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21124) Server Adapter: XML Configuration and Filesets nodes leak to non-JBoss server adapters

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21124?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21124. --------------------------------- I can still see this under a Tomcat server adapter. But apparently that is expected. From the maintenance JIRA (JBIDE-21116): {quote} Rob confirmed that Tomcat will continue to have this. All org.eclipse.jst.* server adapters have this by default. OpenShift had this by mistake and that is fixed as confirmed by Marian. Closing. {quote} > Server Adapter: XML Configuration and Filesets nodes leak to non-JBoss server adapters > -------------------------------------------------------------------------------------- > > Key: JBIDE-21124 > URL: https://issues.jboss.org/browse/JBIDE-21124 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: server_adapter > Fix For: 4.4.0.Alpha1 > > > The XML Configuration and Filesets nodes provided by JBoss Tools leak to non-JBoss server adapters. > !http://content.screencast.com/users/fbricon/folders/Jing/media/be573a07-eff4-4c75-90a0-7334cabb0e09/00000228.png|width=450! > I find these confusing. After [~rob.stryker] explained me how they work, I can see some value in it, however, I think they should be added to non-JBoss servers on an opt-in basis. > [~maxandersen] wdyt? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21441: ----------------------------------- Sprint: devex #113 April 2016 > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be packed jars not unpacked directories for efficiency sake

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Mickael Istria updated JBIDE-3628: ---------------------------------- Priority: Minor (was: Critical) > Plugins should be packed jars not unpacked directories for efficiency sake > -------------------------------------------------------------------------- > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core, hibernate, jsf, visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.x, 4.4.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. Help content that is stored in zip files should be unpacked > 6. TBD -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be packed jars not unpacked directories for efficiency sake

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Mickael Istria updated JBIDE-3628: ---------------------------------- Fix Version/s: 4.4.x > Plugins should be packed jars not unpacked directories for efficiency sake > -------------------------------------------------------------------------- > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core, hibernate, jsf, visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.x, 4.4.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. Help content that is stored in zip files should be unpacked > 6. TBD -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22267) Egit perspective "disappears" after installing JBoss Tools from Eclipse Marketplace

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22267?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22267. ------------------------------- Closing as rejected. > Egit perspective "disappears" after installing JBoss Tools from Eclipse Marketplace > ----------------------------------------------------------------------------------- > > Key: JBIDE-22267 > URL: https://issues.jboss.org/browse/JBIDE-22267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Affects Versions: 4.3.1.Final > Environment: Arch Linux x86_64, Oracle JDK 1.8.0_92, Eclipse JEE Mars 2 , JBoss Tools 4.3.1.Final > Reporter: Leonardo Vieira > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Final > > Attachments: bookmarks.xml, Configuration.log, eclipse.ini, Error.log, features.log, plugins.log > > > Hi, > I have Eclipse JEE Mars 2 installed and when i tried to install JBoss Tools 4.3.1.Final from Eclipse Marketplace, after restart, the Egit perspective was gone. Searching for previous bug reports, i found these two: JBIDE-21838, JBIDE-21821, both closed. Now it seems the solution provided earlier didn't really solve the problem. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3861) Can't donwload some example projects from central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3861?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBDS-3861: ---------------------------------- I guess, that ide-config.properties is just missing entry for featured.examples.url|devstudio|10. I'm not fure where to change this file. Maybe [~nickboldt] could take a look? > Can't donwload some example projects from central > ------------------------------------------------- > > Key: JBDS-3861 > URL: https://issues.jboss.org/browse/JBDS-3861 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 10.0.0.Alpha1 > Environment: Devstudio 10.0.0.Alpha1-v20160427-0539-B5240 > Reporter: Jan Richter > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.0.0.Alpha2 > > > Trying to download some example projects from central simply opens a progress dialog, which quickly disappears and nothing happens. So far I found it happening with HTML5 project, AngularJS forge and Java EE Web Project - but there might be more. > Note that in JBT master they all work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-710) JBDS 9.1 GA: Document a use case for Hibernate Tooling

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-710: ---------------------------------- Assignee: Misha Ali (was: Supriya Bharadwaj) > JBDS 9.1 GA: Document a use case for Hibernate Tooling > ------------------------------------------------------ > > Key: TOOLSDOC-710 > URL: https://issues.jboss.org/browse/TOOLSDOC-710 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Hibernate-tools > Fix For: 9.1 GA > > > Draft a use case and document it for Hibernate Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-710) JBDS 9.1 GA: Document a use case for Hibernate Tooling

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-710: ------------------------------------ Added feedback to google doc. > JBDS 9.1 GA: Document a use case for Hibernate Tooling > ------------------------------------------------------ > > Key: TOOLSDOC-710 > URL: https://issues.jboss.org/browse/TOOLSDOC-710 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Hibernate-tools > Fix For: 9.1 GA > > > Draft a use case and document it for Hibernate Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016