September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23275: ---------------------------------- Priority: Minor (was: Major) > Rename doesn't change fully qualified name in job.xml file > ---------------------------------------------------------- > > Key: JBIDE-23275 > URL: https://issues.jboss.org/browse/JBIDE-23275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip > > > Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name. > For example, when I have batchlet class > {code:java} > package test; > public class BatchletWithProperty extends AbstractBatchlet { > ... > } > {code} > ...and job.xml > {code:xml} > <job ...> > <step id="step1"> > <batchlet ref="test.BatchletWithProperty">  > ... > </batchlet> > </step> > ... > </job> > {code} > ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml. > Renaming works properly when I refer to class using name coming from @Named annotation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23275: ---------------------------------- Priority: Major (was: Minor) > Rename doesn't change fully qualified name in job.xml file > ---------------------------------------------------------- > > Key: JBIDE-23275 > URL: https://issues.jboss.org/browse/JBIDE-23275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip > > > Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name. > For example, when I have batchlet class > {code:java} > package test; > public class BatchletWithProperty extends AbstractBatchlet { > ... > } > {code} > ...and job.xml > {code:xml} > <job ...> > <step id="step1"> > <batchlet ref="test.BatchletWithProperty">  > ... > </batchlet> > </step> > ... > </job> > {code} > ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml. > Renaming works properly when I refer to class using name coming from @Named annotation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23278) Validation of class reference in job.xml produces false-positive warning

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-23278: ------------------------------------ Summary: Validation of class reference in job.xml produces false-positive warning Key: JBIDE-23278 URL: https://issues.jboss.org/browse/JBIDE-23278 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.4.2.AM1 Environment: Fedora 24 Reporter: Lukáš Valach Attachments: BatchRenameManualTest.zip, Rename-Warning.png When I refer to some class using fully qualified name and that class is annotated by @Named or is mentioned in bean.xml, then the eclipse shows warning "Item ... not found." although class exists and code is valid (test passes). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-4059: -------------------------------------- Thanks for working on the issue. I checked rh-eclipse46-devstudio-10.2-0.20160930.0121.el7.x86_64.rpm; all fine except libnotify.so.1 (needed for .../org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/components/libmozgnome.so). As I wrote a week ago, libnotify.so.1 cannot be resolved in RHEL 7. I believe that Eclipse wouldn't load that libmozgnome.so. I see two possibilities: 1. Maybe libmozgnome.so is dead code and I'd be happy to add the reference to libnotify.so.1 as a known false positive (though cutting the dead code out would be better). 2. Maybe it's not dead; then libmozgnome.so would need to be fixed somehow - supplemented with libnotify.so.1 or rebuilt against libnotify.so.4 etc. Please look into this specific problem. I'd like to reopen this issue but I don't see how, maybe I'm missing permissions? > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23192) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23192?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23192. ------------------------------------ > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate] > ------------------------------------------------------------------- > > Key: JBIDE-23192 > URL: https://issues.jboss.org/browse/JBIDE-23192 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Hibernate]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23096) Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23096?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23096. ------------------------------------ verified in git > Remove the definition and uses of class org.jboss.tools.hibernate.runtime.spi.IHibernateMappingGlobalSettings > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23096 > URL: https://issues.jboss.org/browse/JBIDE-23096 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23172) Bump the version identifiers to 5.1.2

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23172?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23172. ------------------------------------ > Bump the version identifiers to 5.1.2 > -------------------------------------- > > Key: JBIDE-23172 > URL: https://issues.jboss.org/browse/JBIDE-23172 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23273) Implement org.jboss.tools.hibernate.runtime.v_x_y.internal.HibernateMappingExporterFacadeTest

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23273?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23273: ------------------------------ Story Points: 8 (was: 4) Summary: Implement org.jboss.tools.hibernate.runtime.v_x_y.internal.HibernateMappingExporterFacadeTest (was: Implement org.jboss.tools.hibernate.runtime.v_3_6.internal.HibernateMappingExporterFacadeTest) > Implement org.jboss.tools.hibernate.runtime.v_x_y.internal.HibernateMappingExporterFacadeTest > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23273 > URL: https://issues.jboss.org/browse/JBIDE-23273 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.2.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4065: ------------------------------------- Good point, Alexey. I think this is a good question for Rob. [~rob.stryker], what's gonna happen if your workspace has a cdk server adapter automatically created during devsuite install and then you create a new devsuite installation and start the new devstudio with the old workspace? Will a second cdk adapter appear? My guess would be that since the Vagrantfile path is most likely the same, the new addition will be ignored and only the old cdk adapter will be present. Am I correct? > DevStudio 1.1 Installer unfriendly when 1.0 present > --------------------------------------------------- > > Key: JBDS-4065 > URL: https://issues.jboss.org/browse/JBDS-4065 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 10, DevSuite Installer 1.0 had been run > Reporter: Rick Wagner > Assignee: Rob Stryker > > When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK. > Observations: > - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned). > - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory. > - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is? > - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup. > - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4074) requirements.json definition should contain download info for all supported platforms

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4074: ----------------------------------- Summary: requirements.json definition should contain download info for all supported platforms Key: JBDS-4074 URL: https://issues.jboss.org/browse/JBDS-4074 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Affects Versions: 10.2.0.AM1 Environment: Windows, Mac OS X Reporter: Denis Golovin Currently requirements.json contains only windows specific download info, its format should let define info for all supported platforms. For example vagrant info should have links do download installers for windows and Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016