Hi all,
This is not a XWiki issue, but following the discussion about the Maven
version to standardize on XWiki build I am trying to configure a
developer environment in a MacBook Pro running Mac OS X 10.5.5. Your
help will be really welcome. Thanks!
Mac OS X 10.5.x includes Maven 2.0.6 in its base installation. Thus, mvn
--version gives...
GMXUX-Ricardo-Rodriguez:~ rrodriguez$ mvn --version
Maven version: 2.0.6
I've tried to follow the installation instructions in Maven support site
to install both (or at least one of them) Maven 2.0.9 and/or Maven 2.1.0
M1 but I am falling at setting the correct environment system wide. It
works fine if I export each concerned variable in a given shell, but
this only works for this and only this shell window...
sh-3.2# export M2_HOME=/usr/local/apache-maven/apache-maven-2.0.9
sh-3.2# export M2=/usr/local/apache-maven/apache-maven-2.0.9/bin
sh-3.2# echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
sh-3.2# export PATH=$PATH:$M2
sh-3.2# echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/apache-maven/apache-maven-2.0.9/bin
sh-3.2# mvn --version
Maven version: 2.0.9
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix"
sh-3.2# echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/apache-maven/apache-maven-2.0.9/bin
sh-3.2#
Please, what method do you use to set M2, M2_HOME and modify PATH to
include M2? Is it possible to set them system wide or at least user
wide? I've tried a number of methods without success.
Thanks for your help,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
vmassol (SVN) wrote:
> Author: vmassol
> Date: 2008-09-15 12:59:12 +0200 (Mon, 15 Sep 2008)
> New Revision: 12689
>
> Modified:
> platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/renderer/XHTMLRenderer.java
> platform/core/trunk/xwiki-rendering/src/test/resources/list/definitionlist2.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list1.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list3.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list4.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list5.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list6.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list7.test
> platform/core/trunk/xwiki-rendering/src/test/resources/list/list8.test
> platform/core/trunk/xwiki-rendering/src/test/resources/macros/velocity/macrovelocity1.test
> Log:
> Refactoring. Remove class="star" when generating a bulleted list in the new rendering.
>
Note that the class was there to differentiate between lists generated
by * and lists generated by -
* class="star" list item
- class="minus" list item
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
mflorea (SVN) wrote:
> Author: mflorea
> Date: 2008-09-26 12:48:14 +0200 (Fri, 26 Sep 2008)
> New Revision: 13009
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/templates/editwysiwygnew.vm
> Log:
> The teletype feature will be included in 1.7 so I removed it from the tool bar. I also changed the way the editor loads. Now it gets as input HTML and not wiki syntax. This way the editor loads faster.
The textarea held wiki markup, so that in case JS is disabled, the user
can still edit the content. Is it OK to break this? Will such a user
know to open the wiki editor instead? Should there be 2 textareas, one
with the wiki markup, and a hidden one with the HTML content?
> Modified: platform/web/trunk/standard/src/main/webapp/templates/editwysiwygnew.vm
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/templates/editwysiwygnew.vm 2008-09-26 10:45:11 UTC (rev 13008)
> +++ platform/web/trunk/standard/src/main/webapp/templates/editwysiwygnew.vm 2008-09-26 10:48:14 UTC (rev 13009)
> @@ -26,14 +26,14 @@
> <link rel="stylesheet" href="${request.contextPath}/com.xpn.xwiki.wysiwyg.Wysiwyg/Wysiwyg.css" />
> <script type="text/javascript" src="${request.contextPath}/com.xpn.xwiki.wysiwyg.Wysiwyg/com.xpn.xwiki.wysiwyg.Wysiwyg.nocache.js"></script>
> <iframe src="javascript:''" id="__gwt_historyFrame" style="width:0;height:0;border:0"></iframe>
> -$xwiki.getTextArea($tdoc.content)
> +$xwiki.getTextArea($xwiki.wysiwyg.toHTML($tdoc.content, $doc.syntaxId))
> <script type="text/javascript">
> //<![CDATA[
> var Wysiwyg0 = {
> hookId: 'content',
> syntax: "$doc.syntaxId",
> plugins: 'separator text valign list indent undo format symbol',
> - toolbar: 'bold italic underline strikethrough teletype | subscript superscript | unorderedlist orderedlist | outdent indent | undo redo | format | hr symbol',
> + toolbar: 'bold italic underline strikethrough | subscript superscript | unorderedlist orderedlist | outdent indent | undo redo | format | hr symbol',
> debug: #if($request.debug)'true'#else'false'#end
> };
> //]]>
>
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
I'd like to propose to change the escape character. Right now it's \
The problem is that if you want to enter a \, you'll want to write \\
but that's reserved for a new line...
Hence and in order to be more Creole compatible I propose to replace
our current \ escape character by a ~
See http://www.wikicreole.org/wiki/Creole1.0#section-Creole1.0-EscapeCharacter
Here's my +1
Thanks
-Vincent
Hi,
Since we send all jira emails to the devs list, I propose to remove
sending notifications systematically to jira project leads (since
they should/must follow the list).
This will prevent lots of duplicates for project leads.
WDYT?
Here's my +1
Thanks
-Vincent
Hi,
I'm proposing to introduce the ((( ... ))) wiki syntax to support
nested documents.
For example this allows putting any type of wiki syntax inside table
cells. This also allows having a table inside a list for example.
See the section entitle "embedded document" on
http://code.google.com/p/wikimodel/wiki/AdvancedStructuralElements for
some examples.
Here's my +1
Thanks
-Vincent
Hi,
Guillaume was surprised (and rightly so) that we use this format for
nested lists:
111*.
He was expecting 111.*
I remember I had the same remark the first time I saw this a long time
ago.
Thus (if we agree) we have 2 solutions:
Solution 1:
=========
111.*
Solution 2:
========
1.1.1.*
Another solution would be to use another symbol but we cannot use #
and the second most common solution is "1."
See http://www.wikimatrix.org/syntax.php?i=33
I'm hesitating but I propose to use Solution 2 which seems the most
consistent to me.
WDYT?
Thanks
-Vincent
Dear all,
The XWiki Development Team is pleased to announce the release of the
Worktream Application, version 1.0.
You can find it here :
http://code.xwiki.org/xwiki/bin/view/Applications/WorkstreamApplication
Workstream is a internal twitter-like micro-blogging application that
allows the wiki users to post short status updates. It support internal
and external URL links using the wiki syntax. There is both a wiki page
with recent updates and the ability to browse updates by user, and a
panel easily installable in the whole wiki or in any space, with as well
recent updates and a text box for one to update its status.
Hope you'll enjoy it !
Thanks,
-The XWiki Development Team
Hello devs,
Couple of weeks ago, I committed a first implementation of a workstream
application in xwiki-applications. I would like to release this as a
first 1.0 version, documenting it and making it available on code.xwiki.org.
This first version is a internal twitter-like micro-blogging application
that allows the wiki users to post short status updates. It support both
internal and external linking using the wiki syntax (actually it just
supports wiki syntax). There is both a wiki page with recent updates,
and the ability to browse updates by user, and a panel easily
installable in the wiki or in any space, with as well recent updates and
a text box for one to update its status.
My +1,
Jerome.
Hello developpers,
The bug fixing week continues until friday evening, please don't forget
to tag the bugs you fix with the keyword "bugfixingweek-39-2008" on
JIRA. Works for all projects !
Thanks,
Jerome.