July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1033) Review the path spec for shell file and directory paths on Linux and Windows

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1033?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1033: ----------------------------------- Fix Version/s: 2.x Future > Review the path spec for shell file and directory paths on Linux and Windows > ---------------------------------------------------------------------------- > > Key: FORGE-1033 > URL: https://issues.jboss.org/browse/FORGE-1033 > Project: Forge > Issue Type: Task > Components: UI - Shell > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Coming from the fix for FORGE-93, it is desirable to document the path specification for files and directories in both Linux (and Mac OS X), and Windows. In Linux, {{'/'}} is the only allowed separator, whereas in Windows, both {{'\'}} and {{'/'}} are allowed. > This obviously has an impact on the FSH script compatibility across these OSes. On the other hand, constraining the directory separator to {{'/'}} for Windows, to achieve commonality would probably work against usability as well as result in unusable paths in Windows. > Discuss. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-601) XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-601?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-601: ------------------------------------- Fix Version/s: 2.x Future > XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs) > ------------------------------------------------------------------------------- > > Key: FORGE-601 > URL: https://issues.jboss.org/browse/FORGE-601 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.5.Final > Environment: Fedora 15 (64-bit), Java 1.7 > Reporter: Ryan Bradley > Fix For: 1.x Future, 2.x Future > > > In my plugin, I use Apache Tiles, which require a reference to a DTD in their layouts/views XML declaration files. I am trying to create these files from a template, and then add more view/layout definitions later in the plugin's workflow. > However, depending on how the DTD reference (in the format <!....>) is added, it is either omitted from the generated file or causes an exception when the XML Parser tries to parse the file for the root node. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] Lennart Jörelid edited comment on FORGE-1031 at 7/22/13 1:35 PM: ----------------------------------------------------------------- No need to apologize, Lincoln. :) Forge is a fine concept and piece of software, with the occasional hiccup ... as most pieces of software have. This issue is merely posted as a reminder for us all. was (Author: lennartj): No need to apologize, Lincoln. :) Forge is a fine piece concept and piece of software, with the occasional hiccup ... as most pieces of software have. This issue is merely a reminder for us all. > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Components: Documentation > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > Fix For: 1.x Future > > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] Lennart Jörelid commented on FORGE-1031: ---------------------------------------- No need to apologize, Lincoln. :) Forge is a fine piece concept and piece of software, with the occasional hiccup ... as most pieces of software have. This issue is merely a reminder for us all. > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Components: Documentation > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > Fix For: 1.x Future > > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1031: -------------------------------------- Fix Version/s: 1.x Future > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Components: Documentation > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > Fix For: 1.x Future > > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1031: ------------------------------------------- Actually this isn't the case. Though looking at our docs, it's also not very clear. The Maven Version is actually completely irrelevant, and is only used in creating the directory structure within forge itself. You do not need to do any maven release of your plugin, since Forge builds it all locally anyway, thus, whether you release or not, it doesn't make a difference. You can leave your plugin as 0.0.1-SNAPSHOT for as long as you like, and as long as you keep updating the branch/tag names to match the version of Forge that that particular branch/tag supports, you'll be fine. To summarize. Releasing your plugin has zero effect. Sorry again for the confusion. And THANK YOU for raising these issues formally so that we can make sure they get addressed. ~Lincoln > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Components: Documentation, Plugin API, Plugin Repository > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1031: -------------------------------------- Component/s: (was: Plugin Repository) (was: Plugin API) > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Components: Documentation > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1032) Create an XMLFileResource as part of an parser-xml addon.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1032?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1032: ---------------------------------------- What about 1.x ? Would that be interesting to have ? > Create an XMLFileResource as part of an parser-xml addon. > --------------------------------------------------------- > > Key: FORGE-1032 > URL: https://issues.jboss.org/browse/FORGE-1032 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha6 > Reporter: Lincoln Baxter III > Priority: Minor > Labels: starter > Fix For: 2.x Future > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1032) Create an XMLFileResource as part of an parser-xml addon.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1032: ----------------------------------------- Summary: Create an XMLFileResource as part of an parser-xml addon. Key: FORGE-1032 URL: https://issues.jboss.org/browse/FORGE-1032 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.0.0.Alpha6 Reporter: Lincoln Baxter III Priority: Minor Fix For: 2.x Future -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lennart Jörelid updated FORGE-1011: ----------------------------------- Affects Version/s: 1.3.3.Final > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final, 1.3.3.Final > Reporter: Lennart Jörelid > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 issue). -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013