-
1. Re: forge's --topLevelPackage not work
I think forge 2 doesn't create the package immediately after project-new command?
-
2. Re: forge's --topLevelPackage not work
Hi xiaohui,
That's right. Right now this information is set as the groupId in the pom.xml, so when you create a new class using the jpa-new-entity command, for example, by default it will create it under the package you provided (org.cedj.ch03.feedback.model in this case).
However now that you mentioned it, I think it would be good to have it created after project-new is executed. Could you create a new JIRA in Forge - JBoss Issue Tracker and I'll have a look at it?
Thank you. Best Regards,
George Gastaldi -
3. Re: forge's --topLevelPackage not work
Just created the issue, it is fixed and it should be available in the next release
[FORGE-2475] Top level packages should be created in project-new - JBoss Issue Tracker]
Best Regards.
George Gastaldi
-
4. Re: forge's --topLevelPackage not work
thank you George.But can you provide some tutorial guiding how to migrate from forge 1 to forge2 . Recently,I explored a lot article about forge(including book <Continuous Enterprise Development in Java>),but most of them use forge 1 as example . I tried to change them to forge2, but I am stuck on them .For example ,I can find out how to jboss-as-7 addon in forge2(forge 1 use:forge install-plugin jboss-as-7). maybe this addon is not ready for forge2?
Or I should use forge 1 instead? thank you.