August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18131: ------------------------------------- Summary: Split the org.jboss.tools.common.validation plugin in 'core' + 'ui' Key: JBIDE-18131 URL: https://issues.jboss.org/browse/JBIDE-18131 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}: - the {{core}} part would deal with performing the validation (based on the WST Validation Framework) - the {{ui}} part would deal for the preference pages and configuration. ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong. OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.) Can we discuss about that change for JBoss Tools 4.3 ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17656: ------------------------------ Assignee: Vineet Reynolds > Forge crashed Eclipse > --------------------- > > Key: JBIDE-17656 > URL: https://issues.jboss.org/browse/JBIDE-17656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Vineet Reynolds > Fix For: 4.2.0.CR1 > > Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log > > > I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17264) Forge Console crashes when auto-completing values

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ] Vineet Reynolds reassigned JBIDE-17264: --------------------------------------- Assignee: Vineet Reynolds (was: Koen Aers) > Forge Console crashes when auto-completing values > ------------------------------------------------- > > Key: JBIDE-17264 > URL: https://issues.jboss.org/browse/JBIDE-17264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: jstack.txt > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-17656: --------------------------------- Assignee: (was: Koen Aers) > Forge crashed Eclipse > --------------------- > > Key: JBIDE-17656 > URL: https://issues.jboss.org/browse/JBIDE-17656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2 > Reporter: Fred Bricon > Fix For: 4.2.0.CR1 > > Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log > > > I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-17656: --------------------------------- Assignee: Koen Aers > Forge crashed Eclipse > --------------------- > > Key: JBIDE-17656 > URL: https://issues.jboss.org/browse/JBIDE-17656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log > > > I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18117) Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18117?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18117: ---------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 > Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1 > ---------------------------------------------------------------------- > > Key: JBIDE-18117 > URL: https://issues.jboss.org/browse/JBIDE-18117 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > A bug in Eclipse WTP causes the following exception: > {code} > java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl.WebAppImpl cannot be cast to org.eclipse.jst.j2ee.webapplication.WebApp > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.uninstallJAXRSReferencesFromWebApp(JAXRSFacetUninstallDelegate.java:116) > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.execute(JAXRSFacetUninstallDelegate.java:85) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > the problem comes from an evaluation that checks for dynamic project facet version 2.5 or 3.0 but not higher, in {{JAXRSJEEUtils#isWebApp25or40(Object)}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18105: ---------------------------------------- Of course, I would answer Maven Mojos (which are IMO easier to develop, use, share than Ant scripts). I'm not sure it's good to assume that everything in the .target is early access. Look at the current stuff in the jbtcentraltarget file, it contains some things that we could consider as supported. The list of early-access IUs can be deduced by resolution of features in the earlyaccess discovery plugin against the .target. > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3124) JBDS doesn't follow/honor <module-alias> of jboss modules

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/JBDS-3124?page=com.atlassian.jira.plugin.... ] Takayuki Konishi updated JBDS-3124: ----------------------------------- Description: JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. [1] {code:title=MANIFEST.MF|borderStyle=solid} Manifest-Version: 1.0 Class-Path: Dependencies: org.apache.log4j {code} [2] {code} import org.apache.log4j.Logger; ... public class SampleClass{ private static final Logger logger = Logger.getLogger(SampleClass.class); ... {code} [3] {code:title=module.xml|borderStyle=solid} <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> {code} was: JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. [1] MANIFEST.MF Manifest-Version: 1.0 Class-Path: Dependencies: org.apache.log4j [2] In a class: import org.apache.log4j.Logger; ... public class SampleClass{ private static final Logger logger = Logger.getLogger(SampleClass.class); ... [3] module.xml: <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> > JBDS doesn't follow/honor <module-alias> of jboss modules > --------------------------------------------------------- > > Key: JBDS-3124 > URL: https://issues.jboss.org/browse/JBDS-3124 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Beta3 > Reporter: Takayuki Konishi > Attachments: modalias.zip > > > JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. > [1] > {code:title=MANIFEST.MF|borderStyle=solid} > Manifest-Version: 1.0 > Class-Path: > Dependencies: org.apache.log4j > {code} > [2] > {code} > import org.apache.log4j.Logger; > ... > public class SampleClass{ > private static final Logger logger = Logger.getLogger(SampleClass.class); > ... > {code} > [3] > {code:title=module.xml|borderStyle=solid} > <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3124) JBDS doesn't follow/honor <module-alias> of jboss modules

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/JBDS-3124?page=com.atlassian.jira.plugin.... ] Takayuki Konishi updated JBDS-3124: ----------------------------------- Attachment: modalias.zip > JBDS doesn't follow/honor <module-alias> of jboss modules > --------------------------------------------------------- > > Key: JBDS-3124 > URL: https://issues.jboss.org/browse/JBDS-3124 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Beta3 > Reporter: Takayuki Konishi > Attachments: modalias.zip > > > JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. > [1] > MANIFEST.MF > Manifest-Version: 1.0 > Class-Path: > Dependencies: org.apache.log4j > [2] > In a class: > import org.apache.log4j.Logger; > ... > public class SampleClass{ > private static final Logger logger = Logger.getLogger(SampleClass.class); > ... > [3] > module.xml: > <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3124) JBDS doesn't follow/honor <module-alias> of jboss modules

by Takayuki Konishi (JIRA)

Takayuki Konishi created JBDS-3124: -------------------------------------- Summary: JBDS doesn't follow/honor <module-alias> of jboss modules Key: JBDS-3124 URL: https://issues.jboss.org/browse/JBDS-3124 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Beta3 Reporter: Takayuki Konishi JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. [1] MANIFEST.MF Manifest-Version: 1.0 Class-Path: Dependencies: org.apache.log4j [2] In a class: import org.apache.log4j.Logger; ... public class SampleClass{ private static final Logger logger = Logger.getLogger(SampleClass.class); ... [3] module.xml: <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014