[JBoss JIRA] (FORGE-2093) Being able to create a new JPA listener
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2093?page=com.atlassian.jira.plugin... ]
Antonio Goncalves reassigned FORGE-2093:
----------------------------------------
Assignee: Antonio Goncalves
> Being able to create a new JPA listener
> ---------------------------------------
>
> Key: FORGE-2093
> URL: https://issues.jboss.org/browse/FORGE-2093
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.12.1.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> It would be good to be able to create a new JPA listener. A basic command could just be :
> {code}
> jpa-new-listener --named MyListener
> {code}
> This will generate the following code :
> {code}
> class MyListener {
> }
> {code}
> Then we would add as many lifecycle events as needed, something like :
> {code}
> jpa-new-listener --named MyListener --lifecycle PRE_PERSIST, POST_UPDATE, POST_REMOVE
> {code}
> {code}
> class MyListener {
> @PrePersist
> private void prePersist(Object object)
> {
> }
> @PostUpdate
> private void postUpdate(Object object)
> {
> }
> @PostRemove
> private void postRemove(Object object)
> {
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2243) Programmatically added maven archetype catalog does not work with new-project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2243?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2243.
----------------------------------
Assignee: George Gastaldi
> Programmatically added maven archetype catalog does not work with new-project
> -----------------------------------------------------------------------------
>
> Key: FORGE-2243
> URL: https://issues.jboss.org/browse/FORGE-2243
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.14.0.Final
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 2.15.0.Final
>
>
> See also FORGE-2242
> When using the new-project command it doesnt work with catalogs that has been added from java code.
> I have added an archetype catalog named "central", eg see FORGE-2242, and when I use it in project-new it fails, as the last output.
> {code}
> [forge-distribution-2.14.0.Final]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> ? Project name: mydemo2
> ? Top level package [org.mydemo2]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/opt/forge-distribution-2.14.0.Final]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Project type: [0-7] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Build system: [0]
> [0] ( ) central
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Catalog: [0]
> ***ERROR*** Catalog must be specified.
> ***ERROR*** Archetype must be specified.
> [forge-distribution-2.14.0.Final]$
> {code}
> But if I add an archetype catalog using archetype-add from the forge shell then it works with project-new, even though they both load the same set of archetypes from maven central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2269) Archetype-list command is displaying duplicate entries
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2269?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2269.
----------------------------------
Resolution: Done
> Archetype-list command is displaying duplicate entries
> ------------------------------------------------------
>
> Key: FORGE-2269
> URL: https://issues.jboss.org/browse/FORGE-2269
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 2.15.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.15.1.Final
>
>
> When you have a class that implements {{ArchetypeCatalogFactory}} and implicitly register another one with the same name using {{org.jboss.forge.addon.maven.archetype.ArchetypeCatalogFactoryRegistry.addArchetypeCatalogFactory(ArchetypeCatalogFactory)}}, the {{archetype-list}} command shows duplicate entries:
> {code}
> [forge-distribution-2.15.0.Final]$ archetype-list
> fabric8 = io.fabric8.forge.camel.commands.project.FabricArchetypeCatalogFactory@bedc1833
> camel = io.fabric8.forge.camel.commands.project.CamelArchetypeCatalogFactory@5a0d4b6
> {code}
> Explicit registration should take precedence on existing services, so it should allow easy overriding of archetype catalog factories.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2269) Archetype-list command is displaying duplicate entries
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2269:
--------------------------------------
Summary: Archetype-list command is displaying duplicate entries
Key: FORGE-2269
URL: https://issues.jboss.org/browse/FORGE-2269
Project: Forge
Issue Type: Bug
Components: Build Tools - Maven
Affects Versions: 2.15.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.15.1.Final
When you have a class that implements {{ArchetypeCatalogFactory}} and implicitly register another one with the same name using {{org.jboss.forge.addon.maven.archetype.ArchetypeCatalogFactoryRegistry.addArchetypeCatalogFactory(ArchetypeCatalogFactory)}}, the {{archetype-list}} command shows duplicate entries:
{code}
[forge-distribution-2.15.0.Final]$ archetype-list
fabric8 = io.fabric8.forge.camel.commands.project.FabricArchetypeCatalogFactory@bedc1833
camel = io.fabric8.forge.camel.commands.project.CamelArchetypeCatalogFactory@5a0d4b6
{code}
Explicit registration should take precedence on existing services, so it should allow easy overriding of archetype catalog factories.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2185) archetype-list - Command has no documentation and lists nothing
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2185?page=com.atlassian.jira.plugin... ]
Claus Ibsen closed FORGE-2185.
------------------------------
Fix Version/s: 2.15.0.Final
Resolution: Done
The man page now have documentation. Thanks
> archetype-list - Command has no documentation and lists nothing
> ---------------------------------------------------------------
>
> Key: FORGE-2185
> URL: https://issues.jboss.org/browse/FORGE-2185
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.13.0.Final
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.15.0.Final
>
>
> In forge 2.13.0 I type
> {code}
> archetype-list
> {code}
> and it prints nothing.
> The man page for this command does not show any documentation what it does, and how to use it.
> {code}
> NAME
> archetype-list -- Maven
> SYNOPSIS
> archetype-list [-]
> DESCRIPTION
> * --named*
> RESOURCES
> forge: <http://forge.jboss.org/>
> COPYING
> Copyright 2015 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}
> Also I wonder as a 3rd party plugin provider, can you install custom archetypes that this command can list?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2243) Programmatically added maven archetype catalog does not work with new-project
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2243?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2243:
------------------------------------
[forge-distribution-2.15.0.Final]$ addon-install --coordinate io.fabric8.forge:camel,2.2-SNAPSHOT
***SUCCESS*** Addon io.fabric8.forge:camel,2.2-SNAPSHOT was installed successfully.
[forge-distribution-2.15.0.Final]$ archetype-list
fabric8 = io.fabric8.forge.camel.commands.project.FabricArchetypeCatalogFactory@bedc1833
camel = io.fabric8.forge.camel.commands.project.CamelArchetypeCatalogFactory@5a0d4b6
[forge-distribution-2.15.0.Final]$ exit
davsclaus:/opt/forge-distribution-2.15.0.Final/$
> Programmatically added maven archetype catalog does not work with new-project
> -----------------------------------------------------------------------------
>
> Key: FORGE-2243
> URL: https://issues.jboss.org/browse/FORGE-2243
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.14.0.Final
> Reporter: Claus Ibsen
> Fix For: 2.15.0.Final
>
>
> See also FORGE-2242
> When using the new-project command it doesnt work with catalogs that has been added from java code.
> I have added an archetype catalog named "central", eg see FORGE-2242, and when I use it in project-new it fails, as the last output.
> {code}
> [forge-distribution-2.14.0.Final]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> ? Project name: mydemo2
> ? Top level package [org.mydemo2]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/opt/forge-distribution-2.14.0.Final]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Project type: [0-7] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Build system: [0]
> [0] ( ) central
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Catalog: [0]
> ***ERROR*** Catalog must be specified.
> ***ERROR*** Archetype must be specified.
> [forge-distribution-2.14.0.Final]$
> {code}
> But if I add an archetype catalog using archetype-add from the forge shell then it works with project-new, even though they both load the same set of archetypes from maven central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2243) Programmatically added maven archetype catalog does not work with new-project
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2243?page=com.atlassian.jira.plugin... ]
Claus Ibsen resolved FORGE-2243.
--------------------------------
Fix Version/s: 2.15.0.Final
(was: 2.x Future)
Resolution: Done
Yay works fine in 2.15.0. The archetype catalog is registered out of the box without any CDI injection.
> Programmatically added maven archetype catalog does not work with new-project
> -----------------------------------------------------------------------------
>
> Key: FORGE-2243
> URL: https://issues.jboss.org/browse/FORGE-2243
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.14.0.Final
> Reporter: Claus Ibsen
> Fix For: 2.15.0.Final
>
>
> See also FORGE-2242
> When using the new-project command it doesnt work with catalogs that has been added from java code.
> I have added an archetype catalog named "central", eg see FORGE-2242, and when I use it in project-new it fails, as the last output.
> {code}
> [forge-distribution-2.14.0.Final]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> ? Project name: mydemo2
> ? Top level package [org.mydemo2]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/opt/forge-distribution-2.14.0.Final]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Project type: [0-7] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Build system: [0]
> [0] ( ) central
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Catalog: [0]
> ***ERROR*** Catalog must be specified.
> ***ERROR*** Archetype must be specified.
> [forge-distribution-2.14.0.Final]$
> {code}
> But if I add an archetype catalog using archetype-add from the forge shell then it works with project-new, even though they both load the same set of archetypes from maven central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2243) Programmatically added maven archetype catalog does not work with new-project
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2243?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2243:
------------------------------------
Okay its better in 2.15.0 now. But they are still listed x2 times
[forge-distribution-2.15.0.Final]$ archetype-list
fabric8 = io.fabric8.forge.camel.commands.project.FabricArchetypeCatalogFactory@bedc1833
camel = io.fabric8.forge.camel.commands.project.CamelArchetypeCatalogFactory@5a0d4b6
camel = io.fabric8.forge.camel.commands.project.CamelArchetypeCatalogFactory@5a0d4b6
fabric8 = io.fabric8.forge.camel.commands.project.FabricArchetypeCatalogFactory@bedc1833
> Programmatically added maven archetype catalog does not work with new-project
> -----------------------------------------------------------------------------
>
> Key: FORGE-2243
> URL: https://issues.jboss.org/browse/FORGE-2243
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.14.0.Final
> Reporter: Claus Ibsen
> Fix For: 2.x Future
>
>
> See also FORGE-2242
> When using the new-project command it doesnt work with catalogs that has been added from java code.
> I have added an archetype catalog named "central", eg see FORGE-2242, and when I use it in project-new it fails, as the last output.
> {code}
> [forge-distribution-2.14.0.Final]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> ? Project name: mydemo2
> ? Top level package [org.mydemo2]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/opt/forge-distribution-2.14.0.Final]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Project type: [0-7] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Build system: [0]
> [0] ( ) central
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Catalog: [0]
> ***ERROR*** Catalog must be specified.
> ***ERROR*** Archetype must be specified.
> [forge-distribution-2.14.0.Final]$
> {code}
> But if I add an archetype catalog using archetype-add from the forge shell then it works with project-new, even though they both load the same set of archetypes from maven central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-2268 at 3/5/15 3:29 PM:
----------------------------------------------------------------
It could be enabled in the CLI provider itself.
If you want to try as an option in camel, you could fetch the {{UIPrompt}} object from the {{UIExecutionContext}} and call the prompt methods as desired in the {{execute(UIExecutionContext)}} method.
was (Author: gastaldi):
It could be enabled in the CLI provider itself.
If you want to try as an option in camel, you could fetch the {{UIPrompt}} object from the {{UIExecutionContext}} and call the prompt methods as desired.
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2268:
----------------------------------------
It could be enabled in the CLI provider itself.
If you want to try as an option in camel, you could fetch the {{UIPrompt}} object from the {{UIExecutionContext}} and call the prompt methods as desired.
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month