23 Jun
2007
23 Jun
'07
10:51 a.m.
I discovered a Maven2 bug yesterday which makes our build fail if you
try it (it fails to download the XAR handler JAR). To fix this you
need to create a ~/.m2/settings.xml file with the following inside:
<settings>
<profiles>
<profile>
<id>xwiki</id>
<repositories>
<repository>
<id>xwiki</id>
<name>XWiki Maven2 Remote Repository</name>
<url>http://maven.xwiki.org</url>
<releases>
<enabled>true</enabled>
</releases>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>xwiki</activeProfile>
</activeProfiles>
</settings>
This simply tells maven to add the xwiki remote repo to the list of
repo it looks in when looking for an artifact that it doesn't find in
your local repo.
I'll document this. Even better, the m2 dev team has fixed it I think
so I'll try to bundle a new snapshot that contains the fix but
that'll take a bit of time so for now you're safe with the
settings.xml thing.
Thanks
-Vincent
On Jun 22, 2007, at 8:51 PM, Vincent Massol wrote:
Hi everyone,
Here's the current status:
* The m2 build works for everything except watch which isn't
finished yet.
* I haven't put back the Ant build as it's more work to maintain 2
builds and I think the m2 build is good enough not to require the
Ant build.
Thus you can start doing some check outs and commits again. Please
let me know of any issue you find and I'll fix it.
Improvements yet to come:
* Add support for build numbering for having the SVN rev in
version.properties (this is supposed through the buildnumber plugin
in m2)
* Finish the Watch build and add support for GWT compiler in the
build (using the m2 gwt plugin)
* Find out to automate generation of NSIS executables.
* Move some of the old unit tests previously in xwiki/tests in the
new dir structure and as unit tests done in isolation
* Add a distribution module for the XEM build (and a distribution-
test module for functional tests)
* Update the building doc on xwiki.org to reflect the latest changes
* Possibly add more svn:externals definitions if users/devs find
that the main one is too all-encompassing
* Find ways and documents them to do in place web development
easily with the new structure
Thanks
-Vincent
On Jun 21, 2007, at 5:59 PM, Vincent Massol wrote:
hmm... I'm just starting to implement the new
structure and
already I'd like to suggest 2 modifications:
1) Rename xwiki-applications into xwiki-products
2) Rename xarlets into xwiki-applications
WDYT?
Thanks
-Vincent
On Jun 12, 2007, at 6:36 PM, Vincent Massol wrote:
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/
wws Hi,
Note: This email supercedes all my other proposals on the SVN
directory structure.
The rationale for this mail is that we're starting to have lots
of applications built on top of the xwiki platform: XWiki
Enterprise (default wiki), XEM, Watch, Curriki, Chronopolys, etc.
We need to accomodate them in our directory structure.
Top level structure
===============
/svnroot/xwiki/
|_ xwiki-platform/
|_ xwiki-applications/
|_ xwiki-enterprise/
|_ xwiki-enterprise-manager/
|_ xwiki-watch/
|_ curriki/
|_ chronopolys/
|_ xwiki-extensions/
|_ xwiki-eclipse/
|_ xwiki-concerto/
|_ sandbox/
where:
* xwiki-platform is the xwiki platform on which all the
applications are built.
* xwiki-applications are applications that extend the platform
with: skins, xwiki pages (XAR), plugins
* xwiki-enterprise is the name of our previously known "default
wiki" application.
* xwiki-extensions are any other extensions of xwiki not fitting
in xwiki-applications. For example the XWiki Eclipse integration,
etc. I've put concerto there but I'm not sure what it'll look like.
Definition of xwiki-platform
=====================
/svnroot/xwiki/xwiki-platform/
|_ tools/
|_ core/ (JAR)
|_ plugins/ (JARs)
|_ skins/ (ZIPs)
|_ dodo/
|_ finch/
|_ albatross/
|_ web/ (WARs)
|_ gwt/
|_ standard/
|_ xarlets (XARs)
|_ selenium/
|_ blog/
|_ calendar/
|_ ...
where:
* tools/ contains tools used to build the platform and xwiki
applications
* xarlets/ contains independent xwiki apps (we need a word better
than xarlets and different than applications which we should
reserve for things like curriki, xwiki enterprise, xem, etc) that
can be installed in any running xwiki app
* In the future core/ will be replaced with:
|_ components/ (JARs)
|_ xwiki-model/
|_ xwiki-storage/
|_ ...
* In the future web/ will be replaced with UI components (see the
UI proposal for more)
Definition of xwiki-enterprise/
=======================
/svnroot/xwiki/xwiki-applications/xwiki-enterprise/
|_ wiki/
|_ distribution/
|_ distribution-test/
where:
* wiki/ contains the xar pages
Generic definition of an xwiki-application/
=================================
/svnroot/xwiki/xwiki-applications/<app name>/
|_ wiki/
|_ web/ (optional)
|_ plugins/ (optional)
|_ skin/ (optional)
|_ distribution/
|_ distribution-test/
For example for xwiki-watch/:
/svnroot/xwiki/xwiki-applications/xwiki-watch/
|_ wiki/
|_ web/ (the gwt stuff)
|_ distribution/
|_ distribution-test/
I think this pretty much includes everything we currently have in
SVN.
WDYT?
Thanks
-Vincent
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://
www.objectweb.org/wws
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://
www.objectweb.org/wws