October 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-235) FacesPlugin should optionally prompt to install JSF dependencies from Mojarra/MyFaces into POM for Servlet Containers

by Brian Leathem (Updated) (JIRA)

[ https://issues.jboss.org/browse/FORGE-235?page=com.atlassian.jira.plugin.... ] Brian Leathem updated FORGE-235: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/66 > FacesPlugin should optionally prompt to install JSF dependencies from Mojarra/MyFaces into POM for Servlet Containers > --------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-235 > URL: https://issues.jboss.org/browse/FORGE-235 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Brian Leathem > > Use PrettyFacesFacet as an example: https://github.com/ocpsoft/prettyfaces-forge-plugin/blob/master/src/main/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-235) FacesPlugin should optionally prompt to install JSF dependencies from Mojarra/MyFaces into POM for Servlet Containers

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/FORGE-235?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned FORGE-235: ----------------------------------- Assignee: Brian Leathem > FacesPlugin should optionally prompt to install JSF dependencies from Mojarra/MyFaces into POM for Servlet Containers > --------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-235 > URL: https://issues.jboss.org/browse/FORGE-235 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Brian Leathem > > Use PrettyFacesFacet as an example: https://github.com/ocpsoft/prettyfaces-forge-plugin/blob/master/src/main/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-141) Declare FacesServlet and mapping

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-141?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-141. ------------------------------------ Fix Version/s: 1.0.0.Beta4 Resolution: Done Implemented conditionally by adding a new prompt in "faces setup" -- Also made mapping configuration available via FacesFacet. > Declare FacesServlet and mapping > -------------------------------- > > Key: FORGE-141 > URL: https://issues.jboss.org/browse/FORGE-141 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Reporter: Thomas Heute > Assignee: Brian Leathem > Fix For: 1.0.0.Beta4 > > > The scaffolding for JSF application currently rely on the auto addition of FacesServlet and mapping feature provided in AS6. web.xml doesn't include those definition. > It is automagically done and do not promote Java EE best practice, worse the JBoss PortletBridge relies on the definition of the FacesServlet in web.xml > I would suggest to explicitly add them in web.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by Lincoln Baxter III (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-273: ------------------------------------------ Rodney, if you are still looking for something to do on this - maybe you could try to figure out how to enable ECHO of input when executing a blocking background process from Forge? > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-178) Project.hasAllFacets should accept a collection and a varags overload would also be nice

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-178?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-178. ------------------------------------ Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Beta4 Resolution: Done > Project.hasAllFacets should accept a collection and a varags overload would also be nice > ---------------------------------------------------------------------------------------- > > Key: FORGE-178 > URL: https://issues.jboss.org/browse/FORGE-178 > Project: Forge > Issue Type: Enhancement > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 1.0.0.Beta4 > > > This would also deprecate Project.hasFacet as the varag overload would fit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-143) Create some base classes for plugin development

by Jason Porter (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-143?page=com.atlassian.jira.plugin.... ] Jason Porter commented on FORGE-143: ------------------------------------ If it's part of a facet, that will work too. I haven't read the new docs yet, but Facets need to play a bigger part, maybe putting some of these utilities on the facets makes more sense. Things like current package, creating Java files, common things each plugin would need to do. There's no point in having each plugin copy / paste all the same code to do the same actions. > Create some base classes for plugin development > ----------------------------------------------- > > Key: FORGE-143 > URL: https://issues.jboss.org/browse/FORGE-143 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Priority: Minor > > There are some core actions a plugin that creates Java classes must do, such as get the current package. Actions like this should be on an abstract base class such as JavaSourceCreationPluginBase (maybe something shorter?) which would also implement Plugin (so we don't break existing plugins) that will have these methods baked in so each plugin doesn't end up copying the code from somewhere else. If Java had mixins this would be a perfect fit, alas, it does not and we're stuck with something else. > The class would probably have to have some abstract getter methods that the subclass would have to implement to get common things like the project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-154) Some of the methods from JavaSource that return lists should be Sets

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-154?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-154. ------------------------------------ Assignee: Lincoln Baxter III Resolution: Won't Fix This can't be done since order matters in such collections. Could use LinkedHashSet, but that would be a less explicit API. > Some of the methods from JavaSource that return lists should be Sets > -------------------------------------------------------------------- > > Key: FORGE-154 > URL: https://issues.jboss.org/browse/FORGE-154 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Assignee: Lincoln Baxter III > Priority: Minor > > Methods like getImports(), getMembers(), (getSyntaxErrors() as SyntaxError is currently defined won't work as there's nothing that really sets apart one SyntaxError from another. If it contained a line number in addition to the definition they could be unique) should returns Sets instead of Lists as you should never have more than one occurrence of an item in the collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-143) Create some base classes for plugin development

