July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15068: ---------------------------------------- Attachment: jstack-forge.txt jstack-forge.txt stacktrace from forge > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Fix For: 4.1.0.CR1 > > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png, jstack-forge.txt > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-69) Refactor TP POM for nexus deployment consistency

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-69?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-69: --------------------------------- Merge in TP POM for nexus changes to master. https://github.com/jbosstools/jbosstools-integration-stack/pull/51 > Refactor TP POM for nexus deployment consistency > ------------------------------------------------ > > Key: JBTIS-69 > URL: https://issues.jboss.org/browse/JBTIS-69 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.0.0, 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.0.Beta1 > > > Depends on the GAV of the thing you deployed. > I might consider refactoring your pom so that it ends up in this folder, > for consistency: > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > As you can see, we have 2 TPs for each (unified, multiple) of > jbdevstudio and jbosstools. You could have jbds-is and jbt-is, or > perhaps jbdevstudio-integration and jbosstools-integration. > The way the path is produced comes from the pom: > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > <groupId>org.jboss.tools.targetplatforms</groupId> (from parent) > <artifactId>jbdevstudio-multiple</artifactId> > <version>4.30.5.Alpha3</version> (from parent) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15068: ---------------------------------------- Attachment: (was: jstack-eclipse.txt) > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Fix For: 4.1.0.CR1 > > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png, jstack-forge.txt > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15068: ---------------------------------------- Attachment: jstack-eclipse.txt jstack-eclipse.txt shows what looks like a livelock in aether > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Fix For: 4.1.0.CR1 > > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png, jstack-eclipse.txt > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15068: --------------------------------------------- I can verify this bug on OSX too. i'll attach jstack files. > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Fix For: 4.1.0.CR1 > > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15068: ---------------------------------------- Fix Version/s: 4.1.0.CR1 > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Fix For: 4.1.0.CR1 > > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because it's using "multiple" with bugs in p2.mirrors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Mickael Istria resolved JBDS-2673. ---------------------------------- Resolution: Done Avoiding p2.mirrors on Kepler site fixed the issue. Also, jobs were updated to consume unified instead of multiple. As for mutliple vs unified and where to put JBDS target-platform, see JBDS-2674. > Can't build JBDS because it's using "multiple" with bugs in p2.mirrors > ---------------------------------------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15035) Add tomcat runtime detection to JBT update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15035?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15035: ------------------------------- Priority: Blocker (was: Critical) > Add tomcat runtime detection to JBT update site > ----------------------------------------------- > > Key: JBIDE-15035 > URL: https://issues.jboss.org/browse/JBIDE-15035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 4.1.0.Beta2 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.CR1 > > > Following JBIDE-14944, can we make sure the Tomcat Detection feature is added to the JBT update site? > See https://github.com/jbosstools/jbosstools-server/blob/master/site/category... for feature ids -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15059 at 7/1/13 10:34 AM: ------------------------------------------------------------------- I'll have to double check the code in EGit and verify once more how things behave if I push via EGit. The git cmd line definitely updates the local tracking branch when you push. If this is done via a fetch (or an internal porcellaine cmd) is not clear to me: http://www.gitguys.com/topics/tracking-branches-and-remote-tracking-branc... - "Publish The Local Commit" 'Next, the git push command causes the remote-tracking branch to be updated with the latest updates from the remote repository' was (Author: adietish): I'll have to double check the code in EGit. The git cmd line definitely updates the local tracking branch when you push. If this is done via a fetch (or an internal porcellaine cmd) is not clear to me: http://www.gitguys.com/topics/tracking-branches-and-remote-tracking-branc... - "Publish The Local Commit" 'Next, the git push command causes the remote-tracking branch to be updated with the latest updates from the remote repository' > Server adapter: tells me that there are local commits that I can publish even though there are none > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-15059 > URL: https://issues.jboss.org/browse/JBIDE-15059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.CR1, 4.2.0.Alpha1 > > Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png > > > 1. EXEC: launch OpenShift Application wizard > 2. EXEC: create a new application and have it imported to your workspace > 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes* > !committed-changes-to-publish.png! > 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of origin by 1) > !is-ahead-1.png! (*wrong!* since we pushed) > 5. EXEC: Pick your server adapter and tell it to publish to OpenShift > Result: > The adapter tells you that you that there are local commits that you may push. (*wrong!*) > !committed-changes-to-publish.png! > Expected: > We just pushed there cannot be local commits that were not pushed yet > 6. EXEC: Confirm the dialog and tell it to publish > Result: > It tells you that OpenShift is already up-to-date (which is true!) > !already-up-to-date.png! > 7. EXEC: pick Team->Fetch from Upstream > 8 ASSERT: > The remote "is ahead of" state of the current branch compared to origin is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed). > !is-ahead-0.png! > If you now publish via adapter it'll tell you that there are no local changes that you can push. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13127) Scala jars added to deployment when they should not

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13127?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13127: -------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Scala jars added to deployment when they should not > --------------------------------------------------- > > Key: JBIDE-13127 > URL: https://issues.jboss.org/browse/JBIDE-13127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Galder Zamarreño > Assignee: Fred Bricon > Labels: scala, upstream > Fix For: 4.2.x > > > Hmmm, seems like we've gone the opposite way now. > My lift dependencies, which bring in Scala, are defined as provided: > {code}<dependency> > <groupId>net.liftweb</groupId> > <artifactId>lift-mapper_${version.scala}</artifactId> > <version>2.4</version> > <scope>provided</scope> > </dependency>{code} > And now, you're adding the Scala jars to the WAR when it shouldn't? See screenshot: > https://dl.dropbox.com/u/6148072/Screen%20Shot%202012-11-14%20at%206.26.4... > Who's responsibility is this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013