[JBoss JIRA] (JBIDE-14842) Include optional dependencies in pom.xml at surefire level
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14842?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-14842:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Include optional dependencies in pom.xml at surefire level
> ----------------------------------------------------------
>
> Key: JBIDE-14842
> URL: https://issues.jboss.org/browse/JBIDE-14842
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs, jax-ws
> Fix For: 4.6.x
>
>
> running tests during a tycho build on MacOSX requires an optional/platform specific bundle (o.e.jdt.launching.macosx) that is currently defined in a profile.
> Problem is that this profile includes *all* optional dependencies, not only this one, while other profiles (ie, platform) include no optional dependency at all.
> Solution: configure this optional dependency at the surefire level and for macosx only
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22035) Server adapter: Stopping of J2EE module does not work
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22035:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Server adapter: Stopping of J2EE module does not work
> -----------------------------------------------------
>
> Key: JBIDE-22035
> URL: https://issues.jboss.org/browse/JBIDE-22035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
>
> Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following
> {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec
> total size is 8,523,390 speedup is 6,180.85
> sending incremental file list
> ROOT.war.isdeploying
> sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec
> total size is 8,523,390 speedup is 5,404.81{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24141:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
> ------------------------------------------------------------
>
> Key: JBIDE-24141
> URL: https://issues.jboss.org/browse/JBIDE-24141
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.4.AM2, 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.6.x
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:*
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2
> {code}
> {code}
> Failed
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> Failing for the past 2 builds (Since Unstable#74 )
> Took 0.15 sec.
> add description
> Error Message
> Expected: <6>
> but: was <10>
> Stacktrace
> java.lang.AssertionError:
> Expected: <6>
> but: was <10>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-13578) Provide quickfixes to existing JAX-RS Application
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13578?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13578:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Provide quickfixes to existing JAX-RS Application
> -------------------------------------------------
>
> Key: JBIDE-13578
> URL: https://issues.jboss.org/browse/JBIDE-13578
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.6.x
>
>
> A quickfix to annotate the JAX-RS Application with javax.ws.rs.ApplicationPath should be provided if an error is detected.
> ----
> From JAX-RS 1.1 spec, chap 2.3.2:
> When using the pluggability mechanism the following conditions MUST be met:
> • If no Application subclass is present the added servlet MUST be named: javax.ws.rs.core.Application
> and all root resource classes and providers packaged in the web application MUST be included in the published JAX-RS application. The application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet.
> • If an Application subclass is present and there is already a servlet defined that has a servlet initial- ization parameter named:
> javax.ws.rs.Application
> whose value is the fully qualified name of the Application subclass then no new servlet should be added by the JAX-RS implementation’s ContainerInitializer since the application is already being handled by an existing servlet.
> • If an Application subclass is present that is not being handled by an existing servlet then the servlet added by the ContainerInitializer MUST be named with the fully qualified name of the Application subclass. If the Application subclass is annotated with @ApplicationPath and no servlet-mapping exists for the added servlet then a new servlet mapping is added with the value of the @ApplicationPath annotation with ”/*” appended otherwise the existing mapping is used. If the Application subclass is not annotated with @ApplicationPath then the application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet. It is an error for more than one application to be deployed at the same effective servlet mapping
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20346:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Fix For: 4.6.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-16512) Some dialogs (and wizards) are not draggable (since they do not have a title bar)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16512?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-16512:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Some dialogs (and wizards) are not draggable (since they do not have a title bar)
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-16512
> URL: https://issues.jboss.org/browse/JBIDE-16512
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.6.x
>
>
> On Fedora with GNOME many shells (wizards) do not have Title bar and that's the reason they are not dragable / moveable. Before 4.2.0 there was not almost any of the title bars, but with 4.2.0 there is seen improvement.
> Specifically these shells do not have title bar:
> - Port forwarding (shell opened from application context menu)
> - Edit enviroment variables (shell opened from application context menu)
> - Import application (wizard opened from application context menu)
> - New connection (shell opened from OpenShift explorer view context menu or by click on tool bar button Connect to Openshift)
> - Edit connection (shell opened from context menu of connection)
> - New domain (shell opened from context menu of connection)
> - Edit domain (shell opened from context menu of domain)
> - Manage domains (shell opened from context menu of connection)
> - New application (wizard open from context menu of connection / domain or File - New - OpenShift Application
> Few examples of correct shells:
> - Tail Files (shell opened from application context menu)
> - Details (shell opened from application context menu)
> - Create server adapted (shell opened from application context menu)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20051) As a I user I want to be able to automatically install webhooks into my GitHub repository
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20051?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20051:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> As a I user I want to be able to automatically install webhooks into my GitHub repository
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20051
> URL: https://issues.jboss.org/browse/JBIDE-20051
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: new_and_noteworthy, openshift_v3
> Fix For: 4.6.x
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> I want to be able to automatically install webhooks into my github repository from Eclipse.
> We can detect if a project has a github url.
> We can probably detect the user github credentials, or ask the user his credentials before trying to install the webhook.
> There must be a GitHub API that allows to then add webhooks automatically.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months