March 2011 - forge-dev - Jboss List Archives

by Paul Bakker

Hi all, I'm working on a feature in the Arquillian plugin that Dan asked about, which is to be able to export @Deployments that are part of the project's tests. To do this I need to invoke the static method on a test class to create the Archive that has to be exported. The problem is that is seems to be impossible to load a class that is in the user's project, although I already have an instance of the JavaSource object that describes the class. I believe it would be best to not rely on the question if the user's project has been compiled or not. So what should happen is the following: -Compile the class based on the JavaSource object -(optionally) Create a temporarily .class object -Load the class -(optionally) instantiate it I guess this is something that other plugins might need too in the future, so it would be better to find a reusable solution instead of hacking my way around it. Paul

13 years, 1 month

4
9
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-103) Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-103?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-103. ---------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Alpha3 Resolution: Won't Fix Forge resolves artifacts from Maven repositories. Since Final is not in a public maven repo yet, it will not show up in the list of options. This will function once Final is released to JBoss Nexus Public. Forge does not use artifacts bundled with the Seam Dist release. (But could with some significant tweaking, and if the dist was structured like a maven repo.) > Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. > --------------------------------------------------------------------------------------------------------------------------- > > Key: SEAMFORGE-103 > URL: https://issues.jboss.org/browse/SEAMFORGE-103 > Project: Seam Forge > Issue Type: Bug > Affects Versions: 1.0.0.Alpha2 > Reporter: Marek Schmidt > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 1.0.0.Alpha3 > > > The version of Seam Forge in the 3.0.0.Final distribution generates project that depend on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Beta4. > It should generate projects depending on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Final. > Note that the package org.jboss.seam.persistence.transaction has been moved to org.jboss.seam.transaction, so the generated code and beans.xml needs to be changed as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-107) delete associated methods when deleting a field

by Rodney Russ (JIRA)

delete associated methods when deleting a field ----------------------------------------------- Key: SEAMFORGE-107 URL: https://issues.jboss.org/browse/SEAMFORGE-107 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming, Builtin Plugins Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 Reporter: Rodney Russ Priority: Minor When removing a field, it would make sense to remove the associated methods. For example: cd Person.java rm firstName *delete associated methods setFirstName() and getFirstName() (Y/n)? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-105) Refactory.createGetterAndSetter should create getFirstName method, instead of getFirstname for a field named firstName

by Marek Schmidt (JIRA)

Refactory.createGetterAndSetter should create getFirstName method, instead of getFirstname for a field named firstName ---------------------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-105 URL: https://issues.jboss.org/browse/SEAMFORGE-105 Project: Seam Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.0.0.Alpha2 Reporter: Marek Schmidt Priority: Minor new-field string --fieldName firstName generates getFirstname and setFirstname methods It should create getFirstName and setFirstName methods instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] Updated: (SEAMFORGE-103) Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-103?page=com.atlassian.jira.plu... ] Lincoln Baxter III updated SEAMFORGE-103: ----------------------------------------- Summary: Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. (was: Seam Solder from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final.) This is problematic, because depending on which version of Seam Persistence the user selects, a different class-name/package needs to be used. Ideas on how to solve this (up to and including classloading the persistence jar itself,) are welcome. Thanks. > Seam Forge from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. > --------------------------------------------------------------------------------------------------------------------------- > > Key: SEAMFORGE-103 > URL: https://issues.jboss.org/browse/SEAMFORGE-103 > Project: Seam Forge > Issue Type: Bug > Affects Versions: 1.0.0.Alpha2 > Reporter: Marek Schmidt > Priority: Critical > > The version of Seam Forge in the 3.0.0.Final distribution generates project that depend on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Beta4. > It should generate projects depending on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Final. > Note that the package org.jboss.seam.persistence.transaction has been moved to org.jboss.seam.transaction, so the generated code and beans.xml needs to be changed as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-106) Conflict in plexus classes causes new-project to fail

by Lincoln Baxter III (JIRA)

Conflict in plexus classes causes new-project to fail ----------------------------------------------------- Key: SEAMFORGE-106 URL: https://issues.jboss.org/browse/SEAMFORGE-106 Project: Seam Forge Issue Type: Bug Components: Builtin Plugins Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Alpha3 [no project] bin $ cd ../.. [no project] forge $ mkdir workspace [no project] forge $ cd workspace [no project] workspace $ new-project [named=The name of the new project (of type java.lang.String)]: foo [topLevelPackage=The top level package for your Java source files [e.g: "com.example.project"] (of type java.lang.String)]: org.foo Use [/Users/koen/Temp/forge/workspace/foo] as project directory? [Y/n] Y ***ERROR*** [new-project] WELD-000049 Unable to invoke [method] @PostConstruct public org.jboss.seam.forge.project.facets.builtin.MavenContainer.bootstrapMaven() on org.jboss.seam.forge.project.facets.builtin.MavenContainer@7fa5f230 [no project] workspace $ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-50) Forge default scaffold (metawidget) is not properly configured (id and version fields show up)

by Lincoln Baxter III (JIRA)

Forge default scaffold (metawidget) is not properly configured (id and version fields show up) ---------------------------------------------------------------------------------------------- Key: SEAMFORGE-50 URL: https://issues.jboss.org/browse/SEAMFORGE-50 Project: Seam Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III The lack of a metawidget.xml to tell Metawidget to use JPA means the 'id' and 'version' fields appear in the UI, which looks bad. Also could use a little more UI "spice" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
5
0 / 0

