January 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2585) Allow to obtain the cursor position of the current active editor window

by Claus Ibsen (JIRA)

Claus Ibsen created FORGE-2585: ---------------------------------- Summary: Allow to obtain the cursor position of the current active editor window Key: FORGE-2585 URL: https://issues.jboss.org/browse/FORGE-2585 Project: Forge Issue Type: Feature Request Affects Versions: 3.0.0.Beta3 Reporter: Claus Ibsen For background see: https://github.com/fabric8io/fabric8/issues/5625 It would be great if a forge command can obtain information about what is the current active window and the cursor position. Essentially what we would like to know is that if the end user is currently editing a file, such as java or xml, and if so, what is the current cursor position in that file, or line number / column number etc. Then the commands can use that to react accordingly. For example in fabric8 we want to be able to find out if the cursor is positioned in a Camel route and then let the command be smart to use that route etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2584) Build command always skip tests and fails if a profile is set

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2584?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2584: ----------------------------------- Affects Version/s: 3.0.0.Beta3 > Build command always skip tests and fails if a profile is set > ------------------------------------------------------------- > > Key: FORGE-2584 > URL: https://issues.jboss.org/browse/FORGE-2584 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 3.0.0.Beta3 > Reporter: George Gastaldi > Fix For: 3.x Future > > > {{build --profile arquillian-wildfly-remote}} gives the following exception: > {code} > [SEVERE] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] > {code} > {{build install --profile arquillian-wildfly-remote}} always skip tests even if {{--notest=false}} is specified -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2584) Build command always skip tests and fails if a profile is set

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2584: -------------------------------------- Summary: Build command always skip tests and fails if a profile is set Key: FORGE-2584 URL: https://issues.jboss.org/browse/FORGE-2584 Project: Forge Issue Type: Bug Components: Build Tools - Maven Reporter: George Gastaldi Fix For: 3.x Future {{build --profile arquillian-wildfly-remote}} gives the following exception: {code} [SEVERE] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] {code} {{build install --profile arquillian-wildfly-remote}} always skip tests even if {{--notest=false}} is specified -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/forge/roaster/pull/52 (was: https://github.com/forge/roaster/pull/50) Okay, normally this PR is correct ! Pls confirm it to me ='( ='( > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Open (was: Pull Request Sent) > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Work on ROASTER-91 started by Nicolas Challut. ---------------------------------------------- > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] Work on ROASTER-92 started by Nicolas Challut. ---------------------------------------------- > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-92: ----------------------------------- Status: Open (was: Pull Request Sent) > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-92: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/forge/roaster/pull/51 > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2583) Upgrade JGit to 4.1.1.201511131810-r

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2583?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2583. ---------------------------------- Resolution: Done > Upgrade JGit to 4.1.1.201511131810-r > ------------------------------------ > > Key: FORGE-2583 > URL: https://issues.jboss.org/browse/FORGE-2583 > Project: Forge > Issue Type: Component Upgrade > Components: Git > Affects Versions: 3.0.0.Beta3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2016