[JBoss JIRA] (FORGE-601) XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-601?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-601:
----------------------------------
Fix Version/s: 1.2.4.Final
(was: 1.2.3.Final)
> 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.2.4.Final
>
>
> 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
11 years, 8 months
[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-604:
----------------------------------
Fix Version/s: 1.2.4.Final
(was: 1.2.3.Final)
> Add support for Java EE 6 Full Profile
> --------------------------------------
>
> Key: FORGE-604
> URL: https://issues.jboss.org/browse/FORGE-604
> Project: Forge
> Issue Type: Task
> Components: Java EE APIs
> Affects Versions: 1.0.5.Final
> Environment: All
> Reporter: Christopher Volk
> Fix For: 1.2.4.Final
>
>
> Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging.
> The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort.
> I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile.
> This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-)
--
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
11 years, 8 months
[JBoss JIRA] (FORGE-811) MavenPlugin: Add maven plugin
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-811?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-811:
----------------------------------
Fix Version/s: 1.2.4.Final
(was: 1.2.3.Final)
> MavenPlugin: Add maven plugin
> -----------------------------
>
> Key: FORGE-811
> URL: https://issues.jboss.org/browse/FORGE-811
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration
> Affects Versions: 1.2.1.Final
> Reporter: George Gastaldi
> Labels: starter
> Fix For: 1.2.4.Final
>
>
> The MavenPlugin could have a command to add Maven plugins to the current project's pom.xml
> Syntax could be something like:
> {code}
> maven add-plugin groupId:artifactId:version
> {code}
> version is optional and may be prompted if not specified.
--
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
11 years, 8 months