What is ok for you?
You have deleted the original message so we don't know what you're
answering! :-)
Thanks
-Vincent
> -----Original Message-----
> From: phunghainam(a)xwiki.com [mailto:phunghainam@xwiki.com]
> Sent: mardi 26 décembre 2006 14:30
> To: xwiki-dev(a)objectweb.org
> Subject: Re: RE: [xwiki-dev] XWiki 1.0 JIRA issues
>
> It is ok for me , but I moved some tasks and improvements to 1.1
> version release
___________________________________________________________________________
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 xwiki developers,
When you enter or close some issues please ensure that the "affects" field
is always set.
This lets our users know whether the fixed issues was affecting the version
they're using or not and allows us to categorize issues and have statistics.
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
Hi
I try to compile from the latest svn image. It does not compile at target
xwiki. Have you some idea why?
Buildfile: build.xml
prepare:
[propertyfile] Updating property
file: /home/samba/devel/xwiki/web/standard/src/main/webapp/WEB-INF/version.properties
clover-yes:
clover-no:
xwiki.nonjava:
[copy] Copying 1 file to /home/samba/devel/xwiki/build/web
xwiki:
(...)
[javac] /home/samba/devel/xwiki/core/src/main/java/com/xpn/xwiki/store/XWikiJDBCConnection.java:34:
com.xpn.xwiki.store.XWikiJDBCConnection is not abstract and does not override
abstract method createStruct(java.lang.String,java.lang.Object[]) in
java.sql.Connection
[javac] public class XWikiJDBCConnection implements Connection {
[javac] ^
(...)
[javac] 1 error
[javac] 37 warnings
Hi Ludovic,
I see you've just committed code in the 1.0 BETA 1 branch... I don't think this is right :-) Actually this branch needs to be closed. We already have a tag for 1.0 BETA 1. Could you please recommit this to trunk?
We've agreed to work on trunk till B2 is released and swithc to a 1.0 branch when we promote it to RC1.
Thanks
-Vincent
> -----Original Message-----
> From: Ludovic Dubost [mailto:ludovic@users.forge.objectweb.org]
> Sent: vendredi 22 décembre 2006 15:11
> To: xwiki-commits(a)objectweb.org
> Subject: [xwiki-commits] r1796 -
> xwiki/branches/XWIKI_1_0_BETA_1/core/src/main/java/com/xpn/xwiki/render
> /macro/rss
>
> Author: ludovic
> Date: 2006-12-22 15:10:31 +0100 (Fri, 22 Dec 2006) New Revision: 1796
>
> Modified:
>
> xwiki/branches/XWIKI_1_0_BETA_1/core/src/main/java/com/xpn/xwiki/render
> /macro/rss/RSSMacro.java
> Log:
> XWIKI-283 Fix RssMacro because of changes in Rome
>
> Modified:
> xwiki/branches/XWIKI_1_0_BETA_1/core/src/main/java/com/xpn/xwiki/render
> /macro/rss/RSSMacro.java
> ===================================================================
> ---
> xwiki/branches/XWIKI_1_0_BETA_1/core/src/main/java/com/xpn/xwiki/render
> /macro/rss/RSSMacro.java 2006-12-22 02:34:37 UTC (rev 1795)
> +++
> xwiki/branches/XWIKI_1_0_BETA_1/core/src/main/java/com/xpn/xwiki/render
> /macro/rss/RSSMacro.java 2006-12-22 14:10:31 UTC (rev 1796)
> @@ -181,7 +181,7 @@
> if (paramObj.isFull() && entry.getDescription() != null)
> {
> buf.append(NEWLINE).append("{quote}")
> - .append(NEWLINE).append(entry.getDescription())
> +
> + .append(NEWLINE).append(entry.getDescription().getValue())
> .append(NEWLINE).append("{quote}");
> }
> }
> @@ -214,7 +214,7 @@
> if (paramObj.isFull() && entry.getDescription() != null)
> {
> buf.append(NEWLINE).append("<div
> class='rssitemdescription'>")
> - .append(NEWLINE).append(entry.getDescription())
> +
> + .append(NEWLINE).append(entry.getDescription().getValue())
> .append(NEWLINE).append("</div>"); // close
> rss.item.description
> }
> buf.append(NEWLINE).append("</div>"); // close rss.item
>
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi,
XPertNet, the source of the XWiki Software is looking for XWiki Web
developpers to work on customer projects.
The skill set required is XHTML/CSS/Form/Ajax development for the
front-end talking to the XWiki backend with scripting in velocity or
groovy using the XWiki API.
A good sense of user interface and good design is a plus. Java knowledge
is a plus.
We are looking to fill permanent positions, internships but can also
accept part-time or contracting work.
It can be either in our Paris Office or anywhere else on the planet
working from home.
You will be joining a team of already more than 10 talented and
motivated people working on open source software and on projects like
XWiki 1.0 (http://www.xwiki.org), Curriki (http://www.curriki.org).
You can contact me at ludovic(a)xwiki.com or on skype (ldubost) for more
information.
Ludovic
---
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
Hi,
FYI I have succeeded in cleaning JIRA and removing a user named "Unassigned
Task"!
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
Hi everyone,
We need to organize JIRA for our 1.0 final release. As the 1.0 release
manager I'm listing in this email my view on what 1.0 should container and
the roadmap. Please let me know all your comments.
Definition
==========
* 1.0 means that the application can be used in production and does
something useful. This is already the case as XWiki is used in lots of
places in production. As a consequence 1.0 should be as close as possible to
the current version in trunk but bugs fixed.
* All usability improvements or new features should thus be moved to 1.1 or
after.
Timeline
========
* 1.0 beta 1 is going to be delivered today (19th of Dec 2006)
* I'd like to allow for 2 weeks releases from now on till 1.0 final. Thus:
- 1.0 beta 2 for the 6th of January 2007 (allowing for 1 week during
Christmas)
- 1.0 rc1 for the 20th of January 2007 and promoted to 1.0 final if stable
after 2 weeks of users using it, i.e. for the 3rd of Feb. 2007
- If rc1 is not stable enough, then we do a rc2 for the 3rd of February
and promote it to 1.0 final if stable after 2 weeks of users using it (i.e.
17th of Feb)
What this means is that for 1.0 final we should add JIRA issues *only* for
doing work till the 20th of January. Evyerthing else must be moved to 1.1
and beyond.
As a technical aside, this means that we will create a 1.0 branch on the 6th
of January 2007.
Let me know if the dates are ok with you.
Contents
========
* Known Bug fixes.
* News bug fixes discovered when user start using 1.0 beta 1
* A few select features. I'm proposing:
- Page Rename. Lots of wikis have this feature and I think that's the
major feature we're lacking right now.
- Email notification when pages are modified (watch feature). Only if we
already have most of the code. Otherwise move to 1.1.
* Documentation, documentation and documentation. This means finishing
moving old.xwiki.org to xwiki.org and documenting new features like the new
{image} macro, etc
* More simple and quick wins macros so that there are less HTML in the
pages. For example: {column} macro to display content on several columns,
{panel} macro to display panels in pages.
* Start packaging applications (blog, search, photos, etc) in XAR files.
This will allow to releases new versions of these even if the core is not
released again.
Note: The number of bugs that we'll fix will only depend on the manpower
that we have. In other words, we'll fix as many as possible but still
release with outstanding bugs. Of course critical bugs needs to be addressed
first.
Let me know if you know of other tasks that you think must absolutely be
done before 1.0 final.
Next steps
==========
Could everyone who's going to work on 1.0 final please review his tasks in
JIRA and move them according to the strategy above, and assign them to
himself/herself? When you do so please remember that you're committing to
working on the issue in the timeframe allocated for the different releases.
It's very important that everyone respects this so that we don't deviate
from our release dates.
Please all target to have a sorted out JIRA till 1.0 final by Friday.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
This is ok for me, I'll finish all bug for B2 ,
but I don't know whether the task Xwiki-292 for incomming email plugin is
neccessary for this release version (I'm afraid it's delay)
> Hi everyone,
>
> We need to organize JIRA for our 1.0 final release. As the 1.0 release
> manager I'm listing in this email my view on what 1.0 should container
> and the roadmap. Please let me know all your comments.
>
> Definition
> ==========
>
> * 1.0 means that the application can be used in production and does
> something useful. This is already the case as XWiki is used in lots of
> places in production. As a consequence 1.0 should be as close as
> possible to the current version in trunk but bugs fixed.
> * All usability improvements or new features should thus be moved to
> 1.1 or after.
>
> Timeline
> ========
>
> * 1.0 beta 1 is going to be delivered today (19th of Dec 2006)
> * I'd like to allow for 2 weeks releases from now on till 1.0 final.
> Thus:
> - 1.0 beta 2 for the 6th of January 2007 (allowing for 1 week during
> Christmas)
> - 1.0 rc1 for the 20th of January 2007 and promoted to 1.0 final if
> stable after 2 weeks of users using it, i.e. for the 3rd of Feb. 2007
> - If rc1 is not stable enough, then we do a rc2 for the 3rd of
> February and promote it to 1.0 final if stable after 2 weeks of users
> using it (i.e.
> 17th of Feb)
>
> What this means is that for 1.0 final we should add JIRA issues *only*
> for doing work till the 20th of January. Evyerthing else must be moved
> to 1.1 and beyond.
>
> As a technical aside, this means that we will create a 1.0 branch on
> the 6th of January 2007.
>
> Let me know if the dates are ok with you.
>
> Contents
> ========
>
> * Known Bug fixes.
> * News bug fixes discovered when user start using 1.0 beta 1
> * A few select features. I'm proposing:
> - Page Rename. Lots of wikis have this feature and I think that's the
> major feature we're lacking right now.
> - Email notification when pages are modified (watch feature). Only if
> we already have most of the code. Otherwise move to 1.1.
> * Documentation, documentation and documentation. This means finishing
> moving old.xwiki.org to xwiki.org and documenting new features like the
> new {image} macro, etc
> * More simple and quick wins macros so that there are less HTML in the
> pages. For example: {column} macro to display content on several
> columns, {panel} macro to display panels in pages.
> * Start packaging applications (blog, search, photos, etc) in XAR
> files.
> This will allow to releases new versions of these even if the core is
> not released again.
>
> Note: The number of bugs that we'll fix will only depend on the
> manpower that we have. In other words, we'll fix as many as possible
> but still release with outstanding bugs. Of course critical bugs needs
> to be addressed first.
>
> Let me know if you know of other tasks that you think must absolutely
> be done before 1.0 final.
>
> Next steps
> ==========
>
> Could everyone who's going to work on 1.0 final please review his tasks
> in JIRA and move them according to the strategy above, and assign them
> to himself/herself? When you do so please remember that you're
> committing to working on the issue in the timeframe allocated for the
> different releases.
> It's very important that everyone respects this so that we don't
> deviate from our release dates.
>
> Please all target to have a sorted out JIRA till 1.0 final by Friday.
>
> Thanks
> -Vincent
I've posted a fix for bug #XWIKI-283, and I hope someone can include it
in the next release.
When trying to show an RSS or RSS2 feed in a wiki page using the {rss}
macro, you will see text like:
"SyndContentImpl.value= ... {blog text} ...
SyndContentImpl.type=text/plain"
Here's the fix to java/com/xpn/xwiki/render/macro/rss/RSSMacro.java.
It applies to xwiki 0.9.743 through subversion June 20, 2006. and to
rome 0.6 through 0.8.
185c184
< .append(NEWLINE).append(entry.getDescription())
---
> .append(NEWLINE).append(entry.getDescription().getValue())
218c217
< .append(NEWLINE).append(entry.getDescription())
---
> .append(NEWLINE).append(entry.getDescription().getValue())
Explanation:
The following code appends the result of
com.sun.syndication.feed.synd.SyndEntry.getDescription(). That would be
fine if getDescription returned a String, but in fact it returns a
feed.synd.SyndContent object.
buf.append(NEWLINE).append("<div class='rssitemdescription'>")
.append(NEWLINE).append(entry.getDescription())
.append(NEWLINE).append("</div>");
My test cases were:
RSS: {rss:feed=http://gigazad.blogspot.com/rss.xml|count=4|full=true}
RSS2:
{rss:feed=http://www.mikegiesbrecht.com/Blog.php?feed_type=rss2|count=1|full=true}
More details below.
--
Trevor Cox
skahasoftware.com
Vancouver, Canada
Ludovic Dubost wrote:
>
> Looks like I missed this one !! There is probably a bug with to little
> encoding of what we get from the feeds.
> You should report an issue in http://jira.xwiki.org
>
> Ludovic
>
> Trevor Cox a écrit :
>
>> Has anyone looked in to RSS2 feeds and the {rss} macro? As far as I
>> can figure out, RSS2 is a new version of RSS. My {rss} macro works
>> fine with RSS feeds that are not labelled RSS2 (although Google seems
>> to block access somehow).
>>
>> I tried upgrading to the latest version of rome.jar, 0.7, but that
>> didn't help. A Google search showed that many XWiki users are having
>> the same problem I am.
>>
>> When I use {rss... |full=true} I see the following text. I've put in
>> bold the text that I should be seeing. The rest is coming from the
>> ROME code (not directly from the RSS source).
>>
>> SyndContentImpl.value=*Be sure to check out my November Newsletter
>> for important tips for Buyers! Click on the Newsletter tab on my
>> Home Page and read about 6 questions a Buyer should ask before making
>> an offer. Read More <http://mikegiesbrecht.com/ViewBlog/14/>*
>> SyndContentImpl.type=text/plain SyndContentImpl.interface=interface
>> com.sun.syndication.feed.synd.SyndContent
>>
>>
>> -Trevor Cox
>> http://skahasoftware.com
>> ------------------------------------------------------------------------
>
Hi everyone,
The XWiki development team is proud to announce the release of XWiki 1.0
Beta 1. This is the first in a series of quick releases that will lead to
XWiki 1.0 Final.
Here are the main changes from the 0.9.x versions:
* New Skin
* Lots of usability improvements
* Importer/Exporter to import and export sets of wiki pages
* XWiki can now work with an empty database
* Pages can be tagged (not documented yet) + basic UI for viewing the tag
cloud
* New WYSIWYG editor (using Tiny MCE v2)
* New Rights editor
* New web site and updated documentation
* Improved programming APIs
* Notion of Panels (porlet-like areas which can be added in menus) + Drag
and drop Panel Wizard to easily customize the displayed Panels
(experimental, works only in Firefox)
* Standalone installer to get up to speed quickly (includes Jetty and HSQL
already set up)
* Attachments versioning
* Section edits (ability to edit only sections of a page)
See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotes for more details
on how to migrate your existing installations.
Please note that we're sending this email to the dev list first so that we
can work together on improving the installation and migration information on
xwiki.org. Let us know about any issue you have.
Thanks
-XWiki Dev Team
Hi,
I'm trying to get XWiki build from source, but I guess I'm doing
something wrong here.
I checked out the following dir:
svn://svn.forge.objectweb.org/svnroot/xwiki/trunk
And tried to do a build via maven (2.0.4), but it fails
mvn compile
Compiling 487 source files to /Users/gerwinbrunner/Documents/
workspace3.2/xwiki/core/target/classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[32,34] package
org.apache.lucene.analysis does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[33,31] package
org.apache.lucene.index does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[34,31] package
org.apache.lucene.index does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[35,32] package
org.apache.lucene.search does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[36,32] package
org.apache.lucene.search does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[37,32] package
org.apache.lucene.search does not exist
/Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/
com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[38,31] package
org.apache.lucene.store does not exist
Could someone give me a hint on what else I need to check out.
I think I'm missing some modules?
MfG
Gerwin Brunner
Bizzons eMarketing GmbH
Nikolaiplatz 4
A-8020 Graz
Tel: +43-1-890-3408-240
Mobile: +43-650-7720448
Hi,
I'm trying once more on this theme... For Xwiki issues are assigned by
default to Jeremi. We know very well that Jeremi isn't going to work on them
and he's busy on other stuff.
I'd like to remove automatic assignments. For this we need to enable "Allow
unassigned issues" to true in JIRA.
I'd like to get help from the community for working on issues and also I
don't have clear visibility on who's going to commit and work on what issue.
I'd much rather see an issue that is unassigned and know that nobody is
going to work on it if we don't find a taker than seeing all issues assigned
which gives a false sense of security.
Here's my +1 to remove automatic assignments, especially as we get to see
the issues on the dev list now.
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
Hi developers,
I see in JIRA that there are still 13 issues for Beta 1. I believe most are
already fixed. Could you please update your JIRA issues ASAP?
The plan is to try releasing Beta 1 early this week (possibly on Tuesday).
We said we would release it last week so we're already late. Let's try to
wrap it up quickly.
Thanks a lot
-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