November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1321: ---------------------------------------- [~gastaldi], I was able to reproduce this against my local Nexus instance. I got this stacktrace dumped on the error: {noformat} Downloading: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/p... java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-api:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-impl:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:resources:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:projects:jar:forge-addon:2.0.0-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-20131120.220705-132 from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/c... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:105) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.resolveResources(LazyAddonInfo.java:88) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.getResources(LazyAddonInfo.java:39) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.deploy(DeployRequestImpl.java:59) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl$1.call(DeployRequestImpl.java:49) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.execute(DeployRequestImpl.java:44) at org.jboss.forge.furnace.manager.impl.request.AbstractAddonActionRequest.perform(AbstractAddonActionRequest.java:57) at org.jboss.forge.furnace.manager.impl.request.InstallRequestImpl.perform(InstallRequestImpl.java:39) at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:229) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:147) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) {noformat} Going by this, and the Lightweight HTTP wagon internals, I'd concur that unnecessary or incorrect server settings should be removed from settings.xml. With the lightweight HTTP wagon, the passwords are used only when a challenge is issued. For some reason, the URLConnection and Authenticator classes in the JRE work together to request the password retrieved from the settings.xml (which is done only when the server requires authentication; obviously the server requested authentication even though anonymous access was sufficient). > Failure to install addons when using secure repositories > -------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.0.0.Beta4 > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1340) MavenContainer should return exceptions stored in the Aether result objects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1340?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1340: ---------------------------------------- This is needed to display the exceptions to the output when needed > MavenContainer should return exceptions stored in the Aether result objects > --------------------------------------------------------------------------- > > Key: FORGE-1340 > URL: https://issues.jboss.org/browse/FORGE-1340 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > The exceptions available in the Aether result classes should be returned when the Aether API is used. > The best solution is to create a Result object . > This includes MavenAddonDependencyResolver in furnace-manager and the maven addon. > {quote} > <gastaldi> we should break the API > <gastaldi> but I am unsure if those exceptions shouldn't be just logged or thrown up the stack > <vineetreynolds> gastaldi, Hmm I think they need to stored > <gastaldi> because they shouldn't impact in the usage I guess > <vineetreynolds> Not logged or thrown > <gastaldi> you mean like the Result objects in Aether? > <vineetreynolds> The choice on whether and when to throw should be decided by some other class > <vineetreynolds> gastaldi, Yes > <vineetreynolds> I dont think we should use the Result object in Aether directly though > <gastaldi> of course not > <gastaldi> but we should have our own Result object perhaps > <vineetreynolds> Better to create our own abstraction otherwise every change in Aether would affect us > <vineetreynolds> Yes > <gastaldi> :P this is going to be nasty > <gastaldi> but doable > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1340) MavenContainer should return exceptions stored in the Aether result objects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1340?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1340. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Created a Response object for Furnace Manager Maven operations > MavenContainer should return exceptions stored in the Aether result objects > --------------------------------------------------------------------------- > > Key: FORGE-1340 > URL: https://issues.jboss.org/browse/FORGE-1340 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > The exceptions available in the Aether result classes should be returned when the Aether API is used. > The best solution is to create a Result object . > This includes MavenAddonDependencyResolver in furnace-manager and the maven addon. > {quote} > <gastaldi> we should break the API > <gastaldi> but I am unsure if those exceptions shouldn't be just logged or thrown up the stack > <vineetreynolds> gastaldi, Hmm I think they need to stored > <gastaldi> because they shouldn't impact in the usage I guess > <vineetreynolds> Not logged or thrown > <gastaldi> you mean like the Result objects in Aether? > <vineetreynolds> The choice on whether and when to throw should be decided by some other class > <vineetreynolds> gastaldi, Yes > <vineetreynolds> I dont think we should use the Result object in Aether directly though > <gastaldi> of course not > <gastaldi> but we should have our own Result object perhaps > <vineetreynolds> Better to create our own abstraction otherwise every change in Aether would affect us > <vineetreynolds> Yes > <gastaldi> :P this is going to be nasty > <gastaldi> but doable > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1340) MavenContainer should return exceptions stored in the Aether result objects

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1340: -------------------------------------- Summary: MavenContainer should return exceptions stored in the Aether result objects Key: FORGE-1340 URL: https://issues.jboss.org/browse/FORGE-1340 Project: Forge Issue Type: Feature Request Components: Build Tools - Maven Affects Versions: 2.0.0.Beta3 Reporter: George Gastaldi Fix For: 2.x Future The exceptions available in the Aether result classes should be returned when the Aether API is used. The best solution is to create a Result object . This includes MavenAddonDependencyResolver in furnace-manager and the maven addon. {quote} <gastaldi> we should break the API <gastaldi> but I am unsure if those exceptions shouldn't be just logged or thrown up the stack <vineetreynolds> gastaldi, Hmm I think they need to stored <gastaldi> because they shouldn't impact in the usage I guess <vineetreynolds> Not logged or thrown <gastaldi> you mean like the Result objects in Aether? <vineetreynolds> The choice on whether and when to throw should be decided by some other class <vineetreynolds> gastaldi, Yes <vineetreynolds> I dont think we should use the Result object in Aether directly though <gastaldi> of course not <gastaldi> but we should have our own Result object perhaps <vineetreynolds> Better to create our own abstraction otherwise every change in Aether would affect us <vineetreynolds> Yes <gastaldi> :P this is going to be nasty <gastaldi> but doable {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1249?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1249. ---------------------------------- Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Fixed in java-parser 2.0.0.Alpha1. Commit: https://github.com/forge/java-parser/commit/98da63fd0ea0722f94c9864d25720... > JavaAnnotationImpl should not implement InterfaceCapable > -------------------------------------------------------- > > Key: FORGE-1249 > URL: https://issues.jboss.org/browse/FORGE-1249 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.0.0.Beta4 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1245) Importer+#requiresImport() should return false for types in same package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1245?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1245. ---------------------------------- Resolution: Done Fixed in 2.0.0.Alpha1 > Importer+#requiresImport() should return false for types in same package > ------------------------------------------------------------------------ > > Key: FORGE-1245 > URL: https://issues.jboss.org/browse/FORGE-1245 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > The simple approach of comparing the package name of the Importer to the longest subsequence before any final dot in the name of the proposed import should suffice: the only exceptional case should be inner classes, which would require an import in any case in order to refer to one such by its simple name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1244) Types.isJavaLang() returns true for types in java.lang subpackages

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1244?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1244. ---------------------------------- Resolution: Done Fixed in java-parser 2.0.0.Alpha1 > Types.isJavaLang() returns true for types in java.lang subpackages > ------------------------------------------------------------------ > > Key: FORGE-1244 > URL: https://issues.jboss.org/browse/FORGE-1244 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > Since this method is used to implement Importer#requiresImport(), it leads to incorrect results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-715) Error while working with resources named as Java/FSH keywords

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-715?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-715. --------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Out of Date This no longer happens with Forge 2 + Aesh > Error while working with resources named as Java/FSH keywords > ------------------------------------------------------------- > > Key: FORGE-715 > URL: https://issues.jboss.org/browse/FORGE-715 > Project: Forge > Issue Type: Bug > Components: Forge Scripting Language, UI - Shell > Affects Versions: 1.1.2.Final > Reporter: George Gastaldi > Labels: annoying > > Type the following: > {code} > cd for > {code} > The following error is thrown > {code} > ***ERROR*** Exception encountered: 6 (type "set VERBOSE true" to enable stack traces) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1153) ForgeDeployableContainer should allow specifying a different classifier

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1153?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1153. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > ForgeDeployableContainer should allow specifying a different classifier > ----------------------------------------------------------------------- > > Key: FORGE-1153 > URL: https://issues.jboss.org/browse/FORGE-1153 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container), Test Harness > Affects Versions: 2.0.0.Alpha11 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > As of FORGE-1152, MavenAddonDependencyResolver now allows specifying a new classifier for addons -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1339) Mandatory attributes in CLI

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1339?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1339. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > Mandatory attributes in CLI > --------------------------- > > Key: FORGE-1339 > URL: https://issues.jboss.org/browse/FORGE-1339 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > For the command {{jpa-new-entity}}, when you hit TAB, both {{named}} and {{idStrategy}} are in green (while {{targetPackage}} is in black). I might be wrong, but green shows to me that both {{named}} and {{idStrategy}} are mandatory. Which is not the case : {{named}} IS mandatory but {{idStrategy}} is not -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013