August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1134) Forge fails to resolve dependencies in password protected Maven repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1134?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1134: ----------------------------------- Priority: Critical (was: Major) > Forge fails to resolve dependencies in password protected Maven repositories > ---------------------------------------------------------------------------- > > Key: FORGE-1134 > URL: https://issues.jboss.org/browse/FORGE-1134 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Given a password protected repository defined in settings.xml, like: > {noformat} > ... > <server> > <id>central</id> > <username>testuser</username> > <password>testuser123</password></server> > </servers> > ... > <profiles> > <profile> > <id>nexus</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <repositories> > <repository> > <id>central</id> > <url>http://localhost:8081/nexus/content/repositories/central/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>central</id> > <url>http://localhost:8081/nexus/content/repositories/central/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </pluginRepository> > </pluginRepositories> > </profile> > </profiles> > {noformat} > Forge fails to resolve artifacts, since it does not take the passwords into consideration when attempting to resolve the artifacts, resulting in an error like so (with the fix for FORGE-1133) : > {noformat} > [no project] vineet $ forge install-plugin arquillian > ***INFO*** Preparing to install plugin: arquillian > ***INFO*** Checking out plugin source files to [/tmp/forgetemp6567964705967228540] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] > ***WARNING*** Failed to read artifact descriptor for org.apache.velocity:velocity:jar:1.7 > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.sonatype.aether:aether-api:jar:1.11 > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-core-asl:jar:1.9.1 > ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-mapper-asl:jar:1.9.1 > ***WARNING*** Failed to read artifact descriptor for junit:junit:jar:4.8.2 > ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] > ***INFO*** Cleaning up temp workspace [/tmp/forgetemp6567964705967228540] > Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml > Deleted /tmp/forgetemp6567964705967228540 > ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces) > {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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1134) Forge fails to resolve dependencies in password protected Maven repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1134?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1134: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/346 If a repository is defined along with a server configuration element in settings.xml, then any username and password settings configured, are used for that repository. Additionally, any activeByDefault profiles are treated as active profiles with this fix. > Forge fails to resolve dependencies in password protected Maven repositories > ---------------------------------------------------------------------------- > > Key: FORGE-1134 > URL: https://issues.jboss.org/browse/FORGE-1134 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Given a password protected repository defined in settings.xml, like: > {noformat} > ... > <server> > <id>central</id> > <username>testuser</username> > <password>testuser123</password></server> > </servers> > ... > <profiles> > <profile> > <id>nexus</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <repositories> > <repository> > <id>central</id> > <url>http://localhost:8081/nexus/content/repositories/central/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>central</id> > <url>http://localhost:8081/nexus/content/repositories/central/</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </pluginRepository> > </pluginRepositories> > </profile> > </profiles> > {noformat} > Forge fails to resolve artifacts, since it does not take the passwords into consideration when attempting to resolve the artifacts, resulting in an error like so (with the fix for FORGE-1133) : > {noformat} > [no project] vineet $ forge install-plugin arquillian > ***INFO*** Preparing to install plugin: arquillian > ***INFO*** Checking out plugin source files to [/tmp/forgetemp6567964705967228540] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] > ***WARNING*** Failed to read artifact descriptor for org.apache.velocity:velocity:jar:1.7 > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.sonatype.aether:aether-api:jar:1.11 > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final > ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-core-asl:jar:1.9.1 > ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-mapper-asl:jar:1.9.1 > ***WARNING*** Failed to read artifact descriptor for junit:junit:jar:4.8.2 > ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] > ***INFO*** Cleaning up temp workspace [/tmp/forgetemp6567964705967228540] > Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml > Deleted /tmp/forgetemp6567964705967228540 > ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces) > {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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1135) ServletFacetImpl overrides isInstalled of BaseJavaEEFacet but doesnt call super.isInstalled

by Thomas Frühbeck (JIRA)

