June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1913) Furnace build forces use of settings.xml instead of settings supplied to Maven

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1913: -------------------------------------- Summary: Furnace build forces use of settings.xml instead of settings supplied to Maven Key: FORGE-1913 URL: https://issues.jboss.org/browse/FORGE-1913 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Furnace (Container) Affects Versions: 2.7.0.Final Reporter: Vineet Reynolds The following test failures are encountered, when I have (but dont use) a settings.xml that refers to my local Nexus mirror: {noformat} ------------------------------------------------------- T E S T S ------------------------------------------------------- Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=160m; support was removed in 8.0 Running org.jboss.forge.furnace.manager.impl.AddonManagerRepositoryTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.073 sec - in org.jboss.forge.furnace.manager.impl.AddonManagerRepositoryTest Running org.jboss.forge.furnace.manager.impl.AddonManagerRealTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.035 sec <<< FAILURE! - in org.jboss.forge.furnace.manager.impl.AddonManagerRealTest testInstallUIAddon(org.jboss.forge.furnace.manager.impl.AddonManagerRealTest) Time elapsed: 0.654 sec <<< ERROR! java.lang.RuntimeException: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:ui:jar:forge-addon:2.0.0.Alpha6 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.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:320) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:212) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:317) at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.traverseAddonGraph(MavenAddonDependencyResolver.java:333) at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveAddonDependencyHierarchy(MavenAddonDependencyResolver.java:86) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.info(AddonManagerImpl.java:54) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:67) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:60) at org.jboss.forge.furnace.manager.impl.AddonManagerRealTest.testInstallUIAddon(AddonManagerRealTest.java:91) Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.jboss.forge.addon:ui:pom:2.0.0.Alpha6 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/u... 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/u... 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) at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) testInstallAddonAddon(org.jboss.forge.furnace.manager.impl.AddonManagerRealTest) Time elapsed: 0.38 sec <<< ERROR! java.lang.RuntimeException: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:addons:jar:forge-addon:2.0.0.Alpha6 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.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:320) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:212) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:317) at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.traverseAddonGraph(MavenAddonDependencyResolver.java:333) at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveAddonDependencyHierarchy(MavenAddonDependencyResolver.java:86) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.info(AddonManagerImpl.java:54) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:67) at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:60) at org.jboss.forge.furnace.manager.impl.AddonManagerRealTest.testInstallAddonAddon(AddonManagerRealTest.java:77) Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.jboss.forge.addon:addons:pom:2.0.0.Alpha6 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/a... 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/a... 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) at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {noformat} The Furnace build itself is triggered via {{mvn -s ~/.m2/settings-without-nexus.xml clean install}} where {{settings-without-nexus.xml}} as the file name implies, resolves artifacts from M2 central and JBoss Nexus. Replacing contents of settings.xml with that of {{settings-without-nexus.xml}} resolves this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-120) Invalid AngularJS controllers are generated

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-120?page=com.atlassian.jira.... ] Vineet Reynolds commented on FORGEPLUGINS-120: ---------------------------------------------- Supporting composite keys in the AngularJS scaffold would require AngularJS to support matrix URIs. Support for this is residing in a [PR #4067|https://github.com/angular/angular.js/pull/4067]. > Invalid AngularJS controllers are generated > ------------------------------------------- > > Key: FORGEPLUGINS-120 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-120 > Project: Forge Plugins > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: AngularJS Scaffold > Environment: AngularJS scaffold plugin v1.0.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The following code is generated in the AngularJS controllers via the Scaffolding plugin: > {noformat} > if($scope.actor.filmActors){ > $.each($scope.actor.filmActors, function(idx, element) { > if(item. == element.) { > $scope.filmActorsSelection.push(wrappedObject); > } > }); > } > {noformat} > Note the invalid comparison expression. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1912) Embedded maven execution does not use the user settings file set as a system property

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1912?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1912: ----------------------------------- Summary: Embedded maven execution does not use the user settings file set as a system property (was: Embedded maven execution does not use the user settings flie set as a system property) > Embedded maven execution does not use the user settings file set as a system property > ------------------------------------------------------------------------------------- > > Key: FORGE-1912 > URL: https://issues.jboss.org/browse/FORGE-1912 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Maven > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1912) Embedded maven execution does not use the user settings file set as a system property

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1912?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1912. ---------------------------------- Resolution: Done > Embedded maven execution does not use the user settings file set as a system property > ------------------------------------------------------------------------------------- > > Key: FORGE-1912 > URL: https://issues.jboss.org/browse/FORGE-1912 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Maven > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1912) Embedded maven execution does not use the user settings flie set as a system property

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1912: -------------------------------------- Summary: Embedded maven execution does not use the user settings flie set as a system property Key: FORGE-1912 URL: https://issues.jboss.org/browse/FORGE-1912 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Maven Affects Versions: 2.6.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.7.0.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin... ] Matej Briskar edited comment on FORGE-1898 at 6/26/14 1:22 PM: --------------------------------------------------------------- The problem is only with the projects containing the java keyword separated by dashes, because MavenMetadataFacet uses groupId to generate the package without any validation. There are 2 possible solutions: 1) Create our own checker, for example similar to this: http://forum.codecall.net/topic/62656-java-identifier-checker/ 2) Use some 3rd party library like http://commons.apache.org/sandbox/commons-classscan/apidocs/org/apache/co... was (Author: mbriskar): The problem is only with the projects containing the java keyword separated by dashes, because MavenMetadataFacet uses groupId to generate the package without checking for them. There are 2 possible solutions: 1) Create our own checker, for example similar to this: http://forum.codecall.net/topic/62656-java-identifier-checker/ 2) Use some 3rd party library like http://commons.apache.org/sandbox/commons-classscan/apidocs/org/apache/co... > Dashes in the project name makes jpa-new-entity execution to fail > ----------------------------------------------------------------- > > Key: FORGE-1898 > URL: https://issues.jboss.org/browse/FORGE-1898 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin... ] Matej Briskar commented on FORGE-1898: -------------------------------------- The problem is only with the projects containing the java keyword separated by dashes, because MavenMetadataFacet uses groupId to generate the package without checking for them. There are 2 possible solutions: 1) Create our own checker, for example similar to this: http://forum.codecall.net/topic/62656-java-identifier-checker/ 2) Use some 3rd party library like http://commons.apache.org/sandbox/commons-classscan/apidocs/org/apache/co... > Dashes in the project name makes jpa-new-entity execution to fail > ----------------------------------------------------------------- > > Key: FORGE-1898 > URL: https://issues.jboss.org/browse/FORGE-1898 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin... ] Matej Briskar reassigned FORGE-1898: ------------------------------------ Assignee: Matej Briskar > Dashes in the project name makes jpa-new-entity execution to fail > ----------------------------------------------------------------- > > Key: FORGE-1898 > URL: https://issues.jboss.org/browse/FORGE-1898 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1802) Console hangs when running an invalid script

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1802?page=com.atlassian.jira.plugin... ] Ståle Pedersen commented on FORGE-1802: --------------------------------------- here is a poc of how to do it; https://github.com/aeshell/aesh/commit/0afd74e5732159b0836d280700753cede8... > Console hangs when running an invalid script > -------------------------------------------- > > Key: FORGE-1802 > URL: https://issues.jboss.org/browse/FORGE-1802 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.7.0.Final > > > I am executing a script (with the {{run}} command) and the console hanged and stopped working completely (I had to kill the process). I realized that there is an error in the script (missing {{;}} at the end of line {{--named ISBN}}). > Take the following script, and save it on a {{hangs.fsh}} file > {code} > # ##################### # > # Creates a new project # > # ##################### # > project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ; > # Setup the persistence unit in persistence.xml > # ############ > jpa-setup --persistenceUnitName cdbookstorePU ; > # ######################## # > # Creates the domain model # > # ######################## # > # ISBN constraint > # ############ > constraint-new-annotation --named ISBN > # Genre entity > # ############ > jpa-new-entity --named Genre ; > jpa-new-field --named name --length 100 ; > {code} > Now, execute the script, and see the error message : > {code} > [temp]$ run hangs.fsh > project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ; > ***SUCCESS*** Project named 'cdbookstore' has been created. > [cdbookstore]$ jpa-setup --persistenceUnitName cdbookstorePU ; > ***SUCCESS*** Persistence (JPA) is installed. > [cdbookstore]$ constraint-new-annotation --named ISBN > ***SUCCESS*** Bean Validation Constraint Annotations org.agoncal.training.javaee6adv.constraints.ISBN was created > [ISBN.java]$ jpa-new-entity --named Genre ; > Exception when parsing/running: jpa-new-entity --named Genre , org.jboss.forge.roaster.model.impl.JavaAnnotationImpl cannot be cast to org.jboss.forge.roaster.model.MemberHolder > [ISBN.java]$ > {code} > At this point, I can't interact with the console and need to kill the process. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1398) Being able to create embeddables

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1398?page=com.atlassian.jira.plugin... ] Matej Briskar commented on FORGE-1398: -------------------------------------- Already implemented the command + relationshipType. What about restricting user to select @Embedded relationshipType for not an @Embeddable object and vice versa? E.g not showing these relationTypes as suggestions? > Being able to create embeddables > -------------------------------- > > Key: FORGE-1398 > URL: https://issues.jboss.org/browse/FORGE-1398 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Matej Briskar > Fix For: 2.x Future > > > As per [FORGE-797] it would be good to have a new command to create an embeddable : > {code} > jpa-new-embeddable --named Address ; > jpa-new-field --named street1 --length 50 ; > jpa-new-field --named street2 ; > jpa-new-field --named city --length 50 ; > jpa-new-field --named state ; > {code} > Then, how do we embed it into a entity ? We could have a new {{--relationshipType}} : > {code} > jpa-new-entity --named Customer ; > jpa-new-field --named address --entity org.agoncal.application.petstore.model.Address --relationshipType Embedded ; > {code} > Except {{Address}} is not an entity. So having {{--entity}} pointing to an embeddable looks strange -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014