Thierry is definitely right that you can run into inconsistencies between the incremental Eclipse builds versus Maven builds. I've had to do occasionally some Project->Cleans to get rid of the red.
Wayne I would DEFINITELY upgrade to an Eclipse 3.x product. I think in general you would be better off (provided the SAP bits are still compatible). Do you use any Eclipse based plugin such as m2eclipse or q4e with NWDS? If not and its possible, I would definitely encourage you to at least try it. -aps On 9/17/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > Since we're talking about Eclipse... As I said before, I'm using SAP > NWDS (2.0.14) which is based on Eclipse v2.1. I'm using > eclipse:eclipse to generate metadata and added the proper perspectives > etc. > > When I create a new project (J2EE, EJB Module Project or Web Module > Project) then it shows up in the J2EE Explorer and things are good. > > When I use mvn e:e and then import the project, it comes in as a > "standard" Java project. I've tried editing metadata files manually > but its still not coming up the way I was hoping. The EJB project > shows up in J2EE Explorer but the beans don't show up since I'm not > using the default ejbModule directory etc. > > Any ideas? I might try upgrading to the latest NWDS build which is > based on Eclipse 3, apparently. > > Wayne > > On 9/16/07, Thierry Lach <[EMAIL PROTECTED]> wrote: > > There can be problems caused with a single build destination caused by > the > > Eclipse incremental compiler that would sometimes require doing a clean > in > > both maven and eclipse. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
