The main problem is, that if you try to build everything from scratch with mvn eclipse:eclipse in the old project structure that worked, you also could deploy the sandbox examples directly from eclipse that way. Now if you do that you run into runtime issues, due to the rename of the shared packages in the last build stage.
I will try to find a solution to this problem, but the reorg and maven switch as it is has made things very complicated for all users trying to hack components within an IDE, partially due to the sad state of the maven2 plugins. (well it used to be easier until the build three subpackages from one source within maven issue was programmed in) Manfred Geiler schrieb: > I recommend adding the *-sources.jar files instead of the target dirs > for the reasons mentioned earlier in another thread (jar sources > read-only, target dirs volatile, ...) > > Can some of the eclipse gurus please try that out and revise the wiki > instructions accordingly? > > Thanks, > Manfred > > > > On 3/2/06, Werner Punz <[EMAIL PROTECTED]> wrote: >> Mario Ivankovits schrieb: >>> Hi! >>>> Is there any reason for having after an eclipse import references to a >>>> non existing shared_impl package? >>>> >>> I've posted a workaround for this (with eclipse) >>> See in wiki "Building with myfaces" how to workaround this problem. >>> >>> Unhappily you have to adjust the project, for now. >>> >>> Ciao, >>> Mario >>> >>> >> Thanks mario, adding the refactoring source paths helped ;-) >> >> >
