I don't currently use any of the Maven Eclipse IDE integration plugins
and just use
Eclipse's external tools facility to run mvn for any selected folder
in Eclipse's 'Package Explorer' pane.
At least this way you know Maven is behaving as it does from the
command line, for new dependency I add to pom.xml and run
eclipse:eclipse, but this
can be done from inside Eclipse aswell.
e.g.
Set up a new External Tool as follows :
Name: mvn clean install
Location: ${env_var:M2_HOME}/bin/mvn.bat
Working Directory: ${resource_loc}
Arguments: clean install
Then just select the folder or project in the Eclipse Java Tree
(folder must have a pom.xml in it) then select this external tool 'mvn
clean install' - once run once it will be on the drop down.
You can set up the common maven goals like this, then share the
External tools configuration by using the 'Common' tab and specifying
a folder that is under SCM.
Also can set up an 'General Project' in Eclipse that points to your
local repo folder, this allows you to search this area and open pom
files if necessary.
I would gladly swap to a Plugin but there always seems to be
unexpected side effects.
On 18/09/2007, Pete <[EMAIL PROTECTED]> wrote:
> I use Eclipse and the External Tools configuration to run mvn from
> within eclipse if needed.
>
> I used to have Eclipse compiling to a different classes directory and
> that worked fine for many projects, but recently I use 'mvn
> jetty:run' all the time so that when I save a java file in Eclipse it
> gets compiled immediately by Eclipse and the change will be instantly
> visible in Jetty. Working this way eclipse and mvn must compile to
> same place, as jetty start up using the classpath that mvn is using.
>
>
> On 17/09/2007, Jim Sellers <[EMAIL PROTECTED]> wrote:
> > I'd take a look at what files are generated when you create a new project
> > using SAP. Are there other folders / files that are created? (starting
> > with a dot).
> >
> > Are there project natures / builders that are not being included (in the
> > .project file)?
> >
> > It sounds like there is *something* missing that SAP is reading / looking
> > at.
> >
> > Jim
> >
> >
> > 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]
> > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
