[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-20795.
------------------------------------
Resolution: Done
> canonical form is required(project=arquillian-test)
> ---------------------------------------------------
>
> Key: JBIDE-20795
> URL: https://issues.jboss.org/browse/JBIDE-20795
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: arquillian
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.3.1.Beta1
>
>
> This code:
> {code}
> @RunWith(Arquillian.class)
> public class SimpleTestCase {
> @Deployment
> public static WebArchive test() {
> return ShrinkWrap.create(WebArchive.class)
> .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile());
> }
>
> @Test
> public void shouldX() {}
> }
> {code}
> produce the following warning:
> {code}
> null
> org.jboss.tools.arquillian.core
> Warning
> Wed Sep 23 23:16:17 CEST 2015
> canonical form is required(project=arquillian-test)
> {code}
> On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from.
> With a little digging it's due to the resolve("") failing since the String input is not in the correct format.
> The warning is marked on the Method line, not on the line where the Resolver is called.
> Would it be possible to re position this somehow? At least get a stack trace or something in the warning?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-20795:
---------------------------------------
The message is coming from the arquillian core component. If you think that has to be changed, please, create a bug against the arquillian core.
> canonical form is required(project=arquillian-test)
> ---------------------------------------------------
>
> Key: JBIDE-20795
> URL: https://issues.jboss.org/browse/JBIDE-20795
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: arquillian
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.3.1.Beta1
>
>
> This code:
> {code}
> @RunWith(Arquillian.class)
> public class SimpleTestCase {
> @Deployment
> public static WebArchive test() {
> return ShrinkWrap.create(WebArchive.class)
> .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile());
> }
>
> @Test
> public void shouldX() {}
> }
> {code}
> produce the following warning:
> {code}
> null
> org.jboss.tools.arquillian.core
> Warning
> Wed Sep 23 23:16:17 CEST 2015
> canonical form is required(project=arquillian-test)
> {code}
> On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from.
> With a little digging it's due to the resolve("") failing since the String input is not in the correct format.
> The warning is marked on the Method line, not on the line where the Resolver is called.
> Would it be possible to re position this somehow? At least get a stack trace or something in the warning?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21080) Import Application... context menu item is available for any tree item under an OpenShift 3 connection
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21080:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Import Application... context menu item is available for any tree item under an OpenShift 3 connection
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21080) Import Application... context menu item is available for any tree item under an OpenShift 3 connection
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21080:
--------------------------------
Fix Version/s: 4.3.1.Beta1
> Import Application... context menu item is available for any tree item under an OpenShift 3 connection
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months