St�phane MOR <[EMAIL PROTECTED]> wrote on 02/09/2002 03:29:01 PM:
> [EMAIL PROTECTED] wrote:
>
> >For those with patience, broadband (it's over 1MB) or an interest:
> >
> >http://adslgateway.multitask.com.au/MavenEclipse/index.html
> >
> ><flameSuit>Let me know what you think</flameSuit>
> >
> Great, dIon !
>
> I used that to make an eclipse:external-tools goal, that generates a
> $ECLIPSE_HOME/workspace/.metadata/.plugins/org.eclipse.ui.
> externaltools/externaltools.xml.
Cool. Now all we need is a Maven preferences page to hold MAVEN_HOME :)
> This file contains a tool for each goal. For instance, you'll get a
> "Maven site" button under "Run/External Tools"
> that generates the site.
Sounds good.
> To avoid having 100+ goals, I implemented a property to choose whether
> we want all the goals,
> or only the default goals. (currently thinking about an <include/> and
> <exclude/> mechanism ...)
>
> I'm ready to commit that, but I'd like to know if we can have
> project-specific external tools, under
> workspace/${project}/.metadata/.plugins/org.eclipse.ui.
> externaltools/externaltools.xml
> for instance.
AFAIK, the external tools aren't project specific, they are workspace
specific, hence they get stored under the workspace (-data) directory.
> Any idea ?
>
> I'd like to avoid destroying existing external tools ...
> Hmmm, wait, this can be done by parsing the existing file before writing
> to it ...
It'd be good if it didn't destroy any existing config.
>
> Thanks,
> St�phane
>
> PS: I never used Eclipse before there was the eclipse plugin (I hate
> having to set classpaths and other
> horrible stuff for each IDE...), so please correct me if I've got it
> completely wrong ! ;-)
Nope, this sounds great!
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
