Hi,
I've created an XWiki plugin, which uses a whole lot of frameworks to
do it's job, including
WebObjects, ProjectWonder and some of our own frameworks. It's running
fine in Eclipse.
When I package the resulting webapp from the workspace's server area
(.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/xe-
debug-web)
into a war file, I can deploy the result in a webserver.
Now I would like to be able to package the xe-debug-web from the
command line
or Eclipse into a .war. However: When I invoke mvn clean package (or
any other
mvn command for that matter) inside the xe-debug-web project
directory, i get the
following error message:
mvn package :
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: xe-debug-web:xe-debug-web
Reason: Parent: null:xwiki-web-standard:war:null of project: xe-debug-
web:xe-debug-web has wrong packaging: war. Must be 'pom'. for project
xe-debug-web:xe-debug-web
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parent: null:xwiki-
web-standard:war:null of project: xe-debug-web:xe-debug-web has wrong
packaging: war. Must be 'pom'. for project xe-debug-web:xe-debug-web
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Parent:
null:xwiki-web-standard:war:null of project: xe-debug-web:xe-debug-web
has wrong packaging: war. Must be 'pom'. for project xe-debug-web:xe-
debug-web
at
org
.apache
.maven
.project
.DefaultMavenProjectBuilder
.assembleLineage(DefaultMavenProjectBuilder.java:1377)
at
org
.apache
.maven
.project
.DefaultMavenProjectBuilder
.buildInternal(DefaultMavenProjectBuilder.java:821)
at
org
.apache
.maven
.project
.DefaultMavenProjectBuilder
.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
at
org
.apache
.maven
.project
.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
... 11 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Dec 03 18:41:14 CET 2008
[INFO] Final Memory: 1M/2M
[INFO]
------------------------------------------------------------------------
I don't know what to do about this message. So my thought was to
create a Maven goal
in Eclipse from the run configurations. However, the 'war' goal seems
to be quite fussy
about the layout, and the xe-debug-web project layout does not to be
satisfactory:
...
[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[xe-debug-web] in [/Users/simon/Projects/
Kontrast/MavenWorkspace/xe-debug-web/target/xe-debug-web-1.6.1]
[INFO] Processing war project
[INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/
MavenWorkspace/xe-debug-web/target/maven-shared-archive-resources] to[/
Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/target/xe-
debug-web-1.6.1]
[INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/
MavenWorkspace/xe-debug-web/target/maven-shared-archive-resources/META-
INF] to[/Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/
target/xe-debug-web-1.6.1]
[INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/
MavenWorkspace/xe-debug-web/src/main/webInfResources] to[/Users/simon/
Projects/Kontrast/MavenWorkspace/xe-debug-web/target/xe-debug-web-1.6.1]
Exception in thread "main" java.lang.IllegalStateException: basedir /
Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/src/main/
webInfResources does not exist
at
org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:
550)
...
Since both approaches failed, I need some advice on how to package the
xe-debug-web into
a proper WAR file again.
All pointers much appreciated,
J.L.Simon
Hi,
Please unsubscribe my Email ID from this blog.I dnt want further mails.
regards,
Deepak Sharma
ASE
Tata Consultancy Services
,Phase IV,
Gurgaon
Gurgaon - 122001,Haryana
India
Cell:- 9911502444
Mailto: deepak24.s(a)tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Outsourcing
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
Hi all,
We have setup the new translation tool on a production server and we are
now looking for volunteers to give it a test drive and start updating
the translations of the XWiki Core.
The new tool is at
http://l10n.xwiki.org
You will need to create an account on this wiki (the xwiki.org does not
yet work, but we plan to connect it to xwiki.org using the new Open ID
implementation done in the Summer of Code).
The first thing that we can start with is working on the empty
translations. For example here are the pages to modify the empty
translations for a few languages
German:
http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty…
French:
http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty…
Spanish: German:
http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty…
Polish: German:
http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty…
You can view the full list at
German: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources
and click on "View Empty" next to your favorite language.
Currently there is no locking mecanism, so I hope we won't have
conflicts will working on this. The good thing is that of course
everything is kept in wiki style so with versioning.
Let us know who can test drive the application. Make sure you are
putting in real translations since we want to use the result for real !
Once we start getting some updates I'll document the review process so
that we can also start doing that. For reviews we will 'elect' reviewers
that will have the right to review. If you are volunteer for review,
please tell us by responding to this email.
Thanks
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi,
I'd like to suggest to postpone the release by a couple of days. The
reason is -- as explained in a previous email -- that in its current
state the WYSIWYG 2.0 :
1) Is still causing IE6 crashes on key press (Blocker). It has been
preventing testing on this browser during the last couple of weeks and
last commit from Marius doesn't help (again, IE is a pain). See
http://jira.xwiki.org/jira/browse/XWIKI-2915
2) Can't be considered as a valid replacement of the WYSIWYG 1.0
since the image and table plugins are deactivated by default
(XWIKI-2917 and XWIKI-2916). See pending issues here :
http://tinyurl.com/6hsaqg
If it's ok for everyone I'd like to define december 5th as the new
release date for XE 1.7 ?
Here's my +1.
Thanks,
JV.
General wiki explorer UI :
3) Three +1
4) Five +1 (WINNER)
Tree add options :
A) Four +1 (WINNER)
B) One +1
C) Three +1
JV.
On Thu, Nov 27, 2008 at 7:37 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
> On Tue, Nov 25, 2008 at 5:05 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
>> In a previous thread we've discussed about how to add a link in the
>> WYSIWYG editor, and more generally, how to browse the wiki from a
>> WYSIWYG dialog box (See http://markmail.org/message/tyxrcr24w3n6m2pn
>> for more details).
>>
>> After some thinking and a discussion with Laurent Lunati, I'd like to
>> suggest a 3rd way of browsing the wiki from the WYSIWYG: an enhanced
>> tree menu.
>>
>
> After some more thinking and discussion with Laurent Lunati I've made
> a mockup of a 4th wiki explorer :
> http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorWikiExplorer#H42…
>
> It combines the best of the tree and wizard proposals :
>
> * Easy to use: users are guided throughout the process, one action at a time
> * The dialog size is fixed, action buttons are always at the same
> position on screen
> * The dialog doesn't looked oversized compared to the WYSIWYG
> * Small footprint: can be used even on low resolution displays
> * Since it's a wizard it's highly extensible
> * Scalable : we can have multiple wikis + spaces (even a space hierarchy)
> * Allow to display parent/child relationships between pages (thus
> allowing to handle a lot of pages in a space)
> * Allows the user to see where he is currently located in the wiki
> (default selection)
>
> Here's my +1 for 4).
>
> ps: I consider that the discussion about the position of the add page
> / add spaces buttons is not over.
>
> JV.
>
Hi there,
With XE 1.7 we're going to release some features that don't have the
final planned UI (insert link, image, macro, table for example).
We're still discussing the final UI designs but I'd like that we get
started doing 2 things:
* prepare a roadmap for finishing their definition and set milestones
so that we don't drag on forever
* prepare an implementation roadmap with dates and with whom will be
able to implement them
Re the implementation roadmap I feel it would be good to (iteratively)
release the UIs in 1.7.x releases (1.7.1, 1.7.2, etc) as fast as we
can. The reason is that we initially wanted to have them in 1.7 final
and we're late since the wysiwyg implementation took longer than
planned. Waiting for 1.8 would be too long I think.
Ideally IMO it would be good if we could have most of them done before
December end.
We need to know if that's possible and define a roadmap.
WDYT?
Thanks
-Vincent
Hello xwikiers,
the page at
http://platform.xwiki.org/xwiki/bin/view/DevGuide/Notifications
is really nice and shows a real nice pearl of XWiki.
I did similarly and my notifier seems to run smoothly.
I would like to know, however, what is the way to make sure that a
notifier (an implementation of XWikiDocChangeNotificationInterface) is
running at every restart of our XWiki.
I tried to add the fullname of either the velocity (the "starter") or
the Groovy pages into that line and restarting but my notifier didn't
seem to have been running after that.
What is the correct way?
It should definitely be documented at the pircbot page.
thanks in advance
paul
Fabio,
I would be eager to test it, especially with the changing java
architectures on the mac nowadays (basically the 64-bit/32-bit
switch). As soon as you have a release candidate I'll give it a try.
paul
Le 26-nov.-08 à 17:23, Fabio Mancinelli a écrit :
> Dear all,
>
> I would like to release XEclipse soon. During the last days I've fixed
> many of the outstanding bugs thanks also to the effective
> collaboration
> of Eduard Moraru who provided a lot of patches and I think that now
> XEclipse is pretty stable, usable and functional.
>
> This release incorporates a lot of features that have been implemented
> during the last months. In particular a better integration with the
> Eclipse ecosystem, object editor, translation management, page
> history,
> syntax highlighting and completion (thanks to the work done by Malaka
> during the last GSoC and Venkatesh) and many other improvements.
>
> There are still many things to do but I think that it's a priority to
> have a new version out asap in order to have more feedbacks from users
> and to build upon it.
>
> Due to some previous engagements I think I will be able to release
> it on
> Friday or during the weekend.
Hi,
the new WYSIWYG is still under heavy development, here are some
estimations of its features completion :
* Standard features : 75%. Implemented : bold, italics, underline,
strikethrough, subscript, superscript, unordered list, ordered list,
titles (h1,h2,etc), indent, outdent, ruler, special chars. Remaining :
alignment, verbatim, quote, definition lists, custom parameters like
(% style="color:red" %). Some bugs left too.
* Link : 90%. Allow internal/external/email link insertion. Missing
options. No automated tests.
* Image : 40%. Allow image insertion from any document, image
uploading and resizing. Still buggy. Missing options. No automated
tests.
* Table : 50%. Doesn't work with IE. Missing options. No automated tests.
* Macro : 0%.
* Import: 0%.
In its current state the WYSIWYG 2.0 :
- can't be considered as a valid replacement of the WYSIWYG 1.0
(image and table plugins deactivated by default),
- was causing IE6 crashes after a few seconds of use, this has been
fixed by the last commit from Marius a few minutes ago but has been
preventing IE6 testing for a couple of weeks.
I'm suggesting to postpone XE 1.7 release by a few days, I'll write
another email about this.
Note that the UI of all those features (buttons, dialog boxes, etc) is
not final since the discussion about their ergonomics is still
ongoing.
See the "Need roadmap for new WYSIWYG UI needed" email.
Thanks,
JV.
On Tue, Dec 2, 2008 at 11:17 PM, SVN fmancinelli <
sandbox-notifications(a)xwiki.org> wrote:
> Author: fmancinelli
> Date: 2008-12-02 18:47:06 +0100 (Tue, 02 Dec 2008)
> New Revision: 14514
>
> Added:
> sandbox/xwiki-core-rest/.classpath
> sandbox/xwiki-core-rest/.project
> sandbox/xwiki-core-rest/.settings/
> sandbox/xwiki-core-rest/.settings/org.eclipse.jdt.core.prefs
> sandbox/xwiki-core-rest/.settings/org.eclipse.wst.common.component
>
> sandbox/xwiki-core-rest/.settings/org.eclipse.wst.common.project.facet.core.xml
> sandbox/xwiki-core-rest/.settings/org.maven.ide.eclipse.prefs
I think it's not ok to commit these files. May be it's ok for sandbox ?
- Asiri
