September 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] George Gastaldi commented on FORGEPLUGINS-171: ---------------------------------------------- That seems odd. Try forcing installation of the ResourcesFacet to see if that works for you. > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by Maxime Gréau (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] Maxime Gréau commented on FORGEPLUGINS-171: ------------------------------------------- I don't think so because on the first step, the example_manual.ftl is copied to src/main/asciidoc and I used the ResourceFacet to do it and it works, so the folders src/main/resources and src/main/asciidoc are created. WDYT? > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] George Gastaldi commented on FORGEPLUGINS-171: ---------------------------------------------- Probably because the src/main/resources folder doesn't exist? > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by Maxime Gréau (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] Maxime Gréau commented on FORGEPLUGINS-171: ------------------------------------------- Cool :) No not yet, I will take a look this weekend. It works well for me with 2.8.1.Final I will add some tests too. I've problem for installing GemFacet when the useAsciidoctorDiagram is set : ERROR : ResourcesFacet not found Any idea ? > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

2
1
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] Lincoln Baxter III commented on FORGEPLUGINS-171: ------------------------------------------------- This is excellent! Great idea for an addon! Do we know what the issue is here? > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2000) JavaEEDefaultProvider references inexistent scripts when JPA 2.1 is used

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2000?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2000. ---------------------------------- Fix Version/s: (was: 2.8.2.Final) Resolution: Rejected They are created once the AS starts and as per the spec: {quote} _javax.persistence.schema-generation.scripts.create-target_, _javax.persistence.schema-generation.scripts.drop-target_ If scripts are to be generated,the target locations for the writing of these scripts must be specified. These targets are specified as strings corresponding to file URLs. {quote} > JavaEEDefaultProvider references inexistent scripts when JPA 2.1 is used > ------------------------------------------------------------------------ > > Key: FORGE-2000 > URL: https://issues.jboss.org/browse/FORGE-2000 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.8.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > > When JPA 2.1 is selected, the following properties are created: > {code} > <property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/> > <property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/> > <property name="javax.persistence.schema-generation.scripts.create-target" value="projectCreate.ddl"/> > <property name="javax.persistence.schema-generation.scripts.drop-target" value="projectDrop.ddl"/> > {code} > However, the projectCreate.ddl and projectDrop.ddl file are not created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2000) JavaEEDefaultProvider references inexistent scripts when JPA 2.1 is used

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2000: -------------------------------------- Summary: JavaEEDefaultProvider references inexistent scripts when JPA 2.1 is used Key: FORGE-2000 URL: https://issues.jboss.org/browse/FORGE-2000 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.8.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.8.2.Final When JPA 2.1 is selected, the following properties are created: {code} <property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/> <property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/> <property name="javax.persistence.schema-generation.scripts.create-target" value="projectCreate.ddl"/> <property name="javax.persistence.schema-generation.scripts.drop-target" value="projectDrop.ddl"/> {code} However, the projectCreate.ddl and projectDrop.ddl file are not created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1610) Introduce an Update addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1610?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1610: ---------------------------------------- Hi Ivan, glad you're ready with this! Let's get these questions answered: 1) To show a confirmation dialog/question in Forge UI/Shell, you need to use the {{UIPrompt}} object, supplied by the {{UIExecutionContext}}. The code should be similar to this: {code} public class MyCommand implements UICommand { ... public Result execute(UIExecutionContext context) throws Exception { UIPrompt prompt = context.getPrompt(); boolean answer = prompt.promptBoolean("Do you want to continue?"); return Results.success("You answered: "+answer); } } {code} 2) I think it would be better to have that in a command, since users can ask for update anytime inside the Forge shell (and not only during boot, if the code were in Bootstrap) 3) To test this, I'd recommend to use a controlled Maven environment, like we do in https://github.com/forge/furnace/blob/master/manager/tests/src/test/java/.... Let me know if you need anything else. Best Regards, George Gastaldi > Introduce an Update addon > ------------------------- > > Key: FORGE-1610 > URL: https://issues.jboss.org/browse/FORGE-1610 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Usability > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Ivan St. Ivanov > Fix For: 2.x Future > > > It would be nice to have an Update addon to allow update of addons and the Forge version itself. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1610) Introduce an Update addon

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-1610?page=com.atlassian.jira.plugin... ] Ivan St. Ivanov commented on FORGE-1610: ---------------------------------------- OK, I am pretty ready with this. I have the following questions: 1) How can I show confirmation dialog/question in Forge UI/shell? The Bootstrap example does not use the Shell API 2) Maybe the checks in the third comment should go to the Bootstrap class and not to the Update command (i.e. the Addons addon)? 3) Can I somehow test this? For example setup a furnace container with version 2.6.0 for example and run the update command? Thanks! > Introduce an Update addon > ------------------------- > > Key: FORGE-1610 > URL: https://issues.jboss.org/browse/FORGE-1610 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Usability > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Ivan St. Ivanov > Fix For: 2.x Future > > > It would be nice to have an Update addon to allow update of addons and the Forge version itself. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] George Gastaldi commented on FORGEPLUGINS-171: ---------------------------------------------- For some reason, the plugin version is not being added to the pom.xml in 2.8.2-SNAPSHOT. > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2014