April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-269) Respecting file locking in IDE

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-269?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-269: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Respecting file locking in IDE > ------------------------------ > > Key: FORGE-269 > URL: https://issues.jboss.org/browse/FORGE-269 > Project: Forge > Issue Type: Feature Request > Components: Resources API > Reporter: Koen Aers > Fix For: 2.0.0.Alpha3 > > > - Forge needs to fire events requesting the files/folders to lock > - Forge can lock files as it reads/writes them (on demand) > - If deadlock potential arises, forge could prompt the user to continue anyway, at which point the plugin continues > - in the future, forge could provide a diff to eclipse after performing the operations on the side > see: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2011/forge.20... -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-220) Forge should listen to filesystem changes on the system and publish events for plugins to observe

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-220: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Forge should listen to filesystem changes on the system and publish events for plugins to observe > -------------------------------------------------------------------------------------------------- > > Key: FORGE-220 > URL: https://issues.jboss.org/browse/FORGE-220 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Resources API, UI - Eclipse > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > {code}Event<ResourceCreated> > Event<ResourceModified> > Event<ResourceDeleted>{code} > etc... -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-212) Classload dependencies of current project when performing certain operations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-212?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-212: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Classload dependencies of current project when performing certain operations > ----------------------------------------------------------------------------- > > Key: FORGE-212 > URL: https://issues.jboss.org/browse/FORGE-212 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration, Parsers / File Manipulation, Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: wiktorowski maximilien > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > "Generating crud views for entities located into an external jar is a use case i'd like to see implemented in forge. > In my case i have a model.jar containing my entities and an admin.war generated with seam forge. I'd like to use from-entity to generate scaffolding views in admin.war for the entities located in model.jar" > This means that Forge will need to classload dependencies of the target project in order to perform reflection-based generation. This may also require a reflection-based meta-model such as what was done with Errai/GWT. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-510: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > Fix For: 2.0.0.Alpha3 > > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-379) Add user profiles

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-379?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-379: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Add user profiles > ----------------- > > Key: FORGE-379 > URL: https://issues.jboss.org/browse/FORGE-379 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.0.0.Beta3 > Reporter: Pete Muir > Fix For: 2.0.0.Alpha3 > > > At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does... -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-378: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Add "environments" as a first class construct > --------------------------------------------- > > Key: FORGE-378 > URL: https://issues.jboss.org/browse/FORGE-378 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell, Usability > Reporter: Pete Muir > Fix For: 2.0.0.Alpha3 > > > For example: > {code} > set environment JBOSS_AS7 --version 7.1.0.Final > {code} > Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. > For example, the persistence plugin could read from this, changing > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS7 > {code} > to > {code} > persistence setup > {code} > Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. > Lot's of other places where this could provide better defaulting, or remove the need to ask questions. > This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-479) Implement @CommandScoped to enable Plugin - Facet communication

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-479?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-479: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Implement @CommandScoped to enable Plugin - Facet communication > --------------------------------------------------------------- > > Key: FORGE-479 > URL: https://issues.jboss.org/browse/FORGE-479 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.CR2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > (05:04:44 PM) Lincoln: i want to implement @CommandScoped > (05:04:46 PM) Lincoln: that would be nice > (05:04:49 PM) Lincoln: and not hard to do actually > (05:05:00 PM) Lincoln: actually, is that there? > (05:05:13 PM) Paul Bakker: no > (05:05:17 PM) Paul Bakker: but good idea > (05:05:54 PM) Lincoln: easy to tie into the command execution lifecycle > (05:06:01 PM) Lincoln: would be nice to add extension points there as well > (05:06:04 PM) Lincoln: could be helpful for plugins > (05:06:09 PM) Lincoln: before/after command > (05:06:47 PM) Paul Bakker: yes should really do this, very helpful I think for plugin/facet communication > (05:07:03 PM) Lincoln: yeah that could be a recommended pattern actually > (05:07:11 PM) Lincoln: if it works well > (05:07:21 PM) Paul Bakker: yep -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-440: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > A pom.xml which contains comments loses all of them after Forge operates on it. > ------------------------------------------------------------------------------- > > Key: FORGE-440 > URL: https://issues.jboss.org/browse/FORGE-440 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.0.6.Final > Environment: HEAD > Reporter: Pete Muir > Priority: Critical > Fix For: 2.0.0.Alpha3 > > > Also looses formatting, but this is less of an issue. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-535) Support gradle as a build tool

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-535?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-535: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Support gradle as a build tool > ------------------------------ > > Key: FORGE-535 > URL: https://issues.jboss.org/browse/FORGE-535 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > Much like the current Maven support. It would be nice if Forge could be used to manipulate Gradle projects. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-424) JavaParser does not understand wildcard imports like "javax.persistence.*"

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-424?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-424: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > JavaParser does not understand wildcard imports like "javax.persistence.*" > -------------------------------------------------------------------------- > > Key: FORGE-424 > URL: https://issues.jboss.org/browse/FORGE-424 > Project: Forge > Issue Type: Technical task > Components: Parsers / File Manipulation > Affects Versions: 1.1.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata: > {code}package demo.entities; > import javax.persistence.*; > @Entity > public class Contact implements java.io.Serializable { > @Id > private @GeneratedValue(strategy = GenerationType.AUTO) > @Column(name = "id", updatable = false, nullable = false) > Long id = null; > @Version > private @Column(name = "version") > int version = 0; > public Long getId() { > return this.id; > } > public void setId(final Long id) { > this.id = id; > } > public int getVersion() { > return this.version; > } > public void setVersion(final int version) { > this.version = version; > } > @Override > public boolean equals(Object that) { > if (this == that) { > return true; > } > if (that == null) { > return false; > } > if (getClass() != that.getClass()) { > return false; > } > if (id != null) { > return id.equals(((Contact) that).id); > } > return super.equals(that); > } > @Override > public int hashCode() { > if (id != null) { > return id.hashCode(); > } > return super.hashCode(); > } > private String name; > public String getName() { > return this.name; > } > public void setName(final String name) { > this.name = name; > } > public String toString() { > return "" + name; > } > }{code} -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013