[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18274:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-18377) Automatically add the dependencies specified in jboss-deployment-structure.xml to build path
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18377?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18377:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Automatically add the dependencies specified in jboss-deployment-structure.xml to build path
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18377
> URL: https://issues.jboss.org/browse/JBIDE-18377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Gary Hu
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> I am deploying a dynamic web project to EAP 6 using JBDS 6+. My project's build path includes the JRE System Library, EAP 6 Runtime, and Web App Libraries (the WEB-INF/lib folder). I also have a jboss-deployment-structure.xml file that defines additional module dependencies such as the following:
> <jboss-deployment-structure>
> <deployment>
> <dependencies>
> <module name="org.slf4j" />
> <module name="org.apache.log4j" />
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
> The problem is, the slf4j and log4j modules are not included in the project's build path. While the server resolves them correctly at runtime because of the jboss-deployment-structure.xml file, Eclipse doesn't include them. So the following declaration in the Java code would result in a build error because org.apache.log4j cannot be resolved to a type:
> private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(Example.class);
> Please note that the project has configured correctly the JBoss Server Runtime which points to a valid JBoss directory, and the module dependencies are properly installed in the server.
> The dependencies specified in the jboss-deployment-structure.xml are some private modules installed at the server side but not included in the server runtime by default.
> So, is there a way to automatically add the jboss-deployment-structure module dependencies to the Eclipse build path? So far, I've been unable to find a way to do this.
> I have found a few workarounds, but none of them are ideal, and they seem to completely miss the point of module-based dependencies:
> - Customize the Default Classpath Entries for the server runtime. This is not acceptable because it must be done in each developer's workspace – and possibly per project since projects may have different, conflicting dependencies.
> - Add the libraries to WEB-INF/lib. This is not acceptable because it defeats the purpose of server modules.
> - Add the libraries to a user library for the project. This could work, but it's very inconvenient, because each developer on the team would have to add the jars to the user libraries in their workspaces.
> Here can find the discussion of exact same issue https://developer.jboss.org/thread/203309?tstart=0
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19629) Unable to create connections from nightly build when installing v3 plugins only
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19629?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19629:
-------------------------------------
Issue Type: Bug (was: Feature Request)
Fix Version/s: 4.3.0.Alpha2
Description:
# ASSERT make sure that you have only openshift v3 plugins installed
# ASSERT: make sure that you have a openshift v3 server reachable for Eclipse
# EXEC: in Explorer: launch conection wizard
Result:
The connection wizard wont open. In the Eclipse log you'll find the following stacktrace:
{code}
!ENTRY org.eclipse.ui 4 0 2015-04-16 12:37:21.636
!MESSAGE Unhandled event loop exception
!STACK 0
com.openshift.restclient.OpenShiftException: Malformed URL %s
at com.openshift.restclient.ClientFactory.create(ClientFactory.java:39)
at org.jboss.tools.openshift.core.connection.Connection.<init>(Connection.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:45)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.initNewConnection(ConnectionWizardPageModel.java:113)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.init(ConnectionWizardPageModel.java:95)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.<init>(ConnectionWizardPageModel.java:68)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.<init>(ConnectionWizardPage.java:97)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:39)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:32)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:28)
at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:132)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
{code}
was:
!ENTRY org.eclipse.ui 4 0 2015-04-16 12:37:21.636
!MESSAGE Unhandled event loop exception
!STACK 0
com.openshift.restclient.OpenShiftException: Malformed URL %s
at com.openshift.restclient.ClientFactory.create(ClientFactory.java:39)
at org.jboss.tools.openshift.core.connection.Connection.<init>(Connection.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:45)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.initNewConnection(ConnectionWizardPageModel.java:113)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.init(ConnectionWizardPageModel.java:95)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.<init>(ConnectionWizardPageModel.java:68)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.<init>(ConnectionWizardPage.java:97)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:39)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:32)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:28)
at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:132)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> Unable to create connections from nightly build when installing v3 plugins only
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19629
> URL: https://issues.jboss.org/browse/JBIDE-19629
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> # ASSERT make sure that you have only openshift v3 plugins installed
> # ASSERT: make sure that you have a openshift v3 server reachable for Eclipse
> # EXEC: in Explorer: launch conection wizard
> Result:
> The connection wizard wont open. In the Eclipse log you'll find the following stacktrace:
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-04-16 12:37:21.636
> !MESSAGE Unhandled event loop exception
> !STACK 0
> com.openshift.restclient.OpenShiftException: Malformed URL %s
> at com.openshift.restclient.ClientFactory.create(ClientFactory.java:39)
> at org.jboss.tools.openshift.core.connection.Connection.<init>(Connection.java:50)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:50)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:45)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.initNewConnection(ConnectionWizardPageModel.java:113)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.init(ConnectionWizardPageModel.java:95)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.<init>(ConnectionWizardPageModel.java:68)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.<init>(ConnectionWizardPage.java:97)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:39)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:32)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:28)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:132)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19614) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19614?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-19614.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Hibernate]
> --------------------------------------------------------
>
> Key: JBIDE-19614
> URL: https://issues.jboss.org/browse/JBIDE-19614
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Hibernate]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19629) Unable to create connections from nightly build when installing v3 plugins only
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19629:
-------------------------------------
Summary: Unable to create connections from nightly build when installing v3 plugins only
Key: JBIDE-19629
URL: https://issues.jboss.org/browse/JBIDE-19629
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Priority: Blocker
!ENTRY org.eclipse.ui 4 0 2015-04-16 12:37:21.636
!MESSAGE Unhandled event loop exception
!STACK 0
com.openshift.restclient.OpenShiftException: Malformed URL %s
at com.openshift.restclient.ClientFactory.create(ClientFactory.java:39)
at org.jboss.tools.openshift.core.connection.Connection.<init>(Connection.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:50)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:45)
at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.initNewConnection(ConnectionWizardPageModel.java:113)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.init(ConnectionWizardPageModel.java:95)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.<init>(ConnectionWizardPageModel.java:68)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.<init>(ConnectionWizardPage.java:97)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:39)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:32)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.<init>(ConnectionWizard.java:28)
at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:132)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19608) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19608?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19608:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch
> --------------------------------------------
>
> Key: JBIDE-19608
> URL: https://issues.jboss.org/browse/JBIDE-19608
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3412
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19619) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19619?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-19619.
-----------------------------
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Forge]
> ----------------------------------------------------
>
> Key: JBIDE-19619
> URL: https://issues.jboss.org/browse/JBIDE-19619
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Forge]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months