fyi, it's now released.
-Vincent
Begin forwarded message:
> From: Dan Fabulich <dfabulich(a)apache.org>
> Date: September 28, 2008 3:48:46 AM CEDT
> To: announce(a)maven.apache.org, Maven Users List <users(a)maven.apache.org
> >
> Cc: Maven Developers List <dev(a)maven.apache.org>
> Subject: [ANN] Maven Reactor Plugin 1.0 Released
> Reply-To: "Maven Users List" <users(a)maven.apache.org>
>
>
> The Maven team is pleased to announce the release of the Maven
> Reactor Plugin, version 1.0.
>
> This plugin can build a subset of interdependent projects in a
> reactor. It should be useful in large reactor builds that include
> irrelevant stuff you're not working on.
>
> http://maven.apache.org/plugins/maven-reactor-plugin/
>
> The Reactor plugin is normally run from the command line, like this:
>
> * reactor:resume resumes a reactor at a certain point (e.g. when it
> fails in the middle)
> Example: mvn reactor:resume -Dfrom=bar
>
> * reactor:make builds a project X and all of the reactor projects on
> which X depends
> Example: mvn reactor:make -Dmake.folders=foo,bar
>
> * reactor:make-dependents builds a project X and all of the reactor
> projects that depend on X (the reverse of reactor:make)
> Example: mvn reactor:make-dependents -Dmake.folders=foo,bar
>
> * reactor:make-scm-changes build all reactor projects that you
> personally have changed (according to SCM) and all reactor projects
> that depend on your changes
> Example: mvn reactor:make-scm-changes
>
> This is the first release of the Maven Reactor Plugin.
>
> Enjoy,
>
> -The Maven team
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe(a)maven.apache.org
> For additional commands, e-mail: users-help(a)maven.apache.org
>
Hi,
Since we really need to have automated tests for the new WYSIWYG from
the onset here are some ideas I'd like to have:
1) It should use Selenium and we need to run it on different browsers
(FF2, FF3, IE6, IE7, IE8 minimum).
2) We need to develop a complete DSL for entering data in the editor
(typeText, moveCursorLeft, clickBold, insertLink, etc). These commands
sent in the test should be independent of the editor technology, which
means I should be able to run the same test in the current TinyMCE
editor or in the new GWT editor or in any future editor. This is
important so that we can capitalize on our editor test suite.
Note: The goal is not to run the tests on the Tiny MCE editor
(although that would be possible) but more to ensure that our tests
are as solid as possible for the future and as easy to write as
possible.
3) As a consequence the asserts done in the test should be on the
generated XHTML (i.e. including the HTMLCleaner for the GWT editor)
since otherwise there would be too many differences between editors.
4) Each editor should have its test suite where it can specify which
test to run (since some features are available in the new GWT editor
for ex but not in the tinyMCE one)
5) Writing a new test should take less than 5 minutes without even the
need to run the test in the editor to prepare it. This means the DSL
should be simple and expressive. For example here's an example of a
test:
testVerifyCanDeleteList()
{
typeText("a");
selectBulletedList();
moveCursorLeft();
typeBackspace();
assertXHTML("<p>a</p>");
}
Note: This test is not taken at random since it currently doesn't
pass ;)
6) Tests must be deterministic (i.e each action should verify that the
action has worked before continuing. For example a typeText should
have a wait on the type text in the page)
WDYT?
Thanks
-Vincent
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.
Hello,
I want to create a class with a DBList property not containing strings but a
list of ID to other BaseObjects...
Then from velocity I want to access directly to this list of objects to
display each object one by one.
But for this, you need ProgrammingRights because
api.Object.get(propertyname) returns a display of the list and not the
list... to retrieve the list, you must call getXWikiObject which requires
programming rights...
But I don't want to give programming rights just to view objects!
Moreover I don't want to be forced to go among $doc.searchXXX just to find
my objects because I have already these objects in my list...
Do you a solution for me? my model might be bad also...
Pascal
I have certainly found a small bug
in com.xpn.xwiki.api.Document, there is:
/**
* Select a subset of objects from a given class, filtered on a "key =
value" criteria.
*
* @param classname The type of objects to return.
* @param key The name of the property used for filtering.
* @param value The required value.
* @return A Vector of {@link Object objects} matching the criteria. If
no objects are found, or
* if the key is an empty String, then an empty vector is
returned.
*/
public Vector<Object> getObjects(String classname, String key, String
value)
{
Vector<Object> result = new Vector<Object>();
if (StringUtils.isBlank(key) || value == null) {
return getObjects(classname);
}
try {
Vector<BaseObject> allObjects = doc.getObjects(classname);
if (allObjects == null || allObjects.size() == 0) {
return result;
} else {
for (BaseObject obj : allObjects) {
if (obj != null) {
BaseProperty prop = (BaseProperty) obj.get(key);
if (prop == null || prop.getValue() == null) {
continue;
}
if (value.equals(prop.getValue())) {
result.add(newObjectApi(obj,
getXWikiContext()));
}
}
}
}
} catch (Exception e) {
}
return result;
}
What is not good:
if (value.equals(prop.getValue())) {
result.add(newObjectApi(obj,
getXWikiContext()));
}
in XWikiDocument.getObject(), it is:
if (value.equals(obj.getStringValue(key))) {
return obj;
}
so getObjects only works when the property is a String.
Best Regards
Pascal
Hi,
We have a problem with the GWT character map. It contains some
characters that are not ISO-8859-1. The problem is that since our
default encoding is ISO-8859-1 (<?xml version="1.0"
encoding="ISO-8859-1" ?>) the browser replaces for example this
character ∞ with ∞
Our rendering doesn't accept HTML so this value is escaped and is
shown as is.
So we have several non-satisfactory options:
1) Switch to UTF8 by default. A good thing but that won't solve the
problem for those using the GWT editor in ISO-8859-1 encoding.
2) Modify the GWT editor character map so that it only shows
characters valid with the current encoding. This is a pity since it
should be possible to display other chars since the browser knows how
to display them even though the user is not in the correct encoding
3) Introduce a wiki syntax for representing characters not allowed in
the current encoding. However this means we'll still need to replace
∞ with this syntax before the rendering is called and this
forbids users to enter ∞ in the wiki editor so this is not good.
Any better idea?
WDYT?
Thanks
-Vincent
Hi Devs,
I'm working on integrating webdav into XWiki UI (+FoXWiki) and I kind of ran
into a small problem.
Our current xwiki-webdav-foxwiki test server is at
http://91.121.237.216/xwiki/bin/view/Main/ (you may give this a try with
firefox). Here in the attachments view, if a firefox user clicks on the
"Edit" link, it should first check if the user has foxwiki installed and if
not should trigger an installation. If the user has foxwiki installed,
foxwiki will take care of the rest of tasks.
The problem is, foxwiki install trigger code is something like this :
<code>
var params = {
"FoXWiki": { URL: "
http://91.121.237.216/xwiki/bin/download/Main/WebHome/foxwiki.xpi",
IconURL: "
http://91.121.237.216/xwiki/bin/download/Main/WebHome/foxwiki.png",
Hash:
"sha1:76920ec6392fec911e13b53ed8d23f64d75502c6",
toString: function () { return this.URL; }
}
};
InstallTrigger.install(params);
</code>
Currently i have put this code into /skins/albatross/scripts/webdav.js
This doesn't look right for obvious reasons, but where else would i put this
code ?
Please help me out :)
Thanks.
- Asiri
Hello,
I want to do the following:
I create a class with one LongProperty field containing a long ID of another
BaseObject.
The idea is to link an object to another object by simply using its hashcode
ID and not the whole docname+classname+nb string. A one-to-one association
if you prefer.
$xwiki.search("from BaseObject as obj...") will return a BaseObject so I can
get the ID here.
But in velocity, I access objects using $doc.getObject() which returns a
Object API.
I can't find any simple way to retrieve the ID of the nested BaseObject from
Object API because getBaseObject requires programming rights.
Do you have an idea for me?
Is it mandatory to use the docname+classname+nb string to identify an object
from velocity?
regards
Pascal
In order to be as efficient as possible in answering questions and so
that the answer benefit others the most we had defined a strategy.
It's written on
http://dev.xwiki.org/xwiki/bin/view/Community/Contributing#HStrategiesforan…
Here's the relevant excerpt:
"
1.1 Strategies for answering on the XWiki lists
Here's a good strategy that improves the XWiki documentation on
xwiki.org:
1. someone (A) asks a question on a xwiki list
1. someone (B) knows the answer
1. B verifies that the answer can be found on xwiki.org and if so
gives a link to it in the reply to A
1. If the answer is not found on xwiki.org, then B adds it (*) and
then gives a link to it in the reply to A
In this manner we all enrich the xwiki documentation and it'll only
take marginally longer to answer questions. The next time someone asks
the question again we can simply point him/her to the location on
xwiki.org
What happens otherwise is that usually people answer in the email,
often giving very long and elaborate answers with lots of knowledge/
wisdom in it. Then another person comes in, asks the same question and
we answer again, etc. The result is:
* the xwiki.org documentation is not better
* overall as a team we are less efficient
(*) One difficult in putting the answer on xwiki.org is to find the
right location where to put it. So here are a few tips:
* For code snippets, add it to the [Code Zone>code:Main.WebHome]
* For questions on how to use XWiki, please add it to the [Features
guide>platform:Features.WebHome]
* For development questions, add it to the [Developer's
guide>platform:DevGuide.WebHome]
* For configuration questions and administration questions, add it to
the [Administration guide>platform:AdminGuide.WebHome]
* For other questions, add them to the [FAQ>xwiki:FAQ.WebHome]
"
I've seen a lot of emails recently where we're not doing this (me
included) and thus I thought it would be to remind us all about
strategy. Also xwiki.org hasn't been improved a lot for a while so
it's good to make an effort to do so. Could be a good thing to do
especially during the bug fixing week.
WDYT?
Thanks
-Vincent
Hi all,
I'm very much happy to have the opportunity to continue work on xwiki after
completing the GSOC and I must thank all of you for giving me this chance.
I'll be working with fabio on implementing the syntax coloring for xwiki.
Basically I will be integrating my gsoc code with the current xwiki
plugin.Thanks again for giving me this opportunity.
----Malaka
Hello,
is there a chance for me to succeed at building xeclipse?
I tried following
http://svn.xwiki.org/svnroot/xwiki/xeclipse/trunk/plugins/org.xwiki.eclipse…
but failed.
- it is spoken there about three downloads but two configs in the
profile... maybe I goofed there
It ended up as:
> generateFeature:
>
> BUILD FAILED
> /Users/paul/tmp/xeclipse/eclise-SDK-3.4/plugins/
> org.eclipse.pde.build_3.4.0.v20080604/scripts/productBuild/
> productBuild.xml:21: The following error occurred while executing
> this line:
> /Users/paul/tmp/xeclipse/eclise-SDK-3.4/plugins/
> org.eclipse.pde.build_3.4.0.v20080604/scripts/productBuild/
> productBuild.xml:53: Unable to find element: /org.xwiki.eclipse.rcp/
> org.xwiki.eclipse.product.
hints welcome
paul
Hi guys,
We're getting behind again in term of bug closings vs bug openings, see
http://tinyurl.com/52oxjq
I think we'll need to start again the Bug Fixing Day.
I propose to start it again next week.
WDYT? Any better idea?
Thanks
-Vincent
Hi,
We're having some last-minute problems with the new GWT editor and we
need a few more days to fix them.
Thus I'm proposing that we delay the XE 1.5RC1 release for 3 more days
to Thursday 25th of Sept.
This means a potential 1.6 Final (if no important bugs are found) for
the 29th of Sept.
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Workspaces 1.2 Milestone 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
New features have been implemented in this release, amongst them :
* Custom user groups (Manage global group of users, and add them as members of your workspaces)
* Revamped Administration
* Global Search (Search content across all the workspaces you have access to)
You can read the full release notes, including screenshots of the
aforementioned features, here :
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWorkspaces12Milestone1
To get started with XWiki Workspaces, point your browser at
http://workspaces.xwiki.org
Thanks
-The XWiki dev team
Hi Fabio,
I think we should release XEclipse ASAP since it has progressed quite
nicely and we haven't had a release for some time.
I know you're probably quite busy but is it possible to plan a release
and have a roadmap for it?
Thanks a lot
-Vincent
Hello,
did anyone encounter issues with running the ActivityStream plugin
with Postgres?
I seem to have non-well-formed SQL queries in two different Postgres
versions.
Can it be this is related to
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2984
?
paul
Caused by:
com.xpn.xwiki.plugin.activitystream.api.ActivityStreamException: Error
number 3223 in 3: Error number 3223 in 3: Exception while searching
documents with sql select act from ActivityEventImpl as act,
ActivityEventImpl as act2 where act.eventId=act2.eventId and
act.stream=Group_gg group by act.requestId having
(act.priority)=max(act2.priority) order by act.date desc
Wrapped Exception: could not execute query
Wrapped Exception: could not execute query
at
com
.xpn
.xwiki
.plugin
.activitystream
.impl.ActivityStreamImpl.searchEvents(ActivityStreamImpl.java:223)
at
com
.xpn
.xwiki
.plugin
.activitystream
.impl.ActivityStreamImpl.getEvents(ActivityStreamImpl.java:248)