October 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2091) Being able to create a new Java exception

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2091: ---------------------------------------- Summary: Being able to create a new Java exception Key: FORGE-2091 URL: https://issues.jboss.org/browse/FORGE-2091 Project: Forge Issue Type: Sub-task Components: Parsers / File Manipulation Affects Versions: 2.12.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future It would be good to have a command to generate a new Java exception. A simple command such as : {code} java-new-exception --named MyException {code} Would generate : {code} public class MyException extends RuntimeException { } {code} Another attribute would allow to extends from whatever exception we want. So something like : {code} java-new-exception --named MyException --inherits MyOtherException {code} {code} public class MyException extends MyOtherException { } {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2035) Forge does not resolve the tilde slash (~/) denoting a user home directory correctly

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-2035?page=com.atlassian.jira.plugin... ] Daniel Cunha commented on FORGE-2035: ------------------------------------- That's ok? If yes, please close. If not, I'll see later. :) > Forge does not resolve the tilde slash (~/) denoting a user home directory correctly > ------------------------------------------------------------------------------------ > > Key: FORGE-2035 > URL: https://issues.jboss.org/browse/FORGE-2035 > Project: Forge > Issue Type: Bug > Reporter: Sande Gilda > Priority: Critical > > When specifying the `~/` (tilde slash) in a path, the Linux "shortcut" to denote a user's home directory, Forge treats it as a character and creates a directory named '' relative to the directory where you run the 'forge' command. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2090) addon-remove to uninstall all versions of addon (given only G:A)

by Ondrej Zizka (JIRA)

Ondrej Zizka created FORGE-2090: ----------------------------------- Summary: addon-remove to uninstall all versions of addon (given only G:A) Key: FORGE-2090 URL: https://issues.jboss.org/browse/FORGE-2090 Project: Forge Issue Type: Feature Request Components: Addon Manager Affects Versions: 2.12.1.Final Reporter: Ondrej Zizka Priority: Minor The addon-remove needs a parameter including version. That's quite annoying and unnecessary - I simply need to uninstall the current addon's version, and typically, right after that, install a new one. Therefore, having an option of uninstalling just by G:A would come handy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2089) addon-reinstall

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2089?page=com.atlassian.jira.plugin... ] Ondrej Zizka updated FORGE-2089: -------------------------------- Affects Version/s: 2.12.1.Final > addon-reinstall > --------------- > > Key: FORGE-2089 > URL: https://issues.jboss.org/browse/FORGE-2089 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > > addon-install would keep the context of addon installation. > addon-reinstall would then reinstall it from the same place. > Example: > addon-install without arguments searches the current directory's project. > it installs org.jboss:foo,1.0 > Then I want to reinstall, the project is alredy 1.1 > So `addon-reinstall org.jboss:foo` will remove the current addon of the same G:A and install it from the same project directory as last time (possibly different than current working dir). This is a bit magical, but that's the way addon-* work anyway. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2089) addon-reinstall

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2089?page=com.atlassian.jira.plugin... ] Ondrej Zizka updated FORGE-2089: -------------------------------- Component/s: Addon Manager > addon-reinstall > --------------- > > Key: FORGE-2089 > URL: https://issues.jboss.org/browse/FORGE-2089 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > > addon-install would keep the context of addon installation. > addon-reinstall would then reinstall it from the same place. > Example: > addon-install without arguments searches the current directory's project. > it installs org.jboss:foo,1.0 > Then I want to reinstall, the project is alredy 1.1 > So `addon-reinstall org.jboss:foo` will remove the current addon of the same G:A and install it from the same project directory as last time (possibly different than current working dir). This is a bit magical, but that's the way addon-* work anyway. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2089) addon-reinstall

by Ondrej Zizka (JIRA)

