[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
11 years, 5 months
[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
11 years, 5 months
[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
11 years, 5 months
[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
11 years, 5 months
[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
11 years, 5 months
[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
11 years, 5 months
[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
11 years, 5 months
[JBoss JIRA] (JBIDE-13323) integration-tests: cannot build CDI bot tests
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13323?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič commented on JBIDE-13323:
-------------------------------------------
When using default configuration (not a custom settings.xml file) everything is going fine. There is a problem with our local repository on jawa32 machine.
> integration-tests: cannot build CDI bot tests
> ---------------------------------------------
>
> Key: JBIDE-13323
> URL: https://issues.jboss.org/browse/JBIDE-13323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: QA
> Affects Versions: 4.0.0.Final
> Environment: clean (empty) .m2 repo
> Reporter: Pavol Srna
> Assignee: Jaroslav Jankovič
> Fix For: 4.0.0.Final
>
>
> {code}
> psrna@psrna-laptop:~/data/jbosstools-integration-tests/tests$ mvn verify -Dmaven.test.skip -Dswtbot.test.skip
> [INFO] Scanning for projects...
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Adding repository http://p2-reddeer.rhcloud.com/master
> [INFO] Adding repository http://p2-reddeer.rhcloud.com/master
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving class path of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving class path of MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.seam3.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.seam3.bot.test/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.seam3.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.seam3.bot.test/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.cdi.seam3.bot.test 4.0.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.cdi.reddeer 4.0.0.qualifier requires 'bundle org.jboss.reddeer.swt 0.0.0' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.cdi.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.cdi.reddeer 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.cdi.seam3.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.cdi.bot.test 1.2.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
> at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> ... 11 more
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
> {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
11 years, 5 months