May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11752) CLONE - jBPM Component N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11752: ------------------------------------------- Summary: CLONE - jBPM Component N&N Key: JBIDE-11752 URL: https://issues.jboss.org/browse/JBIDE-11752 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jbpm Reporter: Denis Golovin Assignee: Koen Aers Fix For: 3.3.0.Beta1 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11746) CLONE - GWT Integration Component Description in N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11746: ------------------------------------------- Summary: CLONE - GWT Integration Component Description in N&N Key: JBIDE-11746 URL: https://issues.jboss.org/browse/JBIDE-11746 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: GWT Affects Versions: 3.3.0.M2 Reporter: Denis Golovin Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-11761) CLONE - Maven Integration in JBT 3.3.0 Beta 1 N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11761: ------------------------------------------- Summary: CLONE - Maven Integration in JBT 3.3.0 Beta 1 N&N Key: JBIDE-11761 URL: https://issues.jboss.org/browse/JBIDE-11761 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven Affects Versions: 3.3.0.Beta1 Reporter: Max Rydahl Andersen Assignee: Fred Bricon Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] (JBDS-2137) provide staging site for devstudio-directory.xml file; update rel guide docs to point to new URL

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2137: -------------------------------- Summary: provide staging site for devstudio-directory.xml file; update rel guide docs to point to new URL Key: JBDS-2137 URL: https://issues.jboss.org/browse/JBDS-2137 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central, updatesite Affects Versions: 5.0.0.Beta2, 5.0.0.Beta1-SOA Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.Beta3 I should have pushed these bits to a DIFFERENT directory.xml file. Will fix that so that public == QE'd and EA released, whereas there's a different URL which QE can use with the -D flag to test (without having to jump through complex hoops. On 05/11/2012 12:51 PM, Max Andersen wrote: > Yes but nothing should be out on EA before QE and team gives green light. That's my problem here. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] (JBDS-2136) ESB visualizer - freezing a node locks all nodes

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2136: ---------------------------------- Summary: ESB visualizer - freezing a node locks all nodes Key: JBDS-2136 URL: https://issues.jboss.org/browse/JBDS-2136 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Beta1-SOA Environment: Version: 5.0.0.Beta3 Build id: v20120510-2156-H157-Beta3 Build date: 20120510-2156 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 5.0.0.Beta2-SOA This works as advertised: In the View menu and on the right-click popup menu when you right-click on a node in the view, you'll see a new menu - Freeze Node on Double-click. By default this is unchecked. If unchecked, when the user double-clicks on a node, it opens the ESB editor with that particular component selected. The only exception is when you double-click the root node that is now named the same as the file you have opened. In that case, it simply opens the file if not already open. In both cases, the editor gains focus. If checked, double-clicking on a node freezes it in the view. The visual indicator is a wider blue border around the frozen node. Double-click again and the node is unfrozen and the node border returns to normal. If frozen, the node will stay in place when the layout is refreshed or changed. ------------------------- One thing - the node-freezing seems to be global - if you right click/freeze one node - they are all frozen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11757) CLONE - BPEL Component N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11757: ------------------------------------------- Summary: CLONE - BPEL Component N&N Key: JBIDE-11757 URL: https://issues.jboss.org/browse/JBIDE-11757 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: BPEL Reporter: Brian Fitzpatrick Assignee: Robert (Bob) Brodt Fix For: 3.3.0.Beta1 Create a N&N for any BPEL N&N issues for the M2 release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8838) add source feature to JBT components; generate source plugins w/ Tycho

by Nick Boldt (JIRA)

add source feature to JBT components; generate source plugins w/ Tycho ---------------------------------------------------------------------- Key: JBIDE-8838 URL: https://issues.jboss.org/browse/JBIDE-8838 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 As per example done in https://bugs.eclipse.org/bugs/show_bug.cgi?id=344515 and http://wiki.eclipse.org/Minerva#Source, the rest of JBT needs source features/plugins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
63
0 / 0

[JBoss JIRA] (JBDS-2124) CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBDS-2124?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved JBDS-2124. -------------------------------- Resolution: Done Done > CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null > ------------------------------------------------------------------------------------ > > Key: JBDS-2124 > URL: https://issues.jboss.org/browse/JBDS-2124 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.Beta1-SOA > Environment: JBDS 5.0 Beta 3 with SOA-tooling Beta 1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Blocker > Fix For: 5.0.0.Beta2-SOA > > > When I get to this step in the XML Data File import wizard (executed via the Consume Web Service action set, step generate relational models from WSDL), and I select a couple of attributes to be transformed into relational columns, I cannot proceed due to the wizard's claim that my xQuery is empty or null. > The source XML file is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source

by arjan tijms (JIRA)

Easily adding full JBoss AS source ---------------------------------- Key: JBIDE-9309 URL: https://issues.jboss.org/browse/JBIDE-9309 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: arjan tijms Assignee: Rob Stryker The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers. Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job. For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder. For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious. I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

10
30
0 / 0

[JBoss JIRA] (JBIDE-11154) In Beta1c, publish to openshift is non-functional

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11154: ----------------------------------- Summary: In Beta1c, publish to openshift is non-functional Key: JBIDE-11154 URL: https://issues.jboss.org/browse/JBIDE-11154 Project: Tools (JBoss Tools) Issue Type: Bug Environment: MacOSX Lion - 32-bit installation of JBDS 5 Beta1c on 64-bit OS Reporter: Burr Sutter Assignee: Andre Dietisheim Steps to reproduce: 1) click on HTML5, SpringMVC or RichFaces archetype, name the project "poh5", "springmvc" or "richfaces-demo" 2) deploy to localhost:8080 (AS 7.1) to see that the application runs correctly 3) Using the OpenShift Application wizard in JBoss Central - built a new application, and select one of the existing projects. 4) Using the browser, login into the openshift express console. If you hit the URL for your openshift app, you should see the default application - index.html and health.jsp 5) Right click on the openshift app in the Servers tab and select Publish, now revisit the URL for the application, nothing shows up. The last few lines in the console look like the following: [WARNING] The requested profile "openshift" could not be activated because it does not exist. Emptying tmp dir: /var/lib/libra/e1744a38d9c9410e99fd9ecadec2fa64/spring/jbossas-7.0/standalone/tmp/vfs Emptying tmp dir: /var/lib/libra/e1744a38d9c9410e99fd9ecadec2fa64/spring/jbossas-7.0/standalone/tmp/work Starting application... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
23
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 May 2012