August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20412) Hibernate Configuration File wizard should support multiple Hibernate versions

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-20412: ------------------------------------ Summary: Hibernate Configuration File wizard should support multiple Hibernate versions Key: JBIDE-20412 URL: https://issues.jboss.org/browse/JBIDE-20412 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 4.3.0.Beta2 Environment: JBDS 9.0.0.Beta2 Reporter: Jiri Peterka Fix For: 4.3.0.CR1 Currently Hibernate Configuration File wizard is hardcoded to use Hibernate 3.5 and appropriate version of tooling. It should support multiple Hibernate versions so appropriate Hiberante tools libs are used. Highest version of supported Hibernate (currently 4.3) should be offered by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20412) Hibernate Configuration File wizard should support multiple Hibernate versions

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20412?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-20412: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-hibernate/pull/76 > Hibernate Configuration File wizard should support multiple Hibernate versions > ------------------------------------------------------------------------------ > > Key: JBIDE-20412 > URL: https://issues.jboss.org/browse/JBIDE-20412 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Fix For: 4.3.0.CR1 > > > Currently Hibernate Configuration File wizard is hardcoded to use Hibernate 3.5 and appropriate version of tooling. It should support multiple Hibernate versions so appropriate Hiberante tools libs are used. Highest version of supported Hibernate (currently 4.3) should be offered by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20327) [Bower] Automatically open bower.json file after 'Bower init'

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20327?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-20327: -------------------------------- Release Notes Text: (was: Sounds good. Hope we will not face it again ;-)) > [Bower] Automatically open bower.json file after 'Bower init' > ------------------------------------------------------------- > > Key: JBIDE-20327 > URL: https://issues.jboss.org/browse/JBIDE-20327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20327) [Bower] Automatically open bower.json file after 'Bower init'

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20327?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20327: ------------------------------------- Sounds good. Hope we will not face it again ;-) > [Bower] Automatically open bower.json file after 'Bower init' > ------------------------------------------------------------- > > Key: JBIDE-20327 > URL: https://issues.jboss.org/browse/JBIDE-20327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20327) [Bower] Automatically open bower.json file after 'Bower init'

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20327?page=com.atlassian.jira.plugi... ] Ilya Buziuk resolved JBIDE-20327. --------------------------------- Resolution: Cannot Reproduce Bug > [Bower] Automatically open bower.json file after 'Bower init' > ------------------------------------------------------------- > > Key: JBIDE-20327 > URL: https://issues.jboss.org/browse/JBIDE-20327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20327) [Bower] Automatically open bower.json file after 'Bower init'

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20327?page=com.atlassian.jira.plugi... ] Ilya Buziuk resolved JBIDE-20327. --------------------------------- Release Notes Text: Sounds good. Hope we will not face it again ;-) Resolution: Done > [Bower] Automatically open bower.json file after 'Bower init' > ------------------------------------------------------------- > > Key: JBIDE-20327 > URL: https://issues.jboss.org/browse/JBIDE-20327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20327) [Bower] Automatically open bower.json file after 'Bower init'

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20327?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-20327: ------------------------------------ [~ibuziuk], I cannot replicate either. It seems it was some temporary issue. It works with clean workspace. Feel free to close. > [Bower] Automatically open bower.json file after 'Bower init' > ------------------------------------------------------------- > > Key: JBIDE-20327 > URL: https://issues.jboss.org/browse/JBIDE-20327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-455) Add fabric8 feature to the EM features. XML.

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-455?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-455. ------------------------------ Resolution: Done > Add fabric8 feature to the EM features. XML. > -------------------------------------------- > > Key: JBTIS-455 > URL: https://issues.jboss.org/browse/JBTIS-455 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Labels: verified_jbdsis-8.0.3.CR1 > Fix For: 8.0.3.GA > > > The fabric8 feature is missing from the EM feature XML. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-455) Add fabric8 feature to the EM features. XML.

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-455?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-455: ------------------------------- Labels: verified_jbdsis-8.0.3.CR1 (was: release_notes verified_jbdsis-8.0.3.CR1) > Add fabric8 feature to the EM features. XML. > -------------------------------------------- > > Key: JBTIS-455 > URL: https://issues.jboss.org/browse/JBTIS-455 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Labels: verified_jbdsis-8.0.3.CR1 > Fix For: 8.0.3.GA > > > The fabric8 feature is missing from the EM feature XML. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3497) Installer randomly failing to report download statistics

by Jan Richter (JIRA)

Jan Richter created JBDS-3497: --------------------------------- Summary: Installer randomly failing to report download statistics Key: JBDS-3497 URL: https://issues.jboss.org/browse/JBDS-3497 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.0.0.Beta2 Environment: jboss-devstudio-9.0.0.Beta2-installer-standalone.jar Reporter: Jan Richter Priority: Minor In about every third attempt to install JBDS (or maybe more frequently) a p2 error log appears saying this: {noformat}!ENTRY org.eclipse.equinox.p2.artifact.repository 2 0 2015-08-04 08:14:33.521 !MESSAGE Failure reporting download statistics to URL: https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.... !STACK 1 org.eclipse.core.runtime.CoreException: HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:235) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.collectStats(MirrorRequest.java:268) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:235) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707) at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1 at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131) at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) ... 1 more !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2015-08-04 08:14:33.522 !MESSAGE HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt !STACK 1 org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1 at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131) at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2015-08-04 08:14:33.522 !MESSAGE General connection error with response code=-1 {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 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 2015