April 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Commented: (SEAMFORGE-3) Create project from Maven archetype

by Rodney Russ (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-3?page=com.atlassian.jira.plugi... ] Rodney Russ commented on SEAMFORGE-3: ------------------------------------- Actually, FPak isn't quite a stand-in replacement to mvn archetype:generate. It's an alternative to it that should be a little easier than writing your own plugin. What I've been doing is converting a project generated from archetype:generate to be in a format usable by FPak. > Create project from Maven archetype > ----------------------------------- > > Key: SEAMFORGE-3 > URL: https://issues.jboss.org/browse/SEAMFORGE-3 > Project: Seam Forge > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

Re: [forge-dev] shading!?

by Rodney Russ

How about JBoss Modules? http://relation.to/16904.lace ----- "Paul Bakker" <paul.bakker.nl(a)gmail.com> wrote: > From: "Paul Bakker" <paul.bakker.nl(a)gmail.com> > To: "forge-dev List" <forge-dev(a)lists.jboss.org> > Sent: Monday, April 11, 2011 10:32:19 AM GMT -07:00 US/Canada Mountain > Subject: Re: [forge-dev] shading!? > > The ultimate solution would be to use a completely isolated > classloader for plugins and plugin dependencies so that plugins would > even be able to package different versions of libraries that are also > used by Forge. Running Forge in an OSGi container seems to be the > obvious solution. I'm no OSGi expert though, so I can't really see the > consequences. No idea if Weld still works within OSGi bundles for > example, but it's something to consider. Besides OSGi there's the > module system that's part of AS7, maybe that's another option. > > > Paul > > > On Mon, Apr 11, 2011 at 4:00 PM, Lincoln Baxter, III < > lincolnbaxter(a)gmail.com > wrote: > > > Yeah, shading is currently the recommended approach. Conflicts should > be avoided by using relocations. I know this is... not a great method, > but for now it's all we've got. Open to suggestions. > > ~Lincoln > > > > > > On Mon, Apr 11, 2011 at 3:41 AM, Max Rydahl Andersen < > max.andersen(a)redhat.com > wrote: > > > Heya, > > Lincoln, I just saw your commits to hibernattools plugin at ( > https://github.com/forge/plugin-hibernate-tools/commit/8b208b4a8e79dbb8a0... > ) > > Is shading of jars really the recommended approach for plugins in > Forge ? > > How are you going to share/avoid collisions of libraries across > plugins if they need to bundle via shading ? > > /max > http://about.me/maxandersen > > > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-110) Upgrade org.jboss.spec:jboss-javaee-6.0 to 1.0.0.Final

by Dan Allen (JIRA)

Upgrade org.jboss.spec:jboss-javaee-6.0 to 1.0.0.Final ------------------------------------------------------ Key: SEAMFORGE-110 URL: https://issues.jboss.org/browse/SEAMFORGE-110 Project: Seam Forge Issue Type: Library Upgrade Components: Forge Build Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Priority: Minor There are several places where the jboss-javaee-6.0 version is specified. These references should be updated to use 1.0.0.Final. {code} dist/pom.xml: <version>1.0.0.CR1</version> Binary file j2ee-plugins/target/classes/org/jboss/seam/forge/spec/jpa/PersistenceFacet.class matches Binary file j2ee-plugins/target/classes/org/jboss/seam/forge/spec/servlet/ServletFacet.class matches j2ee-plugins/src/main/java/org/jboss/seam/forge/spec/jpa/PersistenceFacet.java: DependencyBuilder.create("org.jboss.spec:jboss-javaee-6.0:1.0.0.CR1:provided:basic"); j2ee-plugins/src/main/java/org/jboss/seam/forge/spec/servlet/ServletFacet.java: DependencyBuilder.create("org.jboss.spec:jboss-javaee-6.0:1.0.0.CR1:provided:basic"); pom.xml: <jboss.javaee.version>1.0.0.CR1</jboss.javaee.version> project-model-tests/target/test-classes/test-pom/pom.xml: <javaee.spec.version>1.0.0.Beta7</javaee.spec.version> project-model-tests/src/test/resources/test-pom/pom.xml: <javaee.spec.version>1.0.0.Beta7</javaee.spec.version> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-34) @Transactional is used by scaffold plugin while not available yet

