November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1307) Forge 2 Resolve Maven Dependencies using a protected repo

by David Beer (JIRA)

[ https://issues.jboss.org/browse/FORGE-1307?page=com.atlassian.jira.plugin... ] David Beer commented on FORGE-1307: ----------------------------------- Stack Trace and output is as follows: dbeer@vulcan:~/Software-Development/forge-distribution-2.0.0.Alpha14$ ./bin/forge --install shell Using Forge at /home/dbeer/Software-Development/forge-distribution-2.0.0.Alpha14 Warning: JAVA_HOME environment variable is not set. Installation request for [org.jboss.forge.addon:shell,2.0.0.Alpha13] will: Deploy: [org.jboss.forge.addon:shell-spi,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:convert,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:environment,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:ui-spi,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:ui,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:facets,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:resources,2.0.0.Alpha13] Deploy: [org.jboss.forge.furnace.container:cdi,2.0.0.Alpha13] Deploy: [org.jboss.forge.addon:shell,2.0.0.Alpha13] java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: Could not transfer artifact org.jboss.forge.addon:facets:jar:forge-addon:2.0.0.Alpha13 from/to central (http:/xxxxxxxxx/artifactory/repo): Access denied to: http://xxxxxxxxx/artifactory/repo/org/jboss/forge/addon/facets/2.0.0.Alph... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:97) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.resolveResources(LazyAddonInfo.java:87) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.getResources(LazyAddonInfo.java:38) 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:207) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not transfer artifact org.jboss.forge.addon:facets:jar:forge-addon:2.0.0.Alpha13 from/to central (http://xxxxxxx/artifactory/repo): Access denied to: http://xxxxxxxxx/artifactory/repo/org/jboss/forge/addon/facets/2.0.0.Alph... at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384) at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:93) ... 11 more Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.jboss.forge.addon:facets:jar:forge-addon:2.0.0.Alpha13 from/to central (http://xxxxxxxxxxxx/artifactory/repo): Access denied to: http://xxxxxxxxxx/artifactory/repo/org/jboss/forge/addon/facets/2.0.0.Alp... at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:459) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) ... 12 more Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.jboss.forge.addon:facets:jar:forge-addon:2.0.0.Alpha13 from/to central (http://xxxxxxxxxx/artifactory/repo): Access denied to: http://xxxxxxxxxxxxx/artifactory/repo/org/jboss/forge/addon/facets/2.0.0.... at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1016) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:725) at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://xxxxxxxx/artifactory/repo/org/jboss/forge/addon/facets/2.0.0.Alpha... at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:145) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:660) ... 4 more > Forge version [2.0.0.Alpha14] > Forge 2 Resolve Maven Dependencies using a protected repo > --------------------------------------------------------- > > Key: FORGE-1307 > URL: https://issues.jboss.org/browse/FORGE-1307 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha14 > Environment: Linux, > java version "1.7.0_25" > OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > Reporter: David Beer > > Trying to install Shell in forge 2. Dependencies are not resolved on a password protected maven repository. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1307) Forge 2 Resolve Maven Dependencies using a protected repo

by David Beer (JIRA)

David Beer created FORGE-1307: --------------------------------- Summary: Forge 2 Resolve Maven Dependencies using a protected repo Key: FORGE-1307 URL: https://issues.jboss.org/browse/FORGE-1307 Project: Forge Issue Type: Bug Components: Build Tools - Maven Affects Versions: 2.0.0.Alpha14 Environment: Linux, java version "1.7.0_25" OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) Reporter: David Beer Trying to install Shell in forge 2. Dependencies are not resolved on a password protected maven repository. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1208) Furnace test harness should deploy @AddonDependencies only once per @Deployment

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1208?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1208. ------------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix This did not result in any real performance gain. Will leave the branch in version control, but closing this issue as "wont fix." > Furnace test harness should deploy @AddonDependencies only once per @Deployment > ------------------------------------------------------------------------------- > > Key: FORGE-1208 > URL: https://issues.jboss.org/browse/FORGE-1208 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container), Test Harness > Affects Versions: 2.0.0.Alpha12 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1305) Introduce an API equivalent to AbstractProjectCommand for UIWizardStep

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1305?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1305. ------------------------------------- Resolution: Rejected > Introduce an API equivalent to AbstractProjectCommand for UIWizardStep > ---------------------------------------------------------------------- > > Key: FORGE-1305 > URL: https://issues.jboss.org/browse/FORGE-1305 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > > The {{AbstractProjectCommand}} type corresponding to the {{UICommand}} type provides access to the current project via the {{getSelectedProject(context)}} API. > There is no such project-inclusive equivalent API for the {{UIWizardStep}}, to provide the selected project to UIWizardStep implementations. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1305) Introduce an API equivalent to AbstractProjectCommand for UIWizardStep

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1305?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1305: ------------------------------------------- A UIWizardStep is a UICommand, so this API should work fine in both places. Give it a try and let me know if it works. Also, if this is confusing, how do you think we can better clear it up? > Introduce an API equivalent to AbstractProjectCommand for UIWizardStep > ---------------------------------------------------------------------- > > Key: FORGE-1305 > URL: https://issues.jboss.org/browse/FORGE-1305 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > > The {{AbstractProjectCommand}} type corresponding to the {{UICommand}} type provides access to the current project via the {{getSelectedProject(context)}} API. > There is no such project-inclusive equivalent API for the {{UIWizardStep}}, to provide the selected project to UIWizardStep implementations. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1304) Top level facets are not detected as installed even though subtype facets are installed

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1304?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1304: ------------------------------------------- I am not able to reproduce this in tests: https://github.com/forge/core/blob/2.0/javaee/tests/src/test/java/org/jbo... I'll try again tomorrow by attempting to roll back your workaround in the branch. > Top level facets are not detected as installed even though subtype facets are installed > --------------------------------------------------------------------------------------- > > Key: FORGE-1304 > URL: https://issues.jboss.org/browse/FORGE-1304 > Project: Forge > Issue Type: Bug > Components: Plugin API > Reporter: Vineet Reynolds > > The invocation {{project.getFacet(ServletFacet.class)}} returns null event though the project has the Servlet 3.0 facet associated with it. > This requires explicit invocations like {{project.getFacet(ServletFacet_3_0.class)}}, {{project.getFacet(ServletFacet_3_1.class)}} etc. > This also affects other top-level facets like the CDI and EJB facets. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1306) JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1306?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1306: ----------------------------------------- Assignee: Lincoln Baxter III > JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package > ------------------------------------------------------------------------------------------------- > > Key: FORGE-1306 > URL: https://issues.jboss.org/browse/FORGE-1306 > Project: Forge > Issue Type: Bug > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Assignee: Lincoln Baxter III > > {{AbstractJPAFacetImpl.getAllEntities()}} relies on the JPA entities being present in the same package in a project with the JPA facet. Additionally, it expects the package to be named "<groupId>.model". > The REST and Scaffold addons therefore depend on the JPA entities to be present in this package, failing which no entities are displayed to the user. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1306) JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1306?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1306. ------------------------------------- Fix Version/s: 2.0.0.Beta1 Resolution: Done > JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package > ------------------------------------------------------------------------------------------------- > > Key: FORGE-1306 > URL: https://issues.jboss.org/browse/FORGE-1306 > Project: Forge > Issue Type: Bug > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta1 > > > {{AbstractJPAFacetImpl.getAllEntities()}} relies on the JPA entities being present in the same package in a project with the JPA facet. Additionally, it expects the package to be named "<groupId>.model". > The REST and Scaffold addons therefore depend on the JPA entities to be present in this package, failing which no entities are displayed to the user. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1306) JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1306: -------------------------------------- Summary: JPAFacet.getAllEntities should not expect JPA entities to be present in a predefined Java package Key: FORGE-1306 URL: https://issues.jboss.org/browse/FORGE-1306 Project: Forge Issue Type: Bug Components: Blessed Plugins Affects Versions: 2.0.0.Alpha14 Reporter: Vineet Reynolds {{AbstractJPAFacetImpl.getAllEntities()}} relies on the JPA entities being present in the same package in a project with the JPA facet. Additionally, it expects the package to be named "<groupId>.model". The REST and Scaffold addons therefore depend on the JPA entities to be present in this package, failing which no entities are displayed to the user. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1303) Use Weld's new Singleton API

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1303?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1303: ------------------------------------------- I guess we never got around to submitting a PR for this :) > Use Weld's new Singleton API > ---------------------------- > > Key: FORGE-1303 > URL: https://issues.jboss.org/browse/FORGE-1303 > Project: Forge > Issue Type: Task > Components: Furnace (Container) > Reporter: Jozef Hartinger > > Since Weld 2.1 it is possible to use the new Singleton API http://docs.jboss.org/weld/javadoc/2.1/weld-spi/org/jboss/weld/bootstrap/... > A String identifier was added to all Singleton's methods. The identifier is used to identify a Weld container. As a result, it is no longer necessary to use the TCCL to identify the right Weld container. > I am not sure if Forge currently sets the TCCL just because Weld required it in the past or if it is used for something else but either way the new SPI should simplify integration. > For each module Forge should generate a unique id and pass it to Weld when calling WeldBootstrap.startContainer(). -- 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 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013