And here's another one I've just discovered:
http://plugins.intellij.net/plugin/?id=1223
I haven't tried it yet.
-Vincent
> -----Original Message-----
> From: Vincent Massol [mailto:vincent@massol.net]
> Sent: vendredi 17 novembre 2006 18:30
> To: 'xwiki-dev(a)objectweb.org'
> Subject: [M2] Plugin for IntelliJ IDEA
>
> Hi,
>
> Just found a M2 plugin for IDEA today (see
> http://plugins.intellij.net/plugin/?id=1166). You can get it by
> directly going to the IDEA plugin settings section and installing it
> from there. It creates a Maven2 window on the right which you can then
> use to start any phase/goal.
>
> Have fun!
> -Vincent
>
>
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi everyone,
I'm continuing my progress on our m2 build and here's what I propose:
xwiki/trunk
|_ core/
|_ web/
|_ database/
|_ container/
|_ application/
Where:
* core/ produces the xwiki core JAR which we distribute. It's useful for
plugin developers as they'll need it in the CP.
* web/ produces the xwiki WAR which we distribute. It's useful for advanced
xwiki users who want to install XWiki in their existing container and define
themselves the xwiki configuration including the plugins the want to use.
They'll have to download the plugins separately and install them.
* database/ produces several zip files which we distribute. They are
database instances loaded with a default set of xwiki documents/pages. We
could start with 2 dbs: hsqldb and mysql for example. The idea is that users
could pick these downloads to quickly get up to speed.
* container/ produces several zips files which we distribute. They are
container zips containing the container + xwiki. The only missing thing to
make a working application is the database. Users might want to use this
download if they have a database installed somewhere (possibly on some other
machine) which they want to reuse and they only need the container + xwiki
part. We could start by providing a few zips: tomcat+hsqldb, jetty+hsqldb,
tomcat+mysql for example.
* application/ produces several zips files which we distribute. They contain
completely packaged and runnable xwiki applications, i.e. database +
container + xwiki WAR + default set of plugins. The zips produced match the
zip produced by the container/ module, i.e. tomcat+hsqldb, jetty+hsqldb,
tomcat+mysql, etc.
Notes:
* Unit tests will be found in core/
* Functional tests will be found in application/
* The database/ module will use the importer from xwiki-tools
* The xwiki documents/pages will be found in database/, in XML (export from
a live wiki). They will be used by the functional tests. Thus they'll act
both as test data and also has the default xwiki application that users can
download to try it out.
* The container/ module will use the Cargo m2 plugin to generate a container
package.
* In term of dependencies it'll go like this in the end:
core --> plugins
--> web -------> container ---> application
--> importer --> database --/
So WDYT?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