Ondrej Zizka created FORGE-2089: ----------------------------------- Summary: addon-reinstall Key: FORGE-2089 URL: https://issues.jboss.org/browse/FORGE-2089 Project: Forge Issue Type: Feature Request Reporter: Ondrej Zizka addon-install would keep the context of addon installation. addon-reinstall would then reinstall it from the same place. Example: addon-install without arguments searches the current directory's project. it installs org.jboss:foo,1.0 Then I want to reinstall, the project is alredy 1.1 So `addon-reinstall org.jboss:foo` will remove the current addon of the same G:A and install it from the same project directory as last time (possibly different than current working dir). This is a bit magical, but that's the way addon-* work anyway. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2088) Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2088?page=com.atlassian.jira.plugin... ] Lincoln Baxter III edited comment on FORGE-2088 at 10/22/14 3:19 PM: --------------------------------------------------------------------- the correct command is: 'addons-remove --addons ADDONID ADDONID ADDONID' But the man page synopsis docs show --addons as [optional] when it is not. Brackets should be removed {code}NAME addon-remove -- Forge/Manage SYNOPSIS addon-remove [-] [--addons] AddonId DESCRIPTION Command to remove a Furnace 2 addon. --addons Installed addons - The installed addons in mutable addon repositories that may be removed [AddonId] (required) Valid choices: [] RESOURCES forge: <http://forge.jboss.org/> COPYING Copyright 2014 Red Hat, Inc. and/or its affiliates. Licensed under the Eclipse Public License version 1.0, available at http://www.eclipse.org/legal/epl-v10.html {code} was (Author: lincolnthree): the correct command is: {code}NAME addon-remove -- Forge/Manage SYNOPSIS addon-remove [-] [--addons] AddonId DESCRIPTION Command to remove a Furnace 2 addon. --addons Installed addons - The installed addons in mutable addon repositories that may be removed [AddonId] (required) Valid choices: [] RESOURCES forge: <http://forge.jboss.org/> COPYING Copyright 2014 Red Hat, Inc. and/or its affiliates. Licensed under the Eclipse Public License version 1.0, available at http://www.eclipse.org/legal/epl-v10.html {code} > Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS > --------------------------------------------------------------------------------------------- > > Key: FORGE-2088 > URL: https://issues.jboss.org/browse/FORGE-2088 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > > Not sure if bug or feature, either way - I'd expect that feeding addon-remove an item from addon-list would remove it. Not the case: > $ addon-list > Currently installed addons: > ... > org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ... > [javaee-WLServlet]$ addon-remove org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ***ERROR*** Installed addons must be specified -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2088) addon-remove doesn't work (or counter-intuitive)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2088?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-2088: --------------------------------------- > addon-remove doesn't work (or counter-intuitive) > ------------------------------------------------ > > Key: FORGE-2088 > URL: https://issues.jboss.org/browse/FORGE-2088 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > Assignee: Lincoln Baxter III > > Not sure if bug or feature, either way - I'd expect that feeding addon-remove an item from addon-list would remove it. Not the case: > $ addon-list > Currently installed addons: > ... > org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ... > [javaee-WLServlet]$ addon-remove org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ***ERROR*** Installed addons must be specified -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2088) Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2088?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2088: -------------------------------------- Summary: Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS (was: addon-remove doesn't work (or counter-intuitive)) > Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS > --------------------------------------------------------------------------------------------- > > Key: FORGE-2088 > URL: https://issues.jboss.org/browse/FORGE-2088 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > Assignee: Lincoln Baxter III > > Not sure if bug or feature, either way - I'd expect that feeding addon-remove an item from addon-list would remove it. Not the case: > $ addon-list > Currently installed addons: > ... > org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ... > [javaee-WLServlet]$ addon-remove org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ***ERROR*** Installed addons must be specified -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2088) Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2088?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2088: -------------------------------------- Assignee: (was: Lincoln Baxter III) > Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS > --------------------------------------------------------------------------------------------- > > Key: FORGE-2088 > URL: https://issues.jboss.org/browse/FORGE-2088 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > > Not sure if bug or feature, either way - I'd expect that feeding addon-remove an item from addon-list would remove it. Not the case: > $ addon-list > Currently installed addons: > ... > org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ... > [javaee-WLServlet]$ addon-remove org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ***ERROR*** Installed addons must be specified -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2014