[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3286:
-----------------------------
CDW devel_ack: ? (was: +)
CDW release: ? (was: +)
> Remove Seam tooling from default JBDS installation
> --------------------------------------------------
>
> Key: JBDS-3286
> URL: https://issues.jboss.org/browse/JBDS-3286
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already).
> [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3297:
-------------------------------
Component/s: requirements
> Download/Import Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3297
> URL: https://issues.jboss.org/browse/JBDS-3297
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Blocker
>
> Use Case #1 - Download/Import Existing OpenShift Project
> a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects)
> b) Assume end-user is logged in (ignore auth for now)
> c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services.
> d) Eclipse user will open a dialog and enter the URL from step a
> e) Eclipse user will see a list of "things" associated with "projects" from step 1c
> "things"
> f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f]
> g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets
> h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files
> i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com)
> j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container:
> docker run -it -p 8080:8080 openshift/wildfly-8-centos
> [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3291:
-------------------------------
Component/s: requirements
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3291
> URL: https://issues.jboss.org/browse/JBDS-3291
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, requirements, server
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3298:
-------------------------------
Component/s: requirements
> Push changes to Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3298
> URL: https://issues.jboss.org/browse/JBDS-3298
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Blocker
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian)
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note:
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3306:
-------------------------------
Component/s: requirements
> Create Deployment from Template
> -------------------------------
>
> Key: JBDS-3306
> URL: https://issues.jboss.org/browse/JBDS-3306
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Priority: Blocker
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api)
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18847) Extract discovery code out of project examples
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18847?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-18847 at 1/15/15 10:52 AM:
--------------------------------------------------------------
New plugin(s) need to be added to JBT and JBDS aggregates. Reopening.
1. add plugin to JBT/JBDS agg sites
2. remove new features (discovery + discovery.test)
(this includes both discovery.core and org.jboss.tools.project.examples.seam, plus any other new plugins)
was (Author: nickboldt):
New plugin(s) need to be added to JBT and JBDS aggregates. Reopening.
> Extract discovery code out of project examples
> ----------------------------------------------
>
> Key: JBIDE-18847
> URL: https://issues.jboss.org/browse/JBIDE-18847
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
>
> Discovery code used by central (to install software) and project-examples (to discover proxy-wizards) lives in project examples. Because of that dependency, project examples also contain API that configures central content. That forces com.jboss.devstudio.core.central to depend on project examples, just to configure central contents.
> This sucks big time and that common discovery code should be extracted to another component, consumed by both central and examples. The central configuration API should move back to central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"
by Stylianos Koussouris (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ]
Stylianos Koussouris updated JBIDE-19042:
-----------------------------------------
Description:
Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive
Unknown error, can not verify user
and in the log
!ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848
!MESSAGE
!STACK 0
java.lang.NullPointerException
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113)
at com.openshift.internal.client.RestService.request(RestService.java:151)
at com.openshift.internal.client.RestService.request(RestService.java:107)
at com.openshift.internal.client.RestService.request(RestService.java:100)
at com.openshift.internal.client.RestService.request(RestService.java:81)
at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252)
at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user
was:
Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive
Unknown error, can not verify user
and in the log
!ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848
!MESSAGE
!STACK 0
java.lang.NullPointerException
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113)
at com.openshift.internal.client.RestService.request(RestService.java:151)
at com.openshift.internal.client.RestService.request(RestService.java:107)
at com.openshift.internal.client.RestService.request(RestService.java:100)
at com.openshift.internal.client.RestService.request(RestService.java:81)
at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252)
at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Cannot login via Openshift Explorer on Openshift "Can not verify User"
> ----------------------------------------------------------------------
>
> Key: JBIDE-19042
> URL: https://issues.jboss.org/browse/JBIDE-19042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.x, 4.2.x
> Environment: Win7, jdk7, Openshift Online
> Reporter: Stylianos Koussouris
> Priority: Critical
> Attachments: CannotVerifyUser.JPG
>
>
> Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive
> Unknown error, can not verify user
> and in the log
> !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113)
> at com.openshift.internal.client.RestService.request(RestService.java:151)
> at com.openshift.internal.client.RestService.request(RestService.java:107)
> at com.openshift.internal.client.RestService.request(RestService.java:100)
> at com.openshift.internal.client.RestService.request(RestService.java:81)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
> at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252)
> at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19043) Error publishing jar inside utility project inside ear project
by Martin Malina (JIRA)
Martin Malina created JBIDE-19043:
-------------------------------------
Summary: Error publishing jar inside utility project inside ear project
Key: JBIDE-19043
URL: https://issues.jboss.org/browse/JBIDE-19043
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.2.Final
Reporter: Martin Malina
Assignee: Rob Stryker
While verifying JBIDE-18862 I wanted to have some really big file to deploy so that I could see is an existing *.dodeploy marker is removed before the copying begins.
So I created an ear project with a nested dynamic web project and utility project. Inside this utility project's src dir I copied JBDS installer jar. Then I tried to deploy the ear to a WildFly 8.2 server (both stopped and running).
It seemed to work, the utility jar had 574 MB. But the tooling showed me this error:
Publishing to wildfly has encountered a problem:
{code}
Error renaming /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/tmp/tmp582268190747176162.jar to /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
You may adjust these settings in the server editor.
{code}
It's true that this was on a different FS, but both the tmp and deploy dirs were one FS, so that should be fine.
And just to be sure, I tried the same on the same FS and the error was the same:
{code}
Error renaming /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/tmp/tmp7876542570838575938.jar to /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
You may adjust these settings in the server editor.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18862:
---------------------------------------
[~rob.stryker], I think it does not work 100 %. The markers are mostly removed after undeploying, that's fine.
But the case where the *.dodeploy is already present is not ok - the tooling should remove it first before copying the content over, but it doesn't.
So when you deploy an ear module to wildfly, the content is being copied while the *.dodeploy flag is there.
That's not a problem with a stopped server, but if the server is running, this will result in unexpected behavior:
This will be in the log:
{code}
16:33:07,134 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of "earproj.ear" (runtime-name: "earproj.ear")
16:33:07,157 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015973: Starting subdeployment (runtime-name: "dynproj.war")
16:33:08,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: /dynproj
16:33:08,053 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "earproj.ear" (runtime-name : "earproj.ear")
{code}
So it seems it's already deployed. But in fact the file are still being copied and eclipse status bar at the bottom right is showing the progress.
So really you should always check if the marker is there and if so, remove it.
Also, I had issues deploying my big module, but that's for another JIRA - JBIDE-19043
Also, when I remove a deployed ear module from a running server, I will end up with the .undeployed marker. I thought we concluded that this should be removed as well, right?
> when removing a module from AS runtime marker files are not removed automatically
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18862
> URL: https://issues.jboss.org/browse/JBIDE-18862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Windiws7 64bit, JDK 8u25
> Reporter: Darryl Miles
> Assignee: Rob Stryker
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> module removal does not delete the various marker files relating to it:
> *.undeployed
> *.dodeploy
> The same should be true when ADDING a module, it should clean out any marker files.
> Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written.
> Write out the*.ear file.
> Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"
by Stylianos Koussouris (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ]
Stylianos Koussouris updated JBIDE-19042:
-----------------------------------------
Attachment: CannotVerifyUser.JPG
> Cannot login via Openshift Explorer on Openshift "Can not verify User"
> ----------------------------------------------------------------------
>
> Key: JBIDE-19042
> URL: https://issues.jboss.org/browse/JBIDE-19042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.x, 4.2.x
> Environment: Win7, jdk7, Openshift Online
> Reporter: Stylianos Koussouris
> Priority: Critical
> Attachments: CannotVerifyUser.JPG
>
>
> Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive
> Unknown error, can not verify user
> and in the log
> !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113)
> at com.openshift.internal.client.RestService.request(RestService.java:151)
> at com.openshift.internal.client.RestService.request(RestService.java:107)
> at com.openshift.internal.client.RestService.request(RestService.java:100)
> at com.openshift.internal.client.RestService.request(RestService.java:81)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
> at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252)
> at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months