Hi, I have tried the demo using AppFuse 3.50 basic Spring Archetype, impressed by its functionality available in a given stack or package. The best to play with the demo is to load the Maven jetty built demo into MyEclipse or other IDEs. However it took me a while to make it runnable on MyEclipse 2014, with a badly formatted project structure, on latest Mac setup. The Standard Maven Project Structure helps developers to easily follow the framework, classes and their implementations. Can it be done in AppFuse?
Sam Lee |
Administrator
|
Hello Sam,
An AppFuse-generated project should follow the standard maven project structure. What do you see in AppFuse that does not do this? Thanks, Matt > On Apr 22, 2016, at 3:49 AM, sam8881 <[hidden email]> wrote: > > Hi, I have tried the demo using AppFuse 3.50 basic Spring Archetype, > impressed by its functionality available in a given stack or package. The > best to play with the demo is to load the Maven jetty built demo into > MyEclipse or other IDEs. However it took me a while to make it runnable on > MyEclipse 2014, with a badly formatted project structure, on latest Mac > setup. The Standard Maven Project Structure helps developers to easily > follow the framework, classes and their implementations. Can it be done in > AppFuse? > > Sam Lee > > > > -- > View this message in context: http://appfuse.547863.n4.nabble.com/Importing-projects-in-Standard-Maven-JEE-Project-Structure-to-any-IDE-tp4657894.html > Sent from the AppFuse - User mailing list archive at Nabble.com. |
Hello Matt,
Thank you for your quick reply! On second look, I was wrong on that. AppFuse 3.5 does follow the Maven standard structure. However, I have been trying to apply: mvn appfuse:full-source on tutorial-spring project in the demo projects. The result contains 52 errors, cannot be complied at all. If I import the project into MyEclipse 2014, nothing is right, all codes show with red errors. But the embedded one is ok! Thanks again Sam Lee |
Administrator
|
Did you create your own tutorial-spring or did you clone the completed one from GitHub?
> On Apr 24, 2016, at 9:59 AM, sam8881 <[hidden email]> wrote: > > Hello Matt, > Thank you for your quick reply! On second look, I was wrong on that. AppFuse > 3.5 does follow the Maven standard structure. However, I have been trying to > apply: mvn appfuse:full-source on tutorial-spring project in the demo > projects. The result contains 52 errors, cannot be complied at all. If I > import the project into MyEclipse 2014, nothing is right, all codes show > with red errors. But the embedded one is ok! > > Thanks again > Sam Lee > > > > -- > View this message in context: http://appfuse.547863.n4.nabble.com/Importing-projects-in-Standard-Maven-JEE-Project-Structure-to-any-IDE-tp4657894p4657896.html > Sent from the AppFuse - User mailing list archive at Nabble.com. |
I cloned the completed one from GitHub! Send by my iPad
|
Administrator
|
appfuse:full-source usually works best after you’ve created a new project with the mvn archetype:generate command. I’d recommend going that route rather than cloning an existing project and trying to run it on that. Hope this helps, Matt
|
Free forum by Nabble | Edit this page |