On 1/25/07, molecool <[EMAIL PROTECTED]> wrote:
Aren't you referring to your 'warpath' plugin? I just took a look at this: http://static.appfuse.org/plugins/maven-warpath-plugin/usage.html and I'm pretty stoked :-)
The war plugin has the overlay feature: http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html The warpath plugin allows us to read dependencies from WARs. By default, Maven treats WARs as dumb dependencies with no dependencies. Without the warpath plugin, you can't add WAR dependencies to your classpath and you have to build WARs with no classes in them. We couldn't do AppFuse 2.0 without this plugin.
So, let me make sure I get this right. The core classes and jsps of appfuse are being injected during the build process and get downloaded to your local maven repo, correct? What I'm still confused about is how exactly running 'mvn war:inplace' changes that dependency. Does it remove that external dependency in the pom and the code is now part of your project? Obviously, once that happens you are unable to update to a new version via maven...
Running mvn war:inplace extracts all the contents of the WAR into your local project. It's pretty ugly because you don't want *everything*. In most cases, you simply want to override a few files. We recommend using war:inplace because after you do so, you can use "mvn jetty:run", which allows you to develop w/o restarting Jetty. It'll automatically restart if it detects any changes. Running "mvn jetty:run-exploded" and "mvn package" in another window has the same effect. However, jetty:run is a lot nicer because you can leverage your IDEs compile-on-save feature and eliminate the deploy cycle. Here's a video demonstration: http://static.appfuse.org/movies/2.0/struts2-crud.mov
Further, if I want to override the look and feel of appfuse without changing for instance the JSPs' code, what would be a good strategy for that? Or if I want to retain a subset of the functionality (login/logout and/or change user prefs) but want to remove the rest - is that possible? Wouldn't it make sense to create sub JSPs that can be enabled/disabled as part of your 'page' JSPs and thereby you could retain some of the core functionality and allow it to be extended later on?
There's all kinds of possibilities. For the most part, we're still trying to get all of AppFuse 1.x's functionality in 2.0, so we haven't started to ask/implement all the features that users might need. It should be possible to remove fields from the userForm.jsp and everything will still work.
I hope I'm not going on a tangent on this one - if these questions have been addressed in the past, please let me know.
These are great questions - we should probably add some to the FAQ. If you're interested in helping out, you should be able to create a wiki account (View > Account > Sign Up) and add them. ;-) http://appfuse.org/display/APF/FAQ Matt
Cheers, Michael Matt Raible-3 wrote: > > They're "merged" in from AppFuse WARs thanks to the Maven War Plugin. > This allows us to package "core" features in AppFuse and inject them > into your project at build time. If you want to modify JSPs and web > files, you can put get them in your project by running "mvn > war:inplace". > > WARNING: This injects everything, including .class files and JAR > files. We recommend you check your project into version control before > running it. Deleting src/main/webapp/WEB-INF/lib and > src/main/webapp/WEB-INF/classes is recommended as duplicate JARs in > your classpath causes issues with some frameworks. > > Here's how to modify the model objects: > > http://appfuse.org/display/APF/AppFuse+Core+Classes > > We're still working on a way for you to customize other source files. > If you're Maven 2 savvy, you can probably build your own project by > piecing together AppFuse's modules from SVN. > > We could distribute a "full source" archetype, but that goes against > the whole "here's an easily upgradable system" that we're trying to > create with AppFuse 2.0. ;-) > > Matt > > On 1/25/07, molecool <[EMAIL PROTECTED]> wrote: >> >> Okay, I'm confused - I was able to deploy and the good old appfuse >> interface >> popped right up. However, all of this seems to be happening automagically >> - >> where are all the sources and the jsps? >> >> find -name '*.java' produces: >> >> ./core/src/main/java/Core.java >> ./core/src/test/java/CoreTest.java >> ./web/src/main/java/App.java >> ./web/src/test/java/AppTest.java >> ./web/target/work/jsp/org/apache/jsp/common/footer_jsp.java >> ./web/target/work/jsp/org/apache/jsp/common/header_jsp.java >> ./web/target/work/jsp/org/apache/jsp/common/menu_jsp.java >> ./web/target/work/jsp/org/apache/jsp/decorators/default_jsp.java >> ./web/target/work/jsp/org/apache/jsp/index_jsp.java >> ./web/target/work/jsp/org/apache/jsp/login_jsp.java >> ./web/target/work/jsp/org/apache/jsp/scripts/validator_jsp.java >> ./web/target/work/jsp/org/apache/jsp/WEB_002dINF/pages/mainMenu_jsp.java >> ./web/target/work/jsp/org/apache/jsp/WEB_002dINF/pages/userForm_jsp.java >> >> Where does all that deployed stuff in target come from? I don't see any >> templates anywhere either. If someone could explain this to me or point >> me >> to the appropriate documentation I would be grateful. >> >> Thanks, >> >> Michael >> -- >> View this message in context: >> http://www.nabble.com/Appfuse-2.0---where-are-the-sources-jsps--tf3119998s2369.html#a8643984 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Appfuse-2.0---where-are-the-sources-jsps--tf3119998s2369.html#a8644707 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
