November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1320) Perform a UX review of the Shell experience in Forge 2

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1320?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1320: -------------------------------------- Fix Version/s: 2.x Future > Perform a UX review of the Shell experience in Forge 2 > ------------------------------------------------------ > > Key: FORGE-1320 > URL: https://issues.jboss.org/browse/FORGE-1320 > Project: Forge > Issue Type: Task > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- 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-1107) Avoiding setters in DependencyBuilder

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1107?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1107: -------------------------------------- Fix Version/s: 2.x Future > Avoiding setters in DependencyBuilder > ------------------------------------- > > Key: FORGE-1107 > URL: https://issues.jboss.org/browse/FORGE-1107 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 2.0.0.Alpha10 > Environment: DependencyBuilder Class > Reporter: Rajmahendra Hegde > Priority: Minor > Fix For: 2.x Future > > > As the name suggests "Builder" we can better remove some of general setter naming of the properties like > setGroupId > setArtifactId > setVersion > etc > and make them > groupId > artifactId > version > etc > So its easy to type. -- 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-1322) Checks for versioned facet installation are insufficient

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1322?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1322: -------------------------------------- Fix Version/s: 2.x Future > Checks for versioned facet installation are insufficient > -------------------------------------------------------- > > Key: FORGE-1322 > URL: https://issues.jboss.org/browse/FORGE-1322 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.x Future > > > The current checks in the {{isInstalled}} method of most versioned Facets include the following line: > {noformat} > return super.isInstalled() && getConfigFile().exists(); > {noformat} > This is insufficient since the config file could exist but could contain a different version. The facet should not be activated in such a case. -- 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-1263) Furnace Imported<?> does not support selecting services with type parameters

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1263?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1263: -------------------------------------- Fix Version/s: 2.x Future > Furnace Imported<?> does not support selecting services with type parameters > ---------------------------------------------------------------------------- > > Key: FORGE-1263 > URL: https://issues.jboss.org/browse/FORGE-1263 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- 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-1264) Furnace CDI container requires implementation coupling to provide generic typed service

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1264?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1264: -------------------------------------- Fix Version/s: 2.x Future > Furnace CDI container requires implementation coupling to provide generic typed service > --------------------------------------------------------------------------------------- > > Key: FORGE-1264 > URL: https://issues.jboss.org/browse/FORGE-1264 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > ExportedInstanceLazyLoader.loadObject() > {code} > private Object loadObject() throws Exception > { > Object result = null; > for (Addon addon : registry.getAddons(ALL_STARTED)) > { > if (ClassLoaders.containsClass(addon.getClassLoader(), serviceType)) > { > ServiceRegistry serviceRegistry = addon.getServiceRegistry(); > if (serviceRegistry.hasService(serviceType)) > { > ExportedInstance<?> instance = serviceRegistry.getExportedInstance(serviceType); > if (instance != null) > { > if (instance instanceof ExportedInstanceImpl) > // FIXME remove the need for this implementation coupling > result = ((ExportedInstanceImpl<?>) instance).get(new LocalServiceInjectionPoint( > injectionPoint, > serviceType)); > else > result = instance.get(); > if (result != null) > break; > } > } > } > } > if (result == null) > { > throw new IllegalStateException("Remote service [" + serviceType.getName() + "] is not registered."); > } > return result; > } > {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-1317) Enable usage tracking for Forge in JBoss Tools

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1317?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1317: -------------------------------------- Fix Version/s: 2.x Future > Enable usage tracking for Forge in JBoss Tools > ---------------------------------------------- > > Key: FORGE-1317 > URL: https://issues.jboss.org/browse/FORGE-1317 > Project: Forge > Issue Type: Task > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Usage tracking is currently disabled for the Forge instance running in JBT/JBDS. We might want to activate usage tracking for this "embedded" Forge instance if JBDS usage tracking is enabled. -- 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-1317) Enable usage tracking for Forge in JBoss Tools

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1317?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1317: -------------------------------------- Affects Version/s: 2.0.0.Alpha14 > Enable usage tracking for Forge in JBoss Tools > ---------------------------------------------- > > Key: FORGE-1317 > URL: https://issues.jboss.org/browse/FORGE-1317 > Project: Forge > Issue Type: Task > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Usage tracking is currently disabled for the Forge instance running in JBT/JBDS. We might want to activate usage tracking for this "embedded" Forge instance if JBDS usage tracking is enabled. -- 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-1312) UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1312?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1312: -------------------------------------- Fix Version/s: 2.x Future > UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed > --------------------------------------------------------------------------------------------------- > > Key: FORGE-1312 > URL: https://issues.jboss.org/browse/FORGE-1312 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Related to FORGE-1131, in the Scaffold setup wizard, I have: > {noformat} > @Override > public Result execute(UIContext context) throws Exception > { > ScaffoldProvider selectedProvider = provider.getValue(); > selectedProvider.setup(getSelectedProject(context), createSetupContext()); > return Results.success("Scaffold was setup successfully."); > } > {noformat} > This is expected to be executed only after all other setup wizards and commands have been executed. For example, if the Faces scaffold provider is being setup, then any or all of CDI, EJB, Servlet, Faces and JPA setup wizards must be executed before {{ScaffoldSetupWizard.execute()}} is invoked. This is not the case currently, resulting in {{ScaffoldSetupWizard.execute()}} being invoked first. -- 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-1318) Create a project governance page on the new 2.0 website

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1318?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1318: -------------------------------------- Fix Version/s: 2.x Future > Create a project governance page on the new 2.0 website > ------------------------------------------------------- > > Key: FORGE-1318 > URL: https://issues.jboss.org/browse/FORGE-1318 > Project: Forge > Issue Type: Task > Components: Website > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > http://wildfly.org/governance/ -- 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-1136) Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1136?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1136: -------------------------------------- Fix Version/s: 2.x Future > Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host > ------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-1136 > URL: https://issues.jboss.org/browse/FORGE-1136 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > This is related to FORGE-1134. > When attempting to resolve dependencies from multiple repositories present on the same host, Forge (actually Maven and Aether) fails to resolve certain dependencies. > The following is an example: > {noformat} > [no project] vineet $ forge install-plugin arquillian > Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected! > ***INFO*** Preparing to install plugin: arquillian > ***INFO*** Checking out plugin source files to [/tmp/forgetemp448150160827402029] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final > Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor... > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final > Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor... > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final > Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor... > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final > Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor... > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final > Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor... > ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] > ***INFO*** Cleaning up temp workspace [/tmp/forgetemp448150160827402029] > Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml > Deleted /tmp/forgetemp448150160827402029 > ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces) > [no project] vineet $ > {noformat} > In this case, some of the dependencies (present in M2 central) were resolved successfully, while others (present in the public repo group) were not. The underlying cause was that the resolved dependencies were present in a repository or repository group via a valid username+password combination. The unresolved dependencies were also present in a repository or repository group protected by a username+password combination. Although valid credentials were provided by Forge to Maven/Aether for the second repository, this was not used by Maven/Aether. > The underlying reason is that the JVM caches the credentials used by the Maven LightweightHTTPWagon implementation since the credentials are supplied via a {{java.net.Authenticator}} instance. This forces only one set of credentials to be used at runtime; the second set of credentials will be ignored. -- 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