by Paul Bakker (JIRA)

@Transactional is used by scaffold plugin while not available yet ----------------------------------------------------------------- Key: SEAMFORGE-34 URL: https://issues.jboss.org/browse/SEAMFORGE-34 Project: Seam Forge Issue Type: Bug Reporter: Paul Bakker Priority: Minor I did the following: -create project -install jpa, jsf and cdi -create entity -install scaffold -scaffold from entity... The generated code uses @Transactional which is not available on the project yet. The scaffold plugin should check this and add missing facets. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] Assigned: (SEAMFORGE-3) Create project from Maven archetype

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-3?page=com.atlassian.jira.plugi... ] Lincoln Baxter III reassigned SEAMFORGE-3: ------------------------------------------ Assignee: Rodney Russ Is this the one you're working on? Using FPak? > Create project from Maven archetype > ----------------------------------- > > Key: SEAMFORGE-3 > URL: https://issues.jboss.org/browse/SEAMFORGE-3 > Project: Seam Forge > Issue Type: Feature Request > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-130) StackOverFlow error in CDIFacet for proejcts with BASIC packaging type

by Lincoln Baxter III (JIRA)

StackOverFlow error in CDIFacet for proejcts with BASIC packaging type ---------------------------------------------------------------------- Key: SEAMFORGE-130 URL: https://issues.jboss.org/browse/SEAMFORGE-130 Project: Seam Forge Issue Type: Bug Components: Brainstorming Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Alpha4 at org.jboss.seam.forge.project.facets.builtin.MavenPackagingFacet.getPackagingType(MavenPackagingFacet.java:84) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:84) at org.jboss.seam.forge.spec.cdi.CDIFacet.printPackTypeWarning(CDIFacet.java:108) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:98) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:84) at org.jboss.seam.forge.spec.cdi.CDIFacet.printPackTypeWarning(CDIFacet.java:108) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:98) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:84) at org.jboss.seam.forge.spec.cdi.CDIFacet.printPackTypeWarning(CDIFacet.java:108) at org.jboss.seam.forge.spec.cdi.CDIFacet.getConfigFile(CDIFacet.java:98) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-131) ServletFacet.getResources(FileFilter f) does not use the filter, and should use ResourceFilter instead.

by Lincoln Baxter III (JIRA)

ServletFacet.getResources(FileFilter f) does not use the filter, and should use ResourceFilter instead. ------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-131 URL: https://issues.jboss.org/browse/SEAMFORGE-131 Project: Seam Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III {code} public List<Resource<?>> getResources(final FileFilter filter) { DirectoryResource webRoot = project.getFacet(WebResourceFacet.class).getWebRootDirectory(); return listChildrenRecursively(webRoot); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-132) SimpleTokenCompleter should swallow exceptions when getting completion tokens

by Lincoln Baxter III (JIRA)

SimpleTokenCompleter should swallow exceptions when getting completion tokens ----------------------------------------------------------------------------- Key: SEAMFORGE-132 URL: https://issues.jboss.org/browse/SEAMFORGE-132 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III This would increase resilience... plain and simple. Just because a dev makes a completer mistake, doesn't mean TAB should crash the command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-129) Forge j2ee plugins should be renamed to JavaEE 6 Plugins

by Lincoln Baxter III (JIRA)

Forge j2ee plugins should be renamed to JavaEE 6 Plugins -------------------------------------------------------- Key: SEAMFORGE-129 URL: https://issues.jboss.org/browse/SEAMFORGE-129 Project: Seam Forge Issue Type: Task Components: Builtin Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Alpha4 as name states... refactor packages to allow different versions of javaEE facets. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
4
0 / 0

Re: [forge-dev] hibernate-tools

by Lincoln Baxter, III

I believe so, but max is the expert here :) On Mon, Apr 11, 2011 at 12:43 PM, brian <brianx(a)vt.edu> wrote: > > the absence of the input parms means it will gen everything, yes? > > and the org.hsqldb.jdbcDriver.class just needs to be on the classpath? > > On Mon, 2011-04-11 at 10:50 -0400, Lincoln Baxter, III wrote: > > It doesn't however, succeed, because it's missing the HSQLDB driver, > > and also has hard-coded JDBC connection properties. > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev April 2011