March 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-364) Allow Plugins to Reference Facets from other Plugins

by Lincoln Baxter III (Created) (JIRA)

Allow Plugins to Reference Facets from other Plugins ---------------------------------------------------- Key: FORGE-364 URL: https://issues.jboss.org/browse/FORGE-364 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Currently, it is impossible to reference Facets defined in a separate plugin, due to Modularity constraints. We need a way to expose this information between plugins. -- 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

11 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-289) Scan plugins for potential problematic dependencies

by Paul Bakker (JIRA)

Scan plugins for potential problematic dependencies --------------------------------------------------- Key: SEAMFORGE-289 URL: https://issues.jboss.org/browse/SEAMFORGE-289 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Reporter: Paul Bakker Due to JBM some dependencies can brake Forge. Most problems have to do with the way Weld currently works. If a class is reimported that is used by the core Weld sees two classes for a injection point. If the cdi api is imported as a compile scoped dependency, this will brake injection in the plugin all together. Forge should scan for these kind of dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-298) Field/Entity plugins should warn when using potential SQL tokens an entity names or field names

by Lincoln Baxter III (JIRA)

Field/Entity plugins should warn when using potential SQL tokens an entity names or field names ----------------------------------------------------------------------------------------------- Key: SEAMFORGE-298 URL: https://issues.jboss.org/browse/SEAMFORGE-298 Project: Seam Forge Issue Type: Enhancement Components: Builtin Plugins, Java EE APIs Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III It's currently possible to easily create an entity or field that will break JPA because of usage of SQL reserved words. E.g: "order" or "limit" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-300) Usage: dark blue on black background?

by Martin Dames (JIRA)

Usage: dark blue on black background? ------------------------------------- Key: SEAMFORGE-300 URL: https://issues.jboss.org/browse/SEAMFORGE-300 Project: Seam Forge Issue Type: Bug Affects Versions: 1.0.0.Beta2 Environment: Windows 7 Reporter: Martin Dames Priority: Minor Hi, im trying Seam Forge 1.0.0Beta2 on my windows machine and it really makes no fun. I can rarely see the "holding" text and its driving me crazy... I tried to change the cmd shell background and text colors.. but besides this is not a task a normal user should do... this does not work. So, please change your colors a little bit more exe friendly! :) I would add a screenshot if I could.... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
14
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-323) add-constraint is missing NotEmpty

by Pete Muir (JIRA)

add-constraint is missing NotEmpty ---------------------------------- Key: SEAMFORGE-323 URL: https://issues.jboss.org/browse/SEAMFORGE-323 Project: Seam Forge Issue Type: Bug Components: Builtin Plugins Reporter: Pete Muir -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-280) Add ability to generate Entity Query classes with Persistence plugin (using Named Queries)

by Jason Porter (JIRA)

Add ability to generate Entity Query classes with Persistence plugin (using Named Queries) ------------------------------------------------------------------------------------------ Key: SEAMFORGE-280 URL: https://issues.jboss.org/browse/SEAMFORGE-280 Project: Seam Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Beta1 Reporter: Jason Porter -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-331) Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet)

by Lincoln Baxter III (JIRA)

Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet) ------------------------------------------------------------------------------ Key: SEAMFORGE-331 URL: https://issues.jboss.org/browse/SEAMFORGE-331 Project: Seam Forge Issue Type: Enhancement Components: Maven Integration Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Priority: Minor {code} MavenPluginFacet mavenPluginFacet = getProject().getFacet(MavenPluginFacet.class); int nrOfPlugins = getNumberOfPlugins(); MavenPluginBuilder plugin = MavenPluginBuilder.create() .setDependency( DependencyBuilder.create() .setGroupId("org.apache.maven.plugins") .setArtifactId("maven-site-plugin") .setVersion("3.0") ); MavenPluginAdapter mvnPlugin = new MavenPluginAdapter(plugin); MavenCoreFacet facet = project.getFacet(MavenCoreFacet.class); Profile profile = new Profile(); profile.setId(profileId); profile.getBuild().addPlugin(theplugin); Model pom = facet.getPOM(); pom.addProfile(profile); facet.setPOM(pom); {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
5
0 / 0

[JBoss JIRA] (SEAMFORGE-352) Create means for measuring usage

by Rodney Russ (Created) (JIRA)

Create means for measuring usage -------------------------------- Key: SEAMFORGE-352 URL: https://issues.jboss.org/browse/SEAMFORGE-352 Project: Forge Issue Type: Feature Request Components: Shell Reporter: Rodney Russ JBoss Tools has a mechanism built in to gather statistics on usage. This provides good information on how decisions affect our existing user base as well as how to prioritize platforms to support. Having this capability will help in planning later releases with real data and not guesses. -- 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

11 years, 5 months

3
14
0 / 0

[JBoss JIRA] (FORGE-360) FacesPlugin should automatically add the faces mapping if the servlet version < 3

by Brian Leathem (Created) (JIRA)

FacesPlugin should automatically add the faces mapping if the servlet version < 3 --------------------------------------------------------------------------------- Key: FORGE-360 URL: https://issues.jboss.org/browse/FORGE-360 Project: Forge Issue Type: Enhancement Affects Versions: 1.0.0.Beta3 Reporter: Brian Leathem Assignee: Brian Leathem -- 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

11 years, 5 months

4
6
0 / 0

[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected

by Dan Allen (Created) (JIRA)

Current directory is poor default for new-project location when existing project is detected -------------------------------------------------------------------------------------------- Key: FORGE-385 URL: https://issues.jboss.org/browse/FORGE-385 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Beta3 Reporter: Dan Allen Assignee: Lincoln Baxter III Priority: Minor When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found. {code} $ new-project --named example --topLevelPackage org.example ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. Where would you like to create the project? [Press ENTER to use the current directory: dallen] {code} This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories. A better default is to append a number to the end of the project name. For example: {code} $ new-project --named example --topLevelPackage org.example ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. Where would you like to create the project? [Press ENTER to use an alternative directory: example2] {code} -- 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

11 years, 5 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2012