[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Antal Varga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Antal Varga updated JBIDE-23149:
--------------------------------
Attachment: RMAReverseEngineeringStrategy.java
BaseReverseEngineeringStrategy.java
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.2.AM2
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23017:
-------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.AM1)
> use sshfs to speed up publishing process
> -----------------------------------------
>
> Key: JBIDE-23017
> URL: https://issues.jboss.org/browse/JBIDE-23017
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org.
> If we could simply copy bits over sshfs, the process might be a lot faster than these times:
> {code}
> JBT coretests 1.1G: 59m20
> JBT core 1.2G: 64m23
> devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13
> devstudio (copy from local to www.qa) 3.1G: 6mins(?)
> {code}
> To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-899) Teiid - Failing smoke tests when running from mvn
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-899:
---------------------------------------
Summary: Teiid - Failing smoke tests when running from mvn
Key: JBTIS-899
URL: https://issues.jboss.org/browse/JBTIS-899
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.4.0.Alpha1
Reporter: Andrej Podhradsky
Assignee: Matus Makovy
Priority: Critical
Teiid smoke tests are failing on Neon. But only when running from mvn (from IDE the tests pass).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode
by Alexander Kurtakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ]
Alexander Kurtakov commented on JBIDE-20045:
--------------------------------------------
So these screenshots are all on various Windows versions? Please in the future when showing visual/rendering issues please make clear which OS and version this is on.
> Software/Update page looks bad in Dark mode
> -------------------------------------------
>
> Key: JBIDE-20045
> URL: https://issues.jboss.org/browse/JBIDE-20045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.3.x
>
> Attachments: central.png, windowws-screenshot.png
>
>
> - Enable Eclipse Dark Theme in Preferences > Appearance,
> - Open Central, click on the Software Update page
> - Make sure Early Access is enabled
> - Check this :
> !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png!
> - grey areas around the checkboxes and the titles
> - blue links don't look good
> - Early-Access items are not highlighted (even after fixing JBIDE-20007)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-896) Drools - Use Jira states for skipping some test cases which are supposed to fail
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-896?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky edited comment on JBTIS-896 at 9/16/16 8:17 AM:
------------------------------------------------------------------
Please have a look at org.jboss.tools.common.reddeer.condition.IssueIsClosed.
You don't need to skip the whole test, you can just use something like
{code}
if (jiraClient.isIssueClosed(issueId) {
assertWhatYouWant(...)
}
{code}
was (Author: apodhrad):
Please have a look at org.jboss.tools.common.reddeer.condition.IssueIsClosed
> Drools - Use Jira states for skipping some test cases which are supposed to fail
> --------------------------------------------------------------------------------
>
> Key: JBTIS-896
> URL: https://issues.jboss.org/browse/JBTIS-896
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM, QE
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andrej Podhradsky
> Assignee: Tomas David
> Fix For: 4.4.0.Alpha1
>
>
> Currently, smoke tests fail due to a known issue in drools plugin (DROOLS-1250). Please use an existing logic for checking Jira states so that we can skip the testing of Problems view (e.g. by setting reddeer.skipUnfixedIssues=true).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months