On 6/12/07, Adam Sherman <[EMAIL PROTECTED]> wrote:
On Jun 11, 2007, at 15:33, Matt Raible wrote:
>> Yeah, you should be able to delete all the files you already have in
>> > src/main/resources (since there will be duplicates). You can also
>> > delete WEB-INF/lib and WEB-INF/classes/your/package/name. You'll
>> need
>> > to retain WEB-INF/classes/org/appfuse because the jetty plugin is
>> > unaware of the warpath plugin (which reads dependencies from war
>> > files).
>>
>> Indeed, this works perfectly. So now I have it both ways: I can run
>> jetty:run and upgrades to the next version of AppFuse will only
>> involve src/main/webapp/WEB-INF/classes/.
>
> The problem with this is you have duplicate dependencies. Maven is
> unaware of any classes in WEB-INF/classes, so if you extend any
> AppFuse classes, you'll be extending the binary dependency as listed
> in your pom.xml. So if your pom.xml and WEB-INF/classes are out of
> synch, you'll likely experience weird issues.
But making sure to upgrade the classes in WEB-INF/classes and change
the PoM simultaneously will keep things working, no?
Yes.
> With that being said, I think you're better off using full-source.
> That will give you the functionality you're looking for - and you'll
> be decoupled from AppFuse.
But I'll never be able to upgrade as you update things in AppFuse,
right? I don't like that.
You can always diff your project against a newer release of AppFuse
with something like Beyond Compare and upgrade that way.
Matt
> Regardless of all this advice - if the setup you're using works for
> you, that's the most important thing.
Well of course! But I like to have a source tree I can be proud of… :-)
Thanks for your help,
A.
--
Adam Sherman
Technologist
+1 (613) 797-6819 | http://www.sherman.ca/ | sip:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com
