September 2014 - forge-issues - Jboss List Archives

[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: ------------------------------------------- OK, done. > 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-2011) AddonManager installs old addon versions of existing addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2011?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2011. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.10.1.Final (was: 2.x Future) Resolution: Done > AddonManager installs old addon versions of existing addons > ----------------------------------------------------------- > > Key: FORGE-2011 > URL: https://issues.jboss.org/browse/FORGE-2011 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.10.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.10.1.Final > > > Having an addon that depends on an older addon version makes the installation deploy the old addon versions. > This should not happen, given that the addon that is currently running is newer. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2011) AddonManager installs old addon versions of existing addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2011?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2011: ----------------------------------- Steps to Reproduce: Run: {code} addon-install --coordinate org.jboss.forge.addon:angularjs,2.1.1.Final {code} was: Run: {code} addon-install --coordinate org.jboss.forge.addon:angularjs-addon,2.1.1.Final {code} > AddonManager installs old addon versions of existing addons > ----------------------------------------------------------- > > Key: FORGE-2011 > URL: https://issues.jboss.org/browse/FORGE-2011 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.10.0.Final > Reporter: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > Having an addon that depends on an older addon version makes the installation deploy the old addon versions. > This should not happen, given that the addon that is currently running is newer. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2011) AddonManager installs old addon versions of existing addons

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2011: -------------------------------------- Summary: AddonManager installs old addon versions of existing addons Key: FORGE-2011 URL: https://issues.jboss.org/browse/FORGE-2011 Project: Forge Issue Type: Bug Components: Addon Manager Affects Versions: 2.10.0.Final Reporter: George Gastaldi Priority: Critical Fix For: 2.x Future Having an addon that depends on an older addon version makes the installation deploy the old addon versions. This should not happen, given that the addon that is currently running is newer. -- 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: ---------------------------------------------- The installation succeeded. Can you update the addon to use Forge 2.10.0.Final? > 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: ------------------------------------------- Oups, sorry I had forgotten to push this modification. Could you try again please > 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: ---------------------------------------------- Now I am seeing the following errors while installing it: {code} [SEVERE] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project asciidoctor-forge-addon-impl: Compilation failure: Compilation failure: [SEVERE] /tmp/1410539786321-0/impl/src/main/java/org/jboss/forge/addon/asciidoctor/AsciidoctorGemFacetImpl.java:[52,39] cannot find symbol [SEVERE] symbol: variable ASCIIDOCTOR_DIAGRAM [SEVERE] location: class org.jboss.forge.addon.asciidoctor.AsciidoctorGemFacetImpl [SEVERE] /tmp/1410539786321-0/impl/src/main/java/org/jboss/forge/addon/asciidoctor/AsciidoctorGemFacetImpl.java:[52,74] cannot find symbol [SEVERE] symbol: variable ASCIIDOCTOR_DIAGRAM [SEVERE] location: class org.jboss.forge.addon.asciidoctor.AsciidoctorGemFacetImpl [SEVERE] /tmp/1410539786321-0/impl/src/main/java/org/jboss/forge/addon/asciidoctor/AsciidoctorGemFacetImpl.java:[114,46] cannot find symbol [SEVERE] symbol: variable ASCIIDOCTOR_DIAGRAM [SEVERE] location: class org.jboss.forge.addon.asciidoctor.AsciidoctorGemFacetImpl [SEVERE] -> [Help 1] {code} > 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-2010) Invalid scaffold code generated for byte[] data-type

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2010?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2010: -------------------------------------- Attachment: example.zip > Invalid scaffold code generated for byte[] data-type > ---------------------------------------------------- > > Key: FORGE-2010 > URL: https://issues.jboss.org/browse/FORGE-2010 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Scaffold > Affects Versions: 2.10.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > Attachments: example.zip > > > getBody() returns byte[], but the following code is generated. Project attached. > {code} > byte body = this.example.getBody(); > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2010) Invalid scaffold code generated for byte[] data-type

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2010: ----------------------------------------- Summary: Invalid scaffold code generated for byte[] data-type Key: FORGE-2010 URL: https://issues.jboss.org/browse/FORGE-2010 Project: Forge Issue Type: Bug Components: Builtin Plugins, Scaffold Affects Versions: 2.10.0.Final Reporter: Lincoln Baxter III Fix For: 2.x Future getBody() returns byte[], but the following code is generated. Project attached. {code} byte body = this.example.getBody(); {code} -- 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: ------------------------------------------- Hi, So I've added some tests and fixed bugs. Based on those Maven examples projects https://github.com/asciidoctor/asciidoctor-maven-examples, you can test for HTML5 or PDF examples : * HTML5 output with asciidoctor-diagram ** asciidoctor-setup --converter HTML5 --useAsciidoctorDiagram true --toc left ** build ** open the target/generated-docs/manual.html * PDF output ** asciidoctor-setup --converter PDF --toc left ** build ** open the target/generated-docs/manual.pdf Let me know if it works for you. Thanks > 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