[JBoss JIRA] (JBIDE-26259) Clicking the HTML5 Project in central does nothing
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26259?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26259:
-------------------------------
Fix Version/s: 4.11.x
> Clicking the HTML5 Project in central does nothing
> --------------------------------------------------
>
> Key: JBIDE-26259
> URL: https://issues.jboss.org/browse/JBIDE-26259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.9.0.AM1
> Reporter: Martin Malina
> Assignee: Dmitrii Bocharov
> Priority: Minor
> Fix For: 4.11.x
>
> Attachments: Screenshot from 2018-09-06 16-14-59.png, screenshot-1.png
>
>
> In order to test the PR for JBIDE-26256 I installed JBT into Eclipse Photon. Now I wanted to create the HTML5 Project from Central. But when I click it, it only displays the Operation in progress window for a moment and then it disappears and nothing happens. The same applies for the Java EE Web Project. Other projects from Central work. I tried opening and closing Central and even restarting Eclipse, neither of those helped. Note that this worked ok in devstudio. I only experienced this today in Eclipse Photon + JBT 4.9.0.AM1 abridged.
> I'm on Mac and I installed JBT from http://download.jboss.org/jbosstools/photon/staging/updates/ which currently contains the 4.9.0.AM1 bits.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26458) Import Entities from DB with ManyToMany relationships doesn't manage mappedBy
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26458?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26458:
-------------------------------
Fix Version/s: 4.11.0.AM1
> Import Entities from DB with ManyToMany relationships doesn't manage mappedBy
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26458
> URL: https://issues.jboss.org/browse/JBIDE-26458
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.6.0.Final
> Environment: Eclipse: Oxygen.3a Release (4.7.3a) Build id: 20180405-1200
> DBMS: Sql Anywhere 17.0.9.4857
> Annotations jdk 1.5+
> Hibernate Version 5.2
> Reporter: Matt B
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
> Import from entities tool does not correctly handle the bidirectional ManyToMany relationships because in some cases it does not define mappedBy on one side.
> example:
> {code:java}
> public class SecGroup implements java.io.Serializable {
> ....
> @ManyToMany(fetch = FetchType.LAZY)
> @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = {
> @JoinColumn(name = "GroupId", nullable = false, updatable = false) }, inverseJoinColumns = {
> @JoinColumn(name = "UserId", nullable = false, updatable = false) })
> public Set<SsUsers> getSsUserses() {
> return this.ssUserses;
> }
> ....
> }
> public class SsUsers implements java.io.Serializable {
> ...
> @ManyToMany(fetch = FetchType.LAZY)
> @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = {
> @JoinColumn(name = "UserId", nullable = false, updatable = false) }, inverseJoinColumns = {
> @JoinColumn(name = "GroupId", nullable = false, updatable = false) })
> public Set<SecGroup> getSecGroups() {
> return this.secGroups;
> }
> ...
> }
> {code}
> It must be for example
> {code:java}
> public class SecGroup implements java.io.Serializable {
> ....
> @ManyToMany(fetch = FetchType.LAZY, mappedBy = "secGroups")
> public Set<SsUsers> getSsUserses() {
> return this.ssUserses;
> }
> ....
> }
> public class SsUsers implements java.io.Serializable {
> ...
> @ManyToMany(fetch = FetchType.LAZY)
> @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = {
> @JoinColumn(name = "UserId", nullable = false, updatable = false) }, inverseJoinColumns = {
> @JoinColumn(name = "GroupId", nullable = false, updatable = false) })
> public Set<SecGroup> getSecGroups() {
> return this.secGroups;
> }
> ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26455) Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26455?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26455:
-------------------------------
Fix Version/s: 4.11.x
> Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26455
> URL: https://issues.jboss.org/browse/JBIDE-26455
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.10.0.AM1
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Priority: Major
> Labels: quality
> Fix For: 4.11.x
>
>
> The tool is to support new test strategy for devstudio:
> {quote}
> In the current approach we do a full test cycle on all components with every milestone. This includes also manual steps, etc. and it is resource and time demanding. However some of the components have zero activity, or only a few commits per train. The idea is to limit the testing on low activity components and focus more on the new stuff - like adapters, where it has more value for the current product offering. We do not plan to stop the testing completely. We will monitor github repositories for significant changes. In case we find out there is a significant change on the repository, we will include the component in the milestone testing.{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBIDE-26475) Update lucene version in target platform
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26475?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26475:
-------------------------------
Fix Version/s: 4.11.0.AM1
> Update lucene version in target platform
> ----------------------------------------
>
> Key: JBIDE-26475
> URL: https://issues.jboss.org/browse/JBIDE-26475
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, target-platform
> Affects Versions: 4.10.0.AM1
> Reporter: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
> Investigate and identify why do we multiple version of org.apache.lucene.8 packages in target plaform(e.g. in eclipse TP is version 7.5, but in target platform is 7.1).
> It would be also nice, if comments would be added in target file to know why we have different versions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months