Thomas Frühbeck created FORGE-1135: -------------------------------------- Summary: ServletFacetImpl overrides isInstalled of BaseJavaEEFacet but doesnt call super.isInstalled Key: FORGE-1135 URL: https://issues.jboss.org/browse/FORGE-1135 Project: Forge Issue Type: Bug Components: Java EE APIs Affects Versions: 1.4.0.Final Reporter: Thomas Frühbeck -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1133) Error and exception handling for Maven dependency resolution does not warn of unresolved dependencies

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1133?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1133: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/346 This displays warnings in the Shell for collection and resolution errors in the full project build. It also displays warnings for problems found in the Maven project model. > Error and exception handling for Maven dependency resolution does not warn of unresolved dependencies > ----------------------------------------------------------------------------------------------------- > > Key: FORGE-1133 > URL: https://issues.jboss.org/browse/FORGE-1133 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Maven dependency resolution errors are not caught and handled appropriately, especially during plugin installation. The following behavior is observed when installing the Forge Arquillian plugin in an environment with an invalid Maven central location, like the one described [here|http://books.sonatype.com/nexus-book/reference/maven-sect-single-gro...], but without the mirror: > {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/forgetemp161339604102750966] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] > ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] > {noformat} > It would be better to display warnings or errors and possibly terminate any operations should this occur. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1134) Forge fails to resolve dependencies in password protected Maven repositories

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1134: -------------------------------------- Summary: Forge fails to resolve dependencies in password protected Maven repositories Key: FORGE-1134 URL: https://issues.jboss.org/browse/FORGE-1134 Project: Forge Issue Type: Bug Components: Build Tools - Maven Affects Versions: 1.4.0.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds Given a password protected repository defined in settings.xml, like: {noformat} ... <server> <id>central</id> <username>testuser</username> <password>testuser123</password></server> </servers> ... <profiles> <profile> <id>nexus</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories> <repository> <id>central</id> <url>http://localhost:8081/nexus/content/repositories/central/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>central</id> <url>http://localhost:8081/nexus/content/repositories/central/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> {noformat} Forge fails to resolve artifacts, since it does not take the passwords into consideration when attempting to resolve the artifacts, resulting in an error like so (with the fix for FORGE-1133) : {noformat} [no project] vineet $ forge install-plugin arquillian ***INFO*** Preparing to install plugin: arquillian ***INFO*** Checking out plugin source files to [/tmp/forgetemp6567964705967228540] via 'git' ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] ***WARNING*** Failed to read artifact descriptor for org.apache.velocity:velocity:jar:1.7 ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final ***WARNING*** Failed to read artifact descriptor for org.sonatype.aether:aether-api:jar:1.11 ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-core-asl:jar:1.9.1 ***WARNING*** Failed to read artifact descriptor for org.codehaus.jackson:jackson-mapper-asl:jar:1.9.1 ***WARNING*** Failed to read artifact descriptor for junit:junit:jar:4.8.2 ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] ***INFO*** Cleaning up temp workspace [/tmp/forgetemp6567964705967228540] Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml Deleted /tmp/forgetemp6567964705967228540 ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces) {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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1067) Adopt WebJars as encapsulation for Bootstrap and JQuery resources

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1067?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1067: ------------------------------------------ Lincoln, Java EE will never (never say never, let's say 'will not in the near future') standardize CSS or JavaScript libraries (except for jsf.js which manages Ajax calls within JSF). If Forge uses Bootstrap by default, why not using WebJar for this non-JavaEE library ? We could say something like "Forge uses Java EE as its core Java dependency and other external non-Java EE dependencies such as Bootstrap". > Adopt WebJars as encapsulation for Bootstrap and JQuery resources > ----------------------------------------------------------------- > > Key: FORGE-1067 > URL: https://issues.jboss.org/browse/FORGE-1067 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Antonio Goncalves > Fix For: 1.x Future > > > At the moment JBoss Forge copies the {{bootstrap.css}} into the resources directory. It would be nice to use WebJar [1] to package Bootstrap (and JQuery) into the war file. > For this to happen you just need to add the following Maven dependencies to the {{pom.xml}} : > {code} > <dependency> > <groupId>org.webjars</groupId> > <artifactId>bootstrap</artifactId> > <version>2.3.2</version> > </dependency> > <dependency> > <groupId>org.webjars</groupId> > <artifactId>jquery</artifactId> > <version>2.0.3</version> > </dependency> > {code} > Then, change the {{pageTemplate.xhtml}} so it looks like this : > {code} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title> > <link rel="icon" href="#{resource['favicon.ico']}"/> > <h:outputStylesheet library="webjars/bootstrap/2.3.2/css" name="bootstrap.min.css"/> > <h:outputStylesheet name="forge-style.css"/> > </h:head> > <h:body> > ... > ... > ... >  >  > <h:outputScript name="webjars/jquery/2.0.3/jquery.min.js"/> > <h:outputScript library="webjars/bootstrap/2.3.2/js" name="bootstrap.min.js"/> > </h:body> > </html> > {code} > And of course, get rid of the {{bootstrap.css}} file ;o) > [1] http://www.webjars.org/ > [1] http://www.jamesward.com/2012/10/31/webjars-officially-launched > See also : https://issues.jboss.org/browse/RF-12584 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1133) Error and exception handling for Maven dependency resolution does not warn of unresolved dependencies

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1133: -------------------------------------- Summary: Error and exception handling for Maven dependency resolution does not warn of unresolved dependencies Key: FORGE-1133 URL: https://issues.jboss.org/browse/FORGE-1133 Project: Forge Issue Type: Bug Components: Build Tools - Maven Affects Versions: 1.4.0.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds Maven dependency resolution errors are not caught and handled appropriately, especially during plugin installation. The following behavior is observed when installing the Forge Arquillian plugin in an environment with an invalid Maven central location, like the one described [here|http://books.sonatype.com/nexus-book/reference/maven-sect-single-gro...], but without the mirror: {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/forgetemp161339604102750966] via 'git' ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final] ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] {noformat} It would be better to display warnings or errors and possibly terminate any operations should this occur. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1131) Shell prompt should display the current resource

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1131?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1131. ---------------------------------- Fix Version/s: 2.0.0.Alpha12 (was: 2.0.0.Alpha11) Resolution: Done > Shell prompt should display the current resource > ------------------------------------------------ > > Key: FORGE-1131 > URL: https://issues.jboss.org/browse/FORGE-1131 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Alpha10 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha12 > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-563) Create a class lookup index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-563: ---------------------------------- Assignee: (was: George Gastaldi) > Create a class lookup index > --------------------------- > > Key: FORGE-563 > URL: https://issues.jboss.org/browse/FORGE-563 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > Fix For: 2.x Future > > > We need to support an index of classes and dependencies which contain them. > This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc. > We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-123) AngularJS scaffolding should scaffold @Embedded properties correctly

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-123?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-123. ---------------------------------------- Resolution: Done Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/ff35b84b7c6ffe... > AngularJS scaffolding should scaffold @Embedded properties correctly > -------------------------------------------------------------------- > > Key: FORGEPLUGINS-123 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-123 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Currently {{@Embedded}} properties are treated as a single property and not expanded in the create and edit views; this results in the input text boxes displaying something like [object Object] for an existing embedded property of an entity. > Also, the search results display the JSON representation of the object instead of one or several properties of the object. This needs correction. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013