March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1664) Scaffold should generate an application JS and an application CSS

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1664?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1664: ---------------------------------------- It would be nice to have the following empty files when scaffold-setup is run: - {{src/main/webapp/resources/css/app.css}} - {{src/main/webapp/resources/js/app.js}} > Scaffold should generate an application JS and an application CSS > ----------------------------------------------------------------- > > Key: FORGE-1664 > URL: https://issues.jboss.org/browse/FORGE-1664 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 2.x Future > > > This makes it easier to add custom JS and CSS without changing the pageTemplate.xhtml. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1664) Scaffold should generate an application JS and an application CSS

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1664: -------------------------------------- Summary: Scaffold should generate an application JS and an application CSS Key: FORGE-1664 URL: https://issues.jboss.org/browse/FORGE-1664 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.1.1.Final Reporter: George Gastaldi Fix For: 2.x Future This makes it easier to add custom JS and CSS without changing the pageTemplate.xhtml. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1663) Create a multi-project release addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1663: -------------------------------------- Summary: Create a multi-project release addon Key: FORGE-1663 URL: https://issues.jboss.org/browse/FORGE-1663 Project: Forge Issue Type: Task Components: Addon Development Affects Versions: 2.1.1.Final Reporter: George Gastaldi Fix For: 2.x Future The idea is to can collect locations of projects to be released, and edit all the poms with required version changes. The Git addon could be needed -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1613) FileWatcher should handle missing folders after deleting a project root directory.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1613?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1613. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.1.2.Final (was: 2.x Future) Resolution: Done > FileWatcher should handle missing folders after deleting a project root directory. > ---------------------------------------------------------------------------------- > > Key: FORGE-1613 > URL: https://issues.jboss.org/browse/FORGE-1613 > Project: Forge > Issue Type: Feature Request > Components: Resources > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.1.2.Final > > > It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs: > {code} > [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE > {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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1661) project-add-dependency ignore new scope

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1661?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1661: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.1.2.Final (was: 2.x Future) Resolution: Done Thanks > project-add-dependency ignore new scope > --------------------------------------- > > Key: FORGE-1661 > URL: https://issues.jboss.org/browse/FORGE-1661 > Project: Forge > Issue Type: Bug > Components: Projects > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.1.2.Final > > > When you have a bom defined in depmgm that include the dep you're trying to add as a direct dependency, you will get the question: This is a managed resource, would you like to include this version? > When you attempt to add a reference to a managed dependency in a given scope, the new scope is ignored if you say yes to not override the managed version. > Take Arquillian as an example, arquillian-bom is defined in depmgm. > project-add-dependencies org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain::test:pom > Do you like to use managed version? Y > Results in: > org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:::pom > Resolver is now in Compile scope. Wanted Test scope. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1661) project-add-dependency ignore new scope

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1661?page=com.atlassian.jira.plugin... ] Aslak Knutsen updated FORGE-1661: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/403 > project-add-dependency ignore new scope > --------------------------------------- > > Key: FORGE-1661 > URL: https://issues.jboss.org/browse/FORGE-1661 > Project: Forge > Issue Type: Bug > Components: Projects > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.x Future > > > When you have a bom defined in depmgm that include the dep you're trying to add as a direct dependency, you will get the question: This is a managed resource, would you like to include this version? > When you attempt to add a reference to a managed dependency in a given scope, the new scope is ignored if you say yes to not override the managed version. > Take Arquillian as an example, arquillian-bom is defined in depmgm. > project-add-dependencies org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain::test:pom > Do you like to use managed version? Y > Results in: > org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:::pom > Resolver is now in Compile scope. Wanted Test scope. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1662) addon-build-and-install ignores --projectRoot argument

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1662?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1662: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.1.2.Final (was: 2.x Future) Resolution: Done > addon-build-and-install ignores --projectRoot argument > ------------------------------------------------------ > > Key: FORGE-1662 > URL: https://issues.jboss.org/browse/FORGE-1662 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.1.2.Final > > > The command line argument ProjectRoot is completely ignored, and the command always use working directory. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1662) addon-build-and-install ignores --projectRoot argument

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1662?page=com.atlassian.jira.plugin... ] Aslak Knutsen updated FORGE-1662: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/402 > addon-build-and-install ignores --projectRoot argument > ------------------------------------------------------ > > Key: FORGE-1662 > URL: https://issues.jboss.org/browse/FORGE-1662 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.x Future > > > The command line argument ProjectRoot is completely ignored, and the command always use working directory. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1662) addon-build-and-install ignores --projectRoot argument

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1662: ------------------------------------ Summary: addon-build-and-install ignores --projectRoot argument Key: FORGE-1662 URL: https://issues.jboss.org/browse/FORGE-1662 Project: Forge Issue Type: Bug Components: Addon Manager Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 2.x Future The command line argument ProjectRoot is completely ignored, and the command always use working directory. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1461) "project-new" command fails while a ResourceTransaction is active

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1461?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1461: ------------------------------------------- Nice job on this one! > "project-new" command fails while a ResourceTransaction is active > ----------------------------------------------------------------- > > Key: FORGE-1461 > URL: https://issues.jboss.org/browse/FORGE-1461 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Resources > Affects Versions: 2.0.0.CR1 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.1.2.Final > > > {code}[Desktop]$ transaction-start > ***SUCCESS*** Resource Transaction started > [Desktop]$ project-new > --named --topLevelPackage --targetLocation --version > --finalName --buildSystem --type > [Desktop]$ project-new --named example > ***SUCCESS*** Project named 'example' has been created. > Exception when parsing/running: project-new --named example, Current working directory must be a directory > [Desktop]$ > [Desktop]$ > [Desktop]$ ls > pom.xml src > [Desktop]$ cd .. > [Desktop]$ ls > example > [Desktop]$ transaction-commit > [Desktop]$ > {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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014