[JBoss JIRA] Moved: (SEAMFORGE-103) Seam Solder from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final.

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-103?page=com.atlassian.jira.plu... ] Shane Bryzak moved SEAM-70 to SEAMFORGE-103: -------------------------------------------- Project: Seam Forge (was: Seam 3 Distribution) Key: SEAMFORGE-103 (was: SEAM-70) Affects Version/s: 1.0.0.Alpha2 (was: 3.0.0.Final) Fix Version/s: (was: Future) > Seam Solder from the seam final distribution creates projects that depend on seam-persistence 3.0.0.Beta4, instead of Final. > ---------------------------------------------------------------------------------------------------------------------------- > > Key: SEAMFORGE-103 > URL: https://issues.jboss.org/browse/SEAMFORGE-103 > Project: Seam Forge > Issue Type: Bug > Affects Versions: 1.0.0.Alpha2 > Reporter: Marek Schmidt > Priority: Critical > > The version of Seam Forge in the 3.0.0.Final distribution generates project that depend on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Beta4. > It should generate projects depending on org.jboss.seam.persistence:seam-persistence-impl:3.0.0.Final. > Note that the package org.jboss.seam.persistence.transaction has been moved to org.jboss.seam.transaction, so the generated code and beans.xml needs to be changed as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

Re: [forge-dev] Fw: Re: Mojavelinux.com Feedback: seam-gen and cdi/weld

by Lincoln Baxter, III

Hi John, I'm sorry for getting back to you in such horribly late fashion. Your email was unfortunately buried in a mass of others. I *really* want to get database reverse-engineering working, and in fact, such an effort had been started by Max Andersen but abandoned because he didn't have time to get it finished up. The forge API has improved since then, so it should be easier, but his work probably needs to be updated at this point: https://github.com/maxandersen/forge/tree/htools Max, if John is interested, would you be willing to give him a brief overview of what has been done, and what still needs to be done? He could at least try it out, see what works and what doesn't, and maybe even pull out what you've done into a standalone plugin: See plugin writing guide: http://docs.jboss.org/forge/snapshot/reference/en-US/html_single/#forge.p... Let me know. I would be more than happy to work with you on this! Lincoln On Thu, Mar 17, 2011 at 8:57 PM, John du Clos <duclosjj(a)yahoo.com> wrote: > Hi Lincoln- > > I was chatting with Dan Allen and he mentioned you are working on Forge and > specifically the reverse engineering feature from the database. I wanted to > reach out to you to see if you have any early versions you need testers to > help you verify this feature. > I look forward to hearing from you! > John > > --- On *Wed, 3/16/11, Dan Allen <dan.j.allen(a)gmail.com>* wrote: > > > From: Dan Allen <dan.j.allen(a)gmail.com> > Subject: Re: Mojavelinux.com Feedback: seam-gen and cdi/weld > To: duclosjj(a)yahoo.com > Date: Wednesday, March 16, 2011, 9:33 PM > > Hey John, > Thanks for reading the book. I'm glad it helped you along. I know about > those painful days of J2EE you are talking about. > The best way to get started atm is using the Maven archetype. > http://tinyurl.com/gojavaee > That gives you a starter project. We don't yet have the reverse engineering > yet for this environment. That what Forge will offer soon. Check out the > issue tracker or mailing list for updates. > Hope that gets you started. Cheers, > - Dan Allen > Sent from my Android-powered phone: > An open platform for carriers, consumers and developers > On Mar 16, 2011 9:04 PM, <duclosjj(a)yahoo.com<http://us.mc308.mail.yahoo.com/mc/compose?to=duclosjj@yahoo.com>> > wrote: > > Submitted by: John duClos <duclosjj(a)yahoo.com<http://us.mc308.mail.yahoo.com/mc/compose?to=duclosjj@yahoo.com>> > on Wednesday, March 16th, 2011 @ 9:04:25 pm (-0400) > > > > Online Form Fields > > ------------------ > > > > Url: > > > > > > Message: > > Dan- > > > > I purchased your Seam book when it was published and am a supporter of > > the Seam framework since I lived the challenging days of early J2EE > > development. > > > > I work with database centric solutions and seam-gen allowed me to > > develop solutions in record time by getting my project started very > > quickly. I'd like to start implementing JEE 6/CDI with JBoss AS 6, but > > I can't seem to find a way to issue the seam-gen command. > > > > I looked at Forge but that is not where seam-gem was. Do you know of a > > valid seam-gen solution for JEE 6/CDI based projects (Seam 3). > > > > Thanks, > > John > > > > Client Variables > > ---------------- > > > > HTTP_USER_AGENT: > > Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; > .NET CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; MDDS; .NET CLR > 3.0.30729; MS-RTC LM 8; AskTB5.4) > > > > > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-98) Bind <tab> functionality to other keys

by Paul Bakker (JIRA)

Bind <tab> functionality to other keys -------------------------------------- Key: SEAMFORGE-98 URL: https://issues.jboss.org/browse/SEAMFORGE-98 Project: Seam Forge Issue Type: Feature Request Components: Shell Reporter: Paul Bakker During development I like to run forge from the IDE because if gives debugging and JRebel support. The only problem is that <tab> is not working. If the tab completion could also be bound to another key-combo (ctr-space for example) it would probably work as normal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev March 2011