August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs

by Jeffrey Simpson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ] Jeffrey Simpson commented on JBIDE-18148: ----------------------------------------- I just downloaded and tried 7.1.1 GA and it also failed. > problem with Hibernate package-info.java TypeDefs > ------------------------------------------------- > > Key: JBIDE-18148 > URL: https://issues.jboss.org/browse/JBIDE-18148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: OSX 10.9.4 > Reporter: Jeffrey Simpson > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: eclipseErrors.log > > > I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity. > Here is my Package-info.java > > @org.hibernate.annotations.TypeDefs ( > > { > @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class), > @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class), > @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class), > @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class), > @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class), > @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class), > @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class), > @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class), > @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class), > @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class), > > } > ) > package org.yfu.util.hibernate; -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 edited comment on JBIDE-18105 at 8/29/14 1:07 PM: ----------------------------------------------------------------- WIP: https://github.com/jbosstools/jbosstools-maven-plugins/commit/5e8c9a30ca2... And example of usage: https://github.com/mickaelistria/jbosstools-discovery/commit/2be4b27c0d22... This generates the properties file from plugin.xml + target file. However, it doesn't yet allow to "append" stuff to existing file (but it's not top priority for this milestone). was (Author: mickael_istria): WIP: https://github.com/jbosstools/jbosstools-maven-plugins/commit/5e8c9a30ca2... This generates the properties file from plugin.xml + target file. However, it doesn't yet allow to "append" stuff to existing file (but it's not top priority for this milestone). > 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: Mickael Istria > 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. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: ---------------------------------------- WIP: https://github.com/jbosstools/jbosstools-maven-plugins/commit/5e8c9a30ca2... This generates the properties file from plugin.xml + target file. However, it doesn't yet allow to "append" stuff to existing file (but it's not top priority for this milestone). > 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: Mickael Istria > 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. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18130?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18130: -------------------------------- Fix Version/s: 4.2.0.CR1 > JBDS doesn't follow/honor <module-alias> of jboss modules > --------------------------------------------------------- > > Key: JBIDE-18130 > URL: https://issues.jboss.org/browse/JBIDE-18130 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Takayuki Konishi > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by fede pia (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] fede pia commented on JBIDE-18128: ---------------------------------- [~rob.stryker] Sure, I'll try to replicate the issue on a sample project if I can I'll send it to you. > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18186) XMLMemento cannot parse a file where first node is a comment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18186?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18186: -------------------------------------- Assignee: Rob Stryker > XMLMemento cannot parse a file where first node is a comment > ------------------------------------------------------------ > > Key: JBIDE-18186 > URL: https://issues.jboss.org/browse/JBIDE-18186 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > The class XMLMemento, originally taken from upstream eclipse, is unable to parse a xml input stream if the first node is not an Element. This restriction should be worked around. This is a patch needed by astools for solving /JBIDE-18130 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18186) XMLMemento cannot parse a file where first node is a comment

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18186?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18186: -------------------------------- Fix Version/s: 4.2.0.CR1 > XMLMemento cannot parse a file where first node is a comment > ------------------------------------------------------------ > > Key: JBIDE-18186 > URL: https://issues.jboss.org/browse/JBIDE-18186 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Fix For: 4.2.0.CR1 > > > The class XMLMemento, originally taken from upstream eclipse, is unable to parse a xml input stream if the first node is not an Element. This restriction should be worked around. This is a patch needed by astools for solving /JBIDE-18130 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18186) XMLMemento cannot parse a file where first node is a comment

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-18186: ----------------------------------- Summary: XMLMemento cannot parse a file where first node is a comment Key: JBIDE-18186 URL: https://issues.jboss.org/browse/JBIDE-18186 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common/jst/core Affects Versions: 4.2.0.CR1 Reporter: Rob Stryker The class XMLMemento, originally taken from upstream eclipse, is unable to parse a xml input stream if the first node is not an Element. This restriction should be worked around. This is a patch needed by astools for solving /JBIDE-18130 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3118) Autocomplete selection shows the selected item as a blank line

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3118?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3118: -------------------------------------- // Do you want me to remove the component "jsp/jsf/xml/html source" too? How do I do this? No, I meant this issue is not a bug of "jsp/jsf/xml/html source" component. It looks like an upstream issue. So I remove this component from the JIRA description. I can't reproduce the issue. > Autocomplete selection shows the selected item as a blank line > -------------------------------------------------------------- > > Key: JBDS-3118 > URL: https://issues.jboss.org/browse/JBDS-3118 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 8.0.0.Beta3 > Environment: JBDS 8.0.0.Beta3 > JDK 1.7.0 > Fedora 19 > Reporter: Mustafa Musaji > > See this screenshot - the autocomplete menu shows the selected item as a blank line every time. > https://www.dropbox.com/s/jcemixql25y37f3/Screenshot-JBDSMissingMenu.png -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18128: ------------------------------------- Do you think you could whip up a tiny proof-of-concept project with the maven config, aspect weaving, etc, that would demonstrate the bug? I think it'd be a lot more useful than us trying to replicate it here piece-by-piece or via discussion. Once we have a project that can easily replicate, we can get to work on debugging it and fixing it. > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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