[JBoss JIRA] (FORGE-1645) JavaResource resolve to wrong path after CD
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1645?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1645.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.13.1.Final
(was: 2.x Future)
Resolution: Done
This should be fixed by FORGE-2170. Reopen if the problem persists
> JavaResource resolve to wrong path after CD
> -------------------------------------------
>
> Key: FORGE-1645
> URL: https://issues.jboss.org/browse/FORGE-1645
> Project: Forge
> Issue Type: Bug
> Components: Parsers / File Manipulation
> Affects Versions: 2.1.1.Final
> Environment: Linux Fedora 20, JDK 1.7
> Reporter: Aslak Knutsen
> Assignee: George Gastaldi
> Fix For: 2.13.1.Final
>
>
> With the following code
> {code}
> @Inject
> @WithAttributes(shortName = 's', label = "source", required = true, type = InputType.JAVA_CLASS_PICKER)
> private UIInput<JavaResource> source;
> {code}
> Assume the following directory structure:
> x/y/src/main/java/x.java
> * Start forge in folder X.
> * cd to some sub folder Y
> * trigger the 'source' field
> ** command --source src/main/java/x.java
> The JavaResource fail to resolve the underlying file as it's pointing to:
> X/src/main/java/x.java
> It seems it's missing the updated 'current dir' and only resolve from 'original working dir'
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2170) Forge addon-build-and-install doesn't work with wildcards "." "~"
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2170?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2170.
----------------------------------
Fixed, please reopen if issue persists
> Forge addon-build-and-install doesn't work with wildcards "." "~"
> ------------------------------------------------------------------
>
> Key: FORGE-2170
> URL: https://issues.jboss.org/browse/FORGE-2170
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.13.0.Final
> Reporter: Daniel Cunha (soro)
> Assignee: George Gastaldi
> Fix For: 2.13.1.Final
>
>
> [addon-arquillian]$ pwd
> /home/soro/Tools/workspace/addon-arquillian
> [addon-arquillian]$ addon-build-and-install --projectRoot .
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$ addon-build-and-install --projectRoot ~/Tools/workspace/addon-arquillian
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2170) Forge addon-build-and-install doesn't work with wildcards "." "~"
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2170?page=com.atlassian.jira.plugin... ]
George Gastaldi resolved FORGE-2170.
------------------------------------
Assignee: George Gastaldi (was: Daniel Cunha (soro))
Fix Version/s: 2.13.1.Final
Resolution: Done
> Forge addon-build-and-install doesn't work with wildcards "." "~"
> ------------------------------------------------------------------
>
> Key: FORGE-2170
> URL: https://issues.jboss.org/browse/FORGE-2170
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.13.0.Final
> Reporter: Daniel Cunha (soro)
> Assignee: George Gastaldi
> Fix For: 2.13.1.Final
>
>
> [addon-arquillian]$ pwd
> /home/soro/Tools/workspace/addon-arquillian
> [addon-arquillian]$ addon-build-and-install --projectRoot .
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$ addon-build-and-install --projectRoot ~/Tools/workspace/addon-arquillian
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2170) Forge addon-build-and-install doesn't work with wildcards "." "~"
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2170?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2170:
-----------------------------------
Affects Version/s: 2.13.0.Final
(was: 2.13.1.Final)
> Forge addon-build-and-install doesn't work with wildcards "." "~"
> ------------------------------------------------------------------
>
> Key: FORGE-2170
> URL: https://issues.jboss.org/browse/FORGE-2170
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.13.0.Final
> Reporter: Daniel Cunha (soro)
> Assignee: George Gastaldi
> Fix For: 2.13.1.Final
>
>
> [addon-arquillian]$ pwd
> /home/soro/Tools/workspace/addon-arquillian
> [addon-arquillian]$ addon-build-and-install --projectRoot .
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$ addon-build-and-install --projectRoot ~/Tools/workspace/addon-arquillian
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2170) Forge addon-build-and-install doesn't work with wildcards "." "~"
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-2170?page=com.atlassian.jira.plugin... ]
Daniel Cunha commented on FORGE-2170:
-------------------------------------
My initial change:
https://github.com/danielsoro/core/commit/49be9df7d06dec55f525c133cca324e...
But I have a problem here:
The second parameter of the constructor is the current dir and I passed null because I don't have the current dir.
In ResourcePathResolver I need to pass the current dir and I don't have the context to get the current dir. For fix the "." wildcard I need the context to fix it.
I know that this issue should be fixed in aesh. Aesh should resolve the inputs and pass the complete path to Forge. IMO.
For now, we're working in aesh, but forge can fix it for now with this Resolver. :)
The next update of the aesh we'll have fixed. Working in progress.
> Forge addon-build-and-install doesn't work with wildcards "." "~"
> ------------------------------------------------------------------
>
> Key: FORGE-2170
> URL: https://issues.jboss.org/browse/FORGE-2170
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.13.1.Final
> Reporter: Daniel Cunha
> Assignee: Daniel Cunha
>
> [addon-arquillian]$ pwd
> /home/soro/Tools/workspace/addon-arquillian
> [addon-arquillian]$ addon-build-and-install --projectRoot .
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$ addon-build-and-install --projectRoot ~/Tools/workspace/addon-arquillian
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-1828) Installing the same Addon twice cause ClassCastException in Eclipse
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-1828?page=com.atlassian.jira.plugin... ]
Daniel Cunha commented on FORGE-1828:
-------------------------------------
I catch same problem.
But the log doesn't show stacktrace.
Forge show only this msg:
Exception when parsing/running: arquillian-setup, org.jboss.forge.arquillian.container.index.ContainerDirectoryParser cannot be cast to org.jboss.forge.arquillian.container.index.ContainerDirectoryParser
> Installing the same Addon twice cause ClassCastException in Eclipse
> -------------------------------------------------------------------
>
> Key: FORGE-1828
> URL: https://issues.jboss.org/browse/FORGE-1828
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Reporter: Aslak Knutsen
> Fix For: 2.x Future
>
>
> Steps:
> * addon-build-and-install
> * execute plugin
> * addon-build-and-install
> * execute plugin
> ** Might fail on ClassCastException due to two different ClassLoaders operating on the same Class.
> java.lang.ClassCastException:
> org.jboss.forge.arquillian.container.index.ContainerDirectoryParser
> cannot be cast to
> org.jboss.forge.arquillian.container.index.ContainerDirectoryParser
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2170) Forge addon-build-and-install doesn't work with wildcards "." "~"
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-2170?page=com.atlassian.jira.plugin... ]
Daniel Cunha reassigned FORGE-2170:
-----------------------------------
Assignee: Daniel Cunha
> Forge addon-build-and-install doesn't work with wildcards "." "~"
> ------------------------------------------------------------------
>
> Key: FORGE-2170
> URL: https://issues.jboss.org/browse/FORGE-2170
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.13.1.Final
> Reporter: Daniel Cunha
> Assignee: Daniel Cunha
>
> [addon-arquillian]$ pwd
> /home/soro/Tools/workspace/addon-arquillian
> [addon-arquillian]$ addon-build-and-install --projectRoot .
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$ addon-build-and-install --projectRoot ~/Tools/workspace/addon-arquillian
> ***ERROR*** No project found in root /home/soro/.m2/repository/org/jboss/forge/forge-distribution/2.13.1-SNAPSHOT/.
> [addon-arquillian]$
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months