June 2013 - jbosstools-issues - Jboss List Archives

[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: --------------------------------- mvn -U clean deploy from Jenkins target-platform job - 4.0.1.Final 14:42:10 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project target-platform: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.integration-stack:target-platform:pom:4.0.1.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Access denied to: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos..., ReasonPhrase:Forbidden. -> [Help 1] 14:42:10 [ERROR] 14:42:10 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 14:42:10 [ERROR] Re-run Maven using the -X switch to enable full debug logging. 14:42:10 [ERROR] 14:42:10 [ERROR] For more information about the errors and possible solutions, please read the following articles: 14:42:10 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 14:42:10 Build step 'Invoke top-level Maven targets' marked build as failure > 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 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.0 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14739) Generated JBoss WS SOAP message is invalid

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-14739: ------------------------------------------- Tested the fix in the WISE 2.1.0-SNAPSHOT build and it does seem to solve the issue. Will update to the 2.0.2.Final build when it is available. Thanks Alessio! > Generated JBoss WS SOAP message is invalid > ------------------------------------------ > > Key: JBIDE-14739 > URL: https://issues.jboss.org/browse/JBIDE-14739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Beta2 > > > STEP: create dynamic web project and register web.xml (to be able to create simple soap web service) > STEP: create simple web service (File -> New -> Other -> JBoss Tools -> Simple Web Service with default settings > STEP: run a server, deploy a project > STEP: open Web Service Tester, enter url of web service and try to invoke its default method (sayHello) > STEP: open the generated web service class (HelloWorld.java) > STEP: add a new web method like this: > {code} > @WebMethod() > public String echo() { > return "Hello World"; > } > {code} redeploy the project > STEP: open web service tester again, url should be still set on text box, so click on the "Get from WSDL" > STEP: in opened dialog, choose the new method "echo", and press OK > ASSERT: generated request message has valid format > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header/> > <soap:Body> > <ns2:echo xmlns:ns2="http://webservices.samples.jboss.org/"/> > </soap:Body> > </soap:Envelope> > {code} > ASSERT: invoking the generated message tends to valid response > FAIL: generated request message has invalid format > {code} > <?xml version="1.0" encoding="utf-8" standalone="yes" ?> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > <soap:Header> > </soap:Header> > <soap:Body> > </soap:Body> > </soap:Envelope> > {code} > FAIL: invoking the message throws a SOAPFaultException: > {code} > java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing. > at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1823) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing. > at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) > at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450) > at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381) > at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502) > at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} > This issue occurs only the first time. After the first try, other tries are successful in words of SOAP message generation. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14694: --------------------------------------- I think we need to remove part of the patch that causes a cheatsheet not to be opened when importing a non maven project. > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1420) Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1420?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen closed JBIDE-1420. -------------------------------------- Resolution: Out of Date > Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-1420 > URL: https://issues.jboss.org/browse/JBIDE-1420 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 2.0.0.GA > Reporter: Alexander Chabatar > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: new_and_noteworthy > Fix For: LATER > > Attachments: dialog - screenshot.jpg, ecxeption - screenshot.jpg, JBIDE-1420_20080612.zip, JUnit_patch_20080612.zip > > > 1) add Test Connection button - should be helpful. > 2) Finish button is always enabled. For example if Database dialect is selected but no driver class, no URL, user. Validation might show a warning. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8529) Duplicate EJB wizards

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8529?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-8529. ---------------------------------------- Resolution: Duplicate Issue JBIDE-11439 deprecated the wizards making this irrelevant. > Duplicate EJB wizards > --------------------- > > Key: JBIDE-8529 > URL: https://issues.jboss.org/browse/JBIDE-8529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: ejb3 > Affects Versions: 3.2.0.Final > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Fix For: 3.3.x > > Attachments: duplicate-wizards.png > > > There are dupliate wizards for creating EJB3 Message-driven bean and EJB3 Session Bean. > For creating Message Driven bean there is: > * EJB/EJB3 Message Driven Bean > * EJB/Message-Driven Bean (EJB3.x) > For creating Session bean theere is: > * EJB/EJB3 Session Bean > * EJB/Session Bean (EJB 3.x) > Both variants create classes, the 2nd variant of both is quite better (generates additional annotations) > Those duplicates should be removed if possible. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14835) Test testAddRemovingDOMElements fails

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-14835: ---------------------------------------------- Summary: Test testAddRemovingDOMElements fails Key: JBIDE-14835 URL: https://issues.jboss.org/browse/JBIDE-14835 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 4.1.0.Beta1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.1.0.Beta2 org.jboss.tools.vpe.xulrunner.test.DOMCreatingTest.testAddRemovingDOMElements (from org.jboss.tools.vpe.xulrunner.test.XulRunnerAllTests) Failing for the past 1 build (Since Unstable#374 ) Took 0.58 sec. add description Stacktrace java.lang.NullPointerException at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.getDOMDocument(XulRunnerEditor.java:242) at org.jboss.tools.vpe.xulrunner.test.DOMCreatingTest.testAddRemovingDOMElements(DOMCreatingTest.java:32) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14540) forge is started even though I have not used it

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14540?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-14540: --------------------------------- Assignee: Koen Aers > forge is started even though I have not used it > ----------------------------------------------- > > Key: JBIDE-14540 > URL: https://issues.jboss.org/browse/JBIDE-14540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > > looks like forge 2 startsup instantly and not only takes up memory but also starts multiple threads even though I have not used forge at all. > That is very nasty behavior for a plugin. > Not sure what it is/was doing but this is 5-10 minutes after startup and it is still in some timed/queuing . > "Reference Reaper" daemon prio=5 tid=0x000000011204f800 nid=0xa00b in Object.wait() [0x000 > 0000111100000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000007dca8cab8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x00000007dca8cab8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at org.jboss.modules.ref.References$ReaperThread.run(References.java:68) > "Forge Container org.jboss.forge.container.ForgeImpl@57f8b993" prio=5 tid=0x0000000110f25000 nid=0xa107 waiting on condition [0x0000000111800000] > java.lang.Thread.State: TIMED_WAITING (sleeping) > at java.lang.Thread.sleep(Native Method) > at org.jboss.forge.container.ForgeImpl.start(ForgeImpl.java:151) > at org.jboss.forge.container.ForgeImpl$1.run(ForgeImpl.java:92) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14761) Forge Wizards: NPE when project name is empty

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14761?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-14761: --------------------------------- Assignee: Koen Aers > Forge Wizards: NPE when project name is empty > --------------------------------------------- > > Key: JBIDE-14761 > URL: https://issues.jboss.org/browse/JBIDE-14761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > > It would be very nice to have a check for empty text field in new project wizard. > {code} > java.lang.NullPointerException > at java.io.File.<init>(File.java:291) > at org.jboss.tools.forge.importer.ProjectImporter.createMavenProjectInfo(ProjectImporter.java:50) > at org.jboss.tools.forge.importer.ProjectImporter.getProjectToImport(ProjectImporter.java:63) > at org.jboss.tools.forge.importer.ProjectImporter.access$0(ProjectImporter.java:61) > at org.jboss.tools.forge.importer.ProjectImporter$1.runInWorkspace(ProjectImporter.java:34) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14686) ForgeWizards: Outline field in editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14686?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-14686: --------------------------------- Assignee: Koen Aers > ForgeWizards: Outline field in editor > -------------------------------------- > > Key: JBIDE-14686 > URL: https://issues.jboss.org/browse/JBIDE-14686 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > > New field should be outlined in editor after click on finish button in New Field Wizard. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14686) ForgeWizards: Outline field in editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14686?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14686. ------------------------------- Resolution: Won't Fix The 'New Field' wizard is not included anymore. Entities and Fields should be created using the wizards provided by the Dali tools. > ForgeWizards: Outline field in editor > -------------------------------------- > > Key: JBIDE-14686 > URL: https://issues.jboss.org/browse/JBIDE-14686 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > > New field should be outlined in editor after click on finish button in New Field Wizard. -- 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, 10 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 June 2013