November 2012 - forge-issues - Jboss List Archives

[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] (FORGE-179) The 'open' and 'edit' commands should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-179?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-179: ---------------------------------- Fix Version/s: 1.1.3.Final (was: 1.1.2.Final) > The 'open' and 'edit' commands should be configurable > ----------------------------------------------------- > > Key: FORGE-179 > URL: https://issues.jboss.org/browse/FORGE-179 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Labels: Starter > Fix For: 1.1.3.Final > > > 'open' and 'edit' currently use the default system application, but if hooks were provided into this system, they could instead be used to open files using a user-specified application, or even trigger editors to open in JBoss Tools. > Koen, I am asigning this to you because I want your feedback here. If running forge in eclipse, these commands should probably be a no-op, and your eclipse system will simply intercept the output and open/edit the desired file, yes? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-340: ---------------------------------- Fix Version/s: 1.1.3.Final (was: 1.1.2.Final) > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Labels: Starter > Fix For: 1.1.3.Final > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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, 5 months

1
0
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-233) Allow user to specify a custom Eclipse formatting profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-233?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-233: ---------------------------------- Fix Version/s: 1.1.3.Final (was: 1.1.2.Final) > Allow user to specify a custom Eclipse formatting profile > --------------------------------------------------------- > > Key: FORGE-233 > URL: https://issues.jboss.org/browse/FORGE-233 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.0.0.Alpha3 > Reporter: Dan Allen > Labels: Starter > Fix For: 1.1.3.Final > > > Allow the user to specify an Eclipse formatting profile in the local configuration (~/.forge). When creating (or updating) Java files, use the Eclipse formatter (or alternative) to format the code using the formatting profile. -- 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, 5 months

1
0
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

[JBoss JIRA] (FORGE-436) JavaSource needs a way to parse nested annotations

by Richard Kennard (JIRA)

Richard Kennard created FORGE-436: ------------------------------------- Summary: JavaSource needs a way to parse nested annotations Key: FORGE-436 URL: https://issues.jboss.org/browse/FORGE-436 Project: Forge Issue Type: Feature Request Reporter: Richard Kennard Currently, if presented with a Java file like this: public class MockAnnotatedMethod { @MockAnnotation( anAnnotation = @AnotherMockAnnotation(43)), public MockAnnotatedMethod() { } } JavaSource can easily parse @MockAnnotation into org.jboss.forge.parser.java.Annotation. But then calling... annotationSource.getLiteralValue("anAnnotation") ...results in the String... "@AnotherMockAnnotation(43)" There doesn't appear to be a good way to parse this String into another org.jboss.forge.parser.java.Annotation, complete with initializing its value to be '43'. This is needed for Metawidget. Metawidget's inspectors can be written to inspect arbitrary metadata. It is feasible (though not currently required) that someone might want to parse: @AttributeOverride( name = "name", column = @Column( name = "name", nullable = false ) ) public class Person { ... } This is a JPA annotation that makes the 'name' field a 'required' field, but to do so it uses nested annotations. -- 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-464) Create Debian/Ubuntu package for Forge

by Dan Allen (JIRA)

Dan Allen created FORGE-464: ------------------------------- Summary: Create Debian/Ubuntu package for Forge Key: FORGE-464 URL: https://issues.jboss.org/browse/FORGE-464 Project: Forge Issue Type: Feature Request Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Dan Allen This issue should act as an umbrella for this project. Use related issues to track the steps. Creating and publishing Forge packages for Debian & Ubuntu would really help boost adoption of Forge, IMO. Telling someone to download an unzip seems simple enough, but there's just something even more elegant about: sudo apt-get install jboss-forge (no sudo if you're hip enough, one of those GUIs if your glitzy enough) Debian provides guidelines for new package maintainers [1]. [1] http://www.debian.org/doc/manuals/maint-guide/ -- 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-463) Create Fedora package for Forge

by Dan Allen (JIRA)

Dan Allen created FORGE-463: ------------------------------- Summary: Create Fedora package for Forge Key: FORGE-463 URL: https://issues.jboss.org/browse/FORGE-463 Project: Forge Issue Type: Feature Request Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Dan Allen This is an umbrella issue for creating a Fedora package for Forge. Track steps using additional issues. Creating and publishing Forge packages for Fedora would really help boost adoption of Forge, IMO. Telling someone to download an unzip seems simple enough, but there's just something even more elegant about: sudo yum install jboss-forge (no sudo if you're hip enough, one of those GUIs if your glitzy enough) I discovered that Fedora is trying to make package development easier than ever for Java developers. They've created a plugin for Eclipse [1] that walks you through creating a package, starting from git clone all the way to publish to Bodhi [2] (think of it like Nexus for Fedora, sort of). This effort relates to, and my help drive, the JBoss AS 7 on Fedora initiative [3]. [1] http://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide [2] http://fedoraproject.org/wiki/Bodhi [3] http://fedoraproject.org/wiki/JBossAS7 -- 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

6
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2012