[ https://issues.jboss.org/browse/FORGE-388?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-388: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/74 -- 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

[ https://issues.jboss.org/browse/FORGE-388?page=com.atlassian.jira.plugin.... ] Serhiy V commented on FORGE-388: -------------------------------- According to latest comments in FORGE-120 I see how to create "pom" type of project. Obviously the same way I can create "war" or "jar"projects. I can run something like {code} new-project --named foo --topLevelPackage com.bar --type pom new-project --named foo-data --topLevelPackage com.bar --type jar new-project --named foo-web --topLevelPackage com.bar --type war {code} but it is still needed to setup dependencies between sub-projects (modules) manually. In is possible to add some helper commands like {code} project add-subproject --named foo-data --type jar {code} But frankly speaking this is not really important. Instead we can have a simple one-page official documentation that explains people how to setup such projects. I would prefer having more documentation and less commands :-). Could you please add some documentation which covers this? Other issue is that is some cases in order to use some functionality you first needs to "setup" something. For example, in order to create new entity classes you need to run {code} persistence setup ... {code} It obviously makes seance. But if you really want to support multi-module projects this approach will not work. Default behavior should stay the same. But I propose to introduce alternative way to add "persistence awareness" to the project through plugins. Something like {code} forge install-plugin jpa {code} This "new" plugin will not add persistence.xml to the project but will rather add proper dependencies to pom.xml and will enable possibility to work with entities using seam commands. Same approach can be used to other plugins that require setup before usage. Another example I want to talk about is the automatic discovery functionality. For example {code} scaffold from-entity {code} and "tab" gives the list of all available entities. Forgive me for not trying this by myself but I had some issues last time when I tried to setup this. I am not sure if this list if only from "current" project or forge does scans also jars in dependencies to check if they have appropriate classes. But anyway the most important thing is some official documentation or guide how to work with multiple modules using seam. There is no need to support everything or all possible features. I am absolutely positive that even very limited (but documented and supported :-)) multi-module support would very helpful and absolutely ok in most cases. Thanks, Serhiy -- 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

[ https://issues.jboss.org/browse/FORGE-388?page=com.atlassian.jira.plugin.... ] Serhiy V commented on FORGE-388: -------------------------------- Maybe I am missing something but I was not able to find mentioned options in the prompt. Here is my console output (can't attache screenshot because issue is closed) {code} D:\tmp\forge-distribution-1.0.0.Beta3\forge-1.0.0.Beta3\bin>forge ____ _____ / ___| ___ __ _ _ __ ___ | ___|__ _ __ __ _ ___ \___ \ / _ \/ _` | '_ ` _ \ | |_ / _ \| '__/ _` |/ _ \ \\ ___) | __/ (_| | | | | | | | _| (_) | | | (_| | __/ // |____/ \___|\__,_|_| |_| |_| |_| \___/|_| \__, |\___| |___/ Windows? Really? Okay... [no project] bin $ new-project --named foo --topLevelPackage com.bar --type pom ? Use [D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo] as project directory? [Y/n] y ***SUCCESS*** Created project [foo] in new working directory [D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo] Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/pom.xml [foo] foo $ new-project --named foo-core --topLevelPackage com.bar ? Use [D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core] as project directory? [Y/n] y ***SUCCESS*** Created project [foo-core] in new working directory [D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core] Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/pom.xml Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/src/main/java Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/src/test/java Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/src/main/resources Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/src/test/resources Wrote D:\/tmp/forge-distribution-1.0.0.Beta3/forge-1.0.0.Beta3/bin/foo/foo-core/src/main/resources/META-INF/forge.xml [foo-core] foo-core $ {code} I was asked only about project directory. And after I've added second project pom.xml of "foo" project is following {code} <?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>com.bar</groupId> <artifactId>foo</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>pom</packaging> <repositories> <repository> <id>JBOSS_NEXUS</id> <url>http://repository.jboss.org/nexus/content/groups/public</url> </repository> </repositories> <build> <finalName>foo</finalName> </build> </project> {code} So it is missing {code} <modules> <module>foo-core</module> </modules> {code} and respectively pom.xml of "foo-core" is missing "parent" definition. Do I need to add some special parameters to the commands? I really don't want to bother you but I can't find mentioned options or any documentation how to work with them. Thanks, Serhiy -- 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

[ https://issues.jboss.org/browse/FORGE-388?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-388: ------------------------------------------ Yep, that's right. Thanks again, Torben! -- 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