January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2440) JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2440?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-2440: ------------------------------------- Fred, this JIRA is only so that we have a reference for the issue that is being solved ad-hoc via emails. This affected all of the archetypes from JBoss Central - they didn't work with EAP 6.0.1 maven repo. We haven't checked which are already fixed. > JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2440 > URL: https://issues.jboss.org/browse/JBDS-2440 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 6.0.1.GA > > > This problem will not be solved in a JBDS build, but it must be resolved in time for the JBDS 6.0.1 release. > The issue is that the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12299) Too restrictive dependency on org.eclipse.mylyn.commons.ui

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12299?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-12299: ------------------------------------------ Still unresolved. Is this going to be done in 3.3.2 ? > Too restrictive dependency on org.eclipse.mylyn.commons.ui > ---------------------------------------------------------- > > Key: JBIDE-12299 > URL: https://issues.jboss.org/browse/JBIDE-12299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 3.3.0.Final > Reporter: Mickael Istria > Assignee: Snjezana Peco > Priority: Critical > Fix For: 3.3.2 > > > Bundle org.jboss.tools.project.examples has a very restrictive dependency range on org.eclipse.mylyn.commons.ui that prevent it from being installed on Eclipse Juno, which ships with Mylyn 3.8. > Is this restriction intentional? If possible we should get rid of it. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-11121: ----------------------------------------- Have started using this target as the foundation for the teiid-designer.target and works nicely for the project. http7://github.com/Teiid-Designer/teiid-designer/blob/master/target-platform/pom.xml Just want to give the thumbs up from our side and subject to approval, it would be good for it to be merged into master. Thanks phantomjinx > Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11121 > URL: https://issues.jboss.org/browse/JBIDE-11121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Douglas Palmer > Priority: Blocker > Labels: f2f2012 > Fix For: 4.0.0.Alpha1-SOA > > Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt > > > Generate target platforms for JBT/JBDS SOA Tooling which include: > 1. JBT Core TP + last stable JBT Core milestone. > 2. JBDS Core TP + last stable JBDS Core milestone. > Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. > This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2440) JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2440?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2440: ----------------------------------- Len do you have a list of the offending archetypes? > JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2440 > URL: https://issues.jboss.org/browse/JBDS-2440 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 6.0.1.GA > > > This problem will not be solved in a JBDS build, but it must be resolved in time for the JBDS 6.0.1 release. > The issue is that the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13328) as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8, 4, 9, 4.10, 4.11, 4.12

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13328?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13328: ------------------------------------- rep-posting from my email to keep it logged: I realize this is probably out of date, but I finally tested the new-ish wtp extension point, and it does work for something like esb. The upstream bugzilla mentioned (right before xmas) that they support .* wildcards. So, the following would work fine if placed into the esb plugin.xml: <extension point="org.eclipse.wst.server.core.runtimeModuleType"> <runtimeModuleType id="some.garbage1" runtimeTypes="org.jboss.ide.eclipse.as.runtime.60"> <moduleType types="jst.jboss.esb" versions="4.*"> </moduleType> </runtimeModuleType> </extension> You would need to modify the runtimeTypes to be a comma-separated list of which runtime types you want to support all 4.* versions of esb. Again, I tested it, and this works fine, even if astools already "supports" 4.11, 4.12. They will not conflict. If anyone wants to push this into any stream, I'd be glad to help. Just need to know what and where and when. Obviously I won't be removing anything from astools until I know 100% that everything's working in esb (or any other such runtimes). But let me know if anyone wants to move on this .* wildcard notation. > as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12 > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13328 > URL: https://issues.jboss.org/browse/JBIDE-13328 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > > The following JIRAs showcase how ass-backwards the implementation of ESB detection/support in as.core's plugin.xml is: > JBIDE-13209 > JBDS-2365 > JBDS-2394 > JBDS-1889 > JBDS-2431 > Would it be possible to have the various servers simply support 4.x instead of needing to keep updating as.core's plugin.xml every time a new version of ESB 4.x comes out? (4.11 is currently not supported properly, and 4.12 is forthcoming. Can we make this better in JBDS 7, then maybe backport that magic to JBDS 5 and 6? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13340: -------------------------------- Fix Version/s: LATER > An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13340 > URL: https://issues.jboss.org/browse/JBIDE-13340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows 7 > Eclipse Juno 64 bit > Jdk 1.7 64 bit > Reporter: andrea tomassi > Assignee: Rob Stryker > Labels: jboss > Fix For: LATER > > Attachments: Img0.png, img1.png, Img2.png > > > 1) Install JBoss Tools version 4.0 (Juno) > 2) Create a new workspace > 3) Select Java EE Eclipse perspective > 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final) > 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options) > 5) Click with right mouse button on the server, than select "Add and Remove...". > 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0) > 7) Create a Dynamic Web Project (default options) > 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1) > 9) Click again with right mouse button on the server, than select "Add and Remove...". > 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13340: ------------------------------------- This is a well-known issue with webtools. The same can be replicated with a web project inside an ear project. You can no longer deploy teh web project standalone. Unfortunately it seems to me that a lot of wtp depends on this situation. For example, when determining what url to run, it would depend on if the web project is running standalone or inside an ear (or in this case the esb is inside the war or not). The current API seems to depend on this functionality, and I think the odds of it getting changed are very very slim. A workaround is to close your web project if you want to deploy the ESB standalone. > An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13340 > URL: https://issues.jboss.org/browse/JBIDE-13340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows 7 > Eclipse Juno 64 bit > Jdk 1.7 64 bit > Reporter: andrea tomassi > Assignee: Rob Stryker > Labels: jboss > Attachments: Img0.png, img1.png, Img2.png > > > 1) Install JBoss Tools version 4.0 (Juno) > 2) Create a new workspace > 3) Select Java EE Eclipse perspective > 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final) > 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options) > 5) Click with right mouse button on the server, than select "Add and Remove...". > 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0) > 7) Create a Dynamic Web Project (default options) > 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1) > 9) Click again with right mouse button on the server, than select "Add and Remove...". > 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-2437: ----------------------------------------- Also not working with JBDS 5.0.2.CR2 (build H238) > Cannot deploy BPEL project > -------------------------- > > Key: JBDS-2437 > URL: https://issues.jboss.org/browse/JBDS-2437 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA > Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA > Reporter: Andrej Podhradsky > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 5.0.2.GA > > Attachments: deploy_error.png > > > Cannot deploy a bpel project. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2411) Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2411?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2411: ---------------------------------- Fix Version/s: 6.0.x (was: 6.0.1.GA) Not enough time to fix prior to release. Pushed to 6.0.2. > Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling > ------------------------------------------------------------------------------- > > Key: JBDS-2411 > URL: https://issues.jboss.org/browse/JBDS-2411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Martin Malina > Assignee: Isaac Rooskov > Fix For: 6.0.x > > Attachments: new-eap6.png > > > The information at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/5.0... is not up2date. When you create an AS7 server (7.0.2+) you can check if you want to expose the management port. Also, for most servers you can check if the server is to be bound to all interfaces. > Note that for a local server you don't really need to expose the management port - it is bound to localhost by default. But for remote servers you need to use it if you want to make a jmx connection to the server. > Also, if this option is checked, it will set the startup poller for that server to JBoss 7 Manager Service. For the startup poller and jmx connection to work you need to have a user created on the given remote server. > Please let me or Rob know if you need more info on 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2411) Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2411?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2411: ---------------------------------- Assignee: Michelle Murray (was: Isaac Rooskov) > Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling > ------------------------------------------------------------------------------- > > Key: JBDS-2411 > URL: https://issues.jboss.org/browse/JBDS-2411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 6.0.x > > Attachments: new-eap6.png > > > The information at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/5.0... is not up2date. When you create an AS7 server (7.0.2+) you can check if you want to expose the management port. Also, for most servers you can check if the server is to be bound to all interfaces. > Note that for a local server you don't really need to expose the management port - it is bound to localhost by default. But for remote servers you need to use it if you want to make a jmx connection to the server. > Also, if this option is checked, it will set the startup poller for that server to JBoss 7 Manager Service. For the startup poller and jmx connection to work you need to have a user created on the given remote server. > Please let me or Rob know if you need more info on 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

13 years, 2 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 January 2013