July 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-158) Create a Seam Catch Plugin

by Jason Porter (JIRA)

Create a Seam Catch Plugin -------------------------- Key: SEAMFORGE-158 URL: https://issues.jboss.org/browse/SEAMFORGE-158 Project: Seam Forge Issue Type: Feature Request Reporter: Jason Porter -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-137) Should validate plugin API names to ensure no duplicates occur

by Lincoln Baxter III (JIRA)

Should validate plugin API names to ensure no duplicates occur -------------------------------------------------------------- Key: SEAMFORGE-137 URL: https://issues.jboss.org/browse/SEAMFORGE-137 Project: Seam Forge Issue Type: Feature Request Components: Plugin API, Shell Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta1 Should be invalid for same resource scopes @Alias("whee") @Alias("whee") Should be invalid in same command: @Option(name="named") @Option(name="named") And so on... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-136) Should use the JBoss Modules project for plugin packaging/loading/isolation.

by Lincoln Baxter III (JIRA)

Should use the JBoss Modules project for plugin packaging/loading/isolation. ---------------------------------------------------------------------------- Key: SEAMFORGE-136 URL: https://issues.jboss.org/browse/SEAMFORGE-136 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta1 Investigate use of the JBoss Modules system for plugin packaging, loading, and dependency management. http://relation.to/16904.lace https://github.com/jbossas/jboss-modules http://docs.jboss.org/jbossmodules/latest/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-85) Forge should support dynamic loading of plugin library dependencies

by Lincoln Baxter III (JIRA)

Forge should support dynamic loading of plugin library dependencies ------------------------------------------------------------------- Key: SEAMFORGE-85 URL: https://issues.jboss.org/browse/SEAMFORGE-85 Project: Seam Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III Right now, Forge extensions must use the maven shade-plugin to package referenced dependencies of plugins. It would greatly enhance developer experience if referenced plugins or libraries could be dynamically loaded from the local maven repository, even if built with Git. A META-INF/dependencies file could be used to list runtime dependencies of the plugin. Or the POM files of each plugin (META-INF/pom...) could be scanned and parsed to determine required libs. A third option, programmatic declaration of runtime dependencies might also be an option if it can be worked into Java from Groovy: http://groovy.codehaus.org/Grape Benefits of these approaches are: * Reduced size deliverable ZIPfile * ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-267) org.jboss.forge.parser.java.Parameter should support examining annotations

by Jason Porter (JIRA)

org.jboss.forge.parser.java.Parameter should support examining annotations -------------------------------------------------------------------------- Key: SEAMFORGE-267 URL: https://issues.jboss.org/browse/SEAMFORGE-267 Project: Seam Forge Issue Type: Enhancement Reporter: Jason Porter There is no way to get annotations on a parameter currently without parsing the string. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-266) Implementations of Interfaces should maintain equality with other implementations

by Jason Porter (JIRA)

Implementations of Interfaces should maintain equality with other implementations --------------------------------------------------------------------------------- Key: SEAMFORGE-266 URL: https://issues.jboss.org/browse/SEAMFORGE-266 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha4 Reporter: Jason Porter Until I saw how to create an Import (which I still don't agree with having to be tied to the Implementation) I thought about creating my own implementation for a test (a mock would be even better) so I looked at the equals for the ImportImpl and it does not keep equality with other implementations because it checks to see if the class is the same. It also checks internal state instead of using the interface methods. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-265) Some of the methods from JavaSource that return lists should be Sets

by Jason Porter (JIRA)

Some of the methods from JavaSource that return lists should be Sets -------------------------------------------------------------------- Key: SEAMFORGE-265 URL: https://issues.jboss.org/browse/SEAMFORGE-265 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha4 Reporter: Jason Porter 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-264) Change Strings to take CharacterSequence in classes building java source files

by Jason Porter (JIRA)

Change Strings to take CharacterSequence in classes building java source files ------------------------------------------------------------------------------ Key: SEAMFORGE-264 URL: https://issues.jboss.org/browse/SEAMFORGE-264 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha4 Reporter: Jason Porter Priority: Minor I'm using org.jboss.forge.parser.java.Method right now and noticing everything takes a string. A nice enhancement would be to accept CharacterSequence (http://download.oracle.com/javase/6/docs/api/java/lang/CharSequence.html) instead of String. This has the added bonus of being able to pass a StringBuilder without having to call toString() on it. Other CharacterSequences may also find ease of use with this change. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-262) Create some base classes for plugin development

by Jason Porter (JIRA)

Create some base classes for plugin development ----------------------------------------------- Key: SEAMFORGE-262 URL: https://issues.jboss.org/browse/SEAMFORGE-262 Project: Seam 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-260) Project.hasAllFacets should accept a collection and a varags overload would also be nice

by Jason Porter (JIRA)

Project.hasAllFacets should accept a collection and a varags overload would also be nice ---------------------------------------------------------------------------------------- Key: SEAMFORGE-260 URL: https://issues.jboss.org/browse/SEAMFORGE-260 Project: Seam Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.0.Alpha4 Reporter: Jason Porter Priority: Minor This would also deprecate Project.hasFacet as the varag overload would fit. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev July 2011