by Lincoln Baxter III (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-143?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-143: ------------------------------------------ Could you please list out the actions that you think should be provided by base classes in specific? I'm willing to bet that most are already provided by Facets. E.g: JavaSourceFacet can be used to calculate the current package. But we could make that API a bit more powerful depending on what you need. > Create some base classes for plugin development > ----------------------------------------------- > > Key: FORGE-143 > URL: https://issues.jboss.org/browse/FORGE-143 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Priority: Minor > > There are some core actions a plugin that creates Java classes must do, such as get the current package. Actions like this should be on an abstract base class such as JavaSourceCreationPluginBase (maybe something shorter?) which would also implement Plugin (so we don't break existing plugins) that will have these methods baked in so each plugin doesn't end up copying the code from somewhere else. If Java had mixins this would be a perfect fit, alas, it does not and we're stuck with something else. > The class would probably have to have some abstract getter methods that the subclass would have to implement to get common things like the project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SEAMFORGE-351) Support generating artifacts

by Pete Muir (Created) (JIRA)

Support generating artifacts ---------------------------- Key: SEAMFORGE-351 URL: https://issues.jboss.org/browse/SEAMFORGE-351 Project: Forge Issue Type: Feature Request Reporter: Pete Muir As forge can simply read existing projects, make it easy to reuse the library of archetypes we have - just make it easy to run the command :-) This may just be a doc item? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (SEAMFORGE-362) Installing plugin hibernate-tools cause log4j failure due to class loader conflict

by Steve Tarver (Created) (JIRA)

Installing plugin hibernate-tools cause log4j failure due to class loader conflict ---------------------------------------------------------------------------------- Key: SEAMFORGE-362 URL: https://issues.jboss.org/browse/SEAMFORGE-362 Project: Forge Issue Type: Bug Components: Blessed Plugins Affects Versions: 1.0.0.Beta3 Environment: Mac OSX 10.7.2, JDK 1.6.0_26 64bit Reporter: Steve Tarver On a fresh forge install, installed hibernate-tools plugin. Stopped forge. Started forge and saw [starver@makara isd-pkgferry 16:14:16]$ forge log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable to a "org.apache.log4j.spi.Configurator" variable. log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by log4j:ERROR [ModuleClassLoader for Module "org.jboss.forge:main" from local module loader @320cf66b (roots: /Users/starver/dev/forge-1.0.0.Beta3/modules,/Users/starver/.forge/plugins)] whereas object of type log4j:ERROR "org.apache.log4j.xml.DOMConfigurator" was loaded by [ModuleClassLoader for Module "org.jboss.hibernate.forge.hibernate-tools-plugin.dependencies:1.0.0-SNAPSHOT-cd6ef896-c37d-40a3-926f-b1d164a0a129" from local module loader @320cf66b (roots: /Users/starver/dev/forge-1.0.0.Beta3/modules,/Users/starver/.forge/plugins)]. log4j:ERROR Could not instantiate configurator [org.apache.log4j.xml.DOMConfigurator]. log4j:WARN No appenders could be found for logger (org.jboss.weld.Version). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2011