[JBoss JIRA] (JBIDE-20703) Projects using CXF services/clients created through the wizard won't deploy to JBoss servers
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20703?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-20703:
-------------------------------------
Assignee: Brian Fitzpatrick
> Projects using CXF services/clients created through the wizard won't deploy to JBoss servers
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20703
> URL: https://issues.jboss.org/browse/JBIDE-20703
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.CR1
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Labels: jax-ws
> Fix For: 4.3.x
>
>
> Creating a service/client that uses CXF as its runtime will cause Eclipse to add CXF jars as a library to the project, which in turn will make it undeployable to JBoss servers.
> I'm not sure if this is more of a bug or a feature, but it would be more user friendly to have those projects deployable straight away without the user having to change the project configuration, particularly when the server selected in the wizards is a JBoss one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-20915:
-------------------------------------
Assignee: Misha Ali (was: Xavier Coulon)
Assigning to you, [~mhusnain], for the purpose of documenting the "delay" option.
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Misha Ali
> Priority: Critical
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3566:
-------------------------------------------
Yes, "not relevant" is similar to "no" but will become a "yes" down the road.
And no, we won't use AERI's current form of discovery since it excludes the eclipse.org from getting reports. AERI are adding an extension point to allow us to *add* reporters instead of defining a singular one.
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21455) The "GitHub" link is unavailable in the "Webhooks triggers" window
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21455?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21455.
-----------------------------------
Fix Version/s: 4.3.1.Beta2
Resolution: Rejected
This is not a bug. You get 404 because you cannot access the page if you are not logged in. If you would use your own git repo with quickstarts and linked it with your application, you would be able to get to this page once you click on the link if you are logged in with the specific user.
> The "GitHub" link is unavailable in the "Webhooks triggers" window
> ------------------------------------------------------------------
>
> Key: JBIDE-21455
> URL: https://issues.jboss.org/browse/JBIDE-21455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> Reporter: Chunyun Chen
> Labels: openshift_v3
> Fix For: 4.3.1.Beta2
>
>
> The "GitHub" link is unavailable in the "Webhooks triggers" window
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21454) Importing eap64 template project fails due to error in egitutils
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21454:
-----------------------------------
Summary: Importing eap64 template project fails due to error in egitutils
Key: JBIDE-21454
URL: https://issues.jboss.org/browse/JBIDE-21454
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Rob Stryker
Attempting to import todolist template project results in trying to connect the git team manager to the project and failing. This is because it is looking for /home/rob/Downloads/cdk/openshift_apps/jee9/openshift-quickstarts/todolist/todolist-jdbc/.git which doesn't exist. This is a nested project in a much larger repository.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months