[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2315:
----------------------------------------
Right, then I believe it's ok to have a move method. +1
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) commented on FORGE-2315:
--------------------------------------------
So, what do you think better?
Create a move or change the renameTo?
For me:
create move +1
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) commented on FORGE-2315:
--------------------------------------------
[~gastaldi] Yes,
but for totally support for 'mv', renameTo need improvement.
with renameTo, my mv not work this form:
{code}
mv file path/
{code}
I need to do:
{code}
mv file path/new-name
{code}
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2315:
----------------------------------------
Actually we do have {{FileResource.renameTo}}, so I guess that should be used instead
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
Work on FORGE-2315 started by Daniel Cunha (soro).
--------------------------------------------------
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FORGE-2315?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) reassigned FORGE-2315:
------------------------------------------
Assignee: Daniel Cunha (soro)
> Add move for FileResources
> --------------------------
>
> Key: FORGE-2315
> URL: https://issues.jboss.org/browse/FORGE-2315
> Project: Forge
> Issue Type: Feature Request
> Components: Resources
> Reporter: Daniel Cunha (soro)
> Assignee: Daniel Cunha (soro)
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Daniel Cunha (soro) created FORGE-2315:
------------------------------------------
Summary: Add move for FileResources
Key: FORGE-2315
URL: https://issues.jboss.org/browse/FORGE-2315
Project: Forge
Issue Type: Feature Request
Components: Resources
Reporter: Daniel Cunha (soro)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/FURNACE-45?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FURNACE-45:
----------------------------------------
Shouldn´t this managed settings.xml be resolved as the Settings to the execution of the mojo? Afaik it is set in the MOJO as in https://github.com/forge/furnace/blob/master/maven-plugin/src/main/java/o...
> furnace maven plugin doens't use the maven settings and mirror and refuses to use the addon that have already been downloaded
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: FURNACE-45
> URL: https://issues.jboss.org/browse/FURNACE-45
> Project: Forge: Furnace
> Issue Type: Feature Request
> Reporter: James Strachan
>
> we've been using the furnace maven plugin for a while. We're trying to use a 'canary' style CD system where we build a bunch of projects internally on a nexus; test everything; then promote. However our Forge project is barfing now as its failing to download the camel forge addons which have been build and deployed to nexus.
> here's the trimmed output of the build
> {code}
> 13:57:26 [INFO] Downloading: http://nexus/content/groups/public/io/fabric8/forge/fabric8-forge-web/2.2...
> 13:57:26 [INFO] Downloading: http://nexus/content/groups/public/io/fabric8/forge/camel/2.2.0-3/camel-2...
> 13:57:26 [INFO] Downloading: http://nexus/content/groups/public/io/fabric8/forge/utils/2.2.0-3/utils-2...
> ...
> 13:57:28 [INFO] Downloaded: http://nexus/content/groups/public/org/jboss/forge/addon/projects-api/2.1... (27 KB at 10.8 KB/sec)
> 13:57:28 [INFO]
> 13:57:28 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ fabric8-forge ---
> 13:57:28 [INFO]
> 13:57:28 [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven) @ fabric8-forge ---
> 13:57:28 [INFO]
> 13:57:28 [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-versions) @ fabric8-forge ---
> 13:57:28 [INFO]
> 13:57:28 [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ fabric8-forge ---
> 13:57:28 [INFO] Using 'UTF-8' encoding to copy filtered resources.
> 13:57:28 [INFO] Copying 1 resource
> 13:57:28 [INFO]
> 13:57:28 [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ fabric8-forge ---
> 13:57:28 [INFO] No sources to compile
> 13:57:29 [INFO]
> 13:57:29 [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ fabric8-forge ---
> 13:57:29 [INFO] Using 'UTF-8' encoding to copy filtered resources.
> 13:57:29 [INFO] skip non existing resourceDirectory /var/jenkins_home/workspace/quickstarts/apps/fabric8-forge/src/test/resources
> 13:57:29 [INFO]
> 13:57:29 [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ fabric8-forge ---
> 13:57:29 [INFO] No sources to compile
> 13:57:29 [INFO]
> 13:57:29 [INFO] --- furnace-maven-plugin:2.17.0.Final:addon-install (deploy-addons) @ fabric8-forge ---
> 13:57:29 [INFO] Downloading: http://nexus/content/groups/public/org/jboss/forge/furnace/furnace/2.17.0...
> ...
> 13:57:30 [INFO] Downloaded: http://nexus/content/groups/public/net/sf/jgrapht/jgrapht/0.8.3/jgrapht-0... (240 KB at 571.6 KB/sec)
> 13:57:30 [INFO] Downloaded: http://nexus/content/groups/public/org/jboss/forge/furnace/furnace-manage... (39 KB at 53.4 KB/sec)
> 13:57:30 Downloading: http://repo1.maven.org/maven2/io/fabric8/forge/camel/2.2.0-3/camel-2.2.0-...
> 13:57:31
> [INFO] Installation request for [io.fabric8.forge:camel,2.2.0-3] will:
> 13:57:31 Deploy: [io.fabric8.forge:camel,2.2.0-3]
> 13:57:31
> 13:57:31 Downloading: http://repo1.maven.org/maven2/io/fabric8/forge/camel/2.2.0-3/camel-2.2.0-...
> 13:57:42
> 13:57:43 [ERROR] Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.17.0.Final:addon-install (deploy-addons) on project fabric8-forge: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.17.0.Final:addon-install failed: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact io.fabric8.forge:camel:jar:forge-addon:2.2.0-3 in central (http://repo1.maven.org/maven2) -> [Help 1]
> 13:57:43 [ERROR]
> {code}
> Notice that its downloaded tons of stuff from the proxy - including the camel/2.2.0-3/camel-2.2.0-3-forge-addon.jar - then the furnace plugin decides to try again - but this time with maven central (even though its already downloaded)
> here's the maven settings
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <settings>
> <!--This sends everything else to /public -->
> <mirrors>
> <mirror>
> <id>nexus</id>
> <mirrorOf>external:*</mirrorOf>
> <url>http://nexus/content/groups/public</url>
> </mirror>
> </mirrors>
> <servers>
> <server>
> <id>nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> <server>
> <id>local-nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> </servers>
> </settings>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Daniel Cunha (soro) created FORGE-2314:
------------------------------------------
Summary: Should display warning when exists conflict name between commands
Key: FORGE-2314
URL: https://issues.jboss.org/browse/FORGE-2314
Project: Forge
Issue Type: Feature Request
Reporter: Daniel Cunha (soro)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)