January 2013 - jbosstools-issues - Jboss List Archives

[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 andrea tomassi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] andrea tomassi updated JBIDE-13340: ----------------------------------- Attachment: img1.png Image 1 > 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

12 years, 10 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 andrea tomassi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] andrea tomassi updated JBIDE-13340: ----------------------------------- Attachment: Img2.png Image 2 > 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

12 years, 10 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 andrea tomassi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] andrea tomassi updated JBIDE-13340: ----------------------------------- Component/s: (was: JBossAS/Servers) > 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 > 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

12 years, 10 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 andrea tomassi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] andrea tomassi updated JBIDE-13340: ----------------------------------- Component/s: JBossAS/Servers > 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

12 years, 10 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 andrea tomassi (JIRA)

andrea tomassi created JBIDE-13340: -------------------------------------- Summary: 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 Attachments: Img0.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

12 years, 10 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 andrea tomassi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ] andrea tomassi updated JBIDE-13340: ----------------------------------- Attachment: Img0.png Image 0 > 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 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-2439: ------------------------------------ Assignee: Denis Golovin > jbdevstudio-unity execution fails when called from different working directory > ------------------------------------------------------------------------------ > > Key: JBDS-2439 > URL: https://issues.jboss.org/browse/JBDS-2439 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.GA > Reporter: Ondrej Skutka > Assignee: Denis Golovin > > jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir. > This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781. -- 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] (JBDS-2432) Use newer version of Eclipse with performance fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2432?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2432: ----------------------------- Fix Version/s: 6.0.1.GA (was: 6.0.x) > Use newer version of Eclipse with performance fix > ------------------------------------------------- > > Key: JBDS-2432 > URL: https://issues.jboss.org/browse/JBDS-2432 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Eclipse project released a maintenance version (that might be the future 4.2.2) for Eclipse 4.2.1 which highly improves performances. http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation -- 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] (TOOLSDOC-295) Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-295?page=com.atlassian.jira.plug... ] Mustafa Musaji commented on TOOLSDOC-295: ----------------------------------------- I'd also like to suggest that the point "NOTE" containing the section on using 'alternatives' may be better placed at the top of section 3.1.1 rather than in the middle. > Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux > --------------------------------------------------------------------------------- > > Key: TOOLSDOC-295 > URL: https://issues.jboss.org/browse/TOOLSDOC-295 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.0.0.CR1 > > > In GSG for JBDS 6 [1], section *3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux*, I see: > {quote} > You only need to run "alternative" as a safe guard for the right JVM. > {quote} > Suggest changing this to: > {quote} > You only need to run *alternatives* to select the correct default JDK. > {quote} > [1] https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > Note too that the JDK referenced is now called the Oracle JDK, not the Sun JDK. > {quote} > 3.1.1. Installing and Configuring 32-bit *Sun* JDK 6 on Linux > To install 32-bit *Sun* JDK 6 on Linux and configure it, you should follow the next steps: > Download the *Sun* JDK 6 from *Sun*'s website. > {quote} -- 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] (TOOLSDOC-295) Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux

by Nick Boldt (JIRA)

Nick Boldt created TOOLSDOC-295: ----------------------------------- Summary: Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux Key: TOOLSDOC-295 URL: https://issues.jboss.org/browse/TOOLSDOC-295 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Getting Started Guide Reporter: Nick Boldt Assignee: Michelle Murray Fix For: 4.0.0.CR1 In GSG for JBDS 6 [1], section *3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux*, I see: {quote} You only need to run "alternative" as a safe guard for the right JVM. {quote} Suggest changing this to: {quote} You only need to run *alternatives* to select the correct default JDK. {quote} [1] https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... Note too that the JDK referenced is now called the Oracle JDK, not the Sun JDK. {quote} 3.1.1. Installing and Configuring 32-bit *Sun* JDK 6 on Linux To install 32-bit *Sun* JDK 6 on Linux and configure it, you should follow the next steps: Download the *Sun* JDK 6 from *Sun*'s website. {quote} -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013