Thanks. I also interested in knowing what causes the test to fail.
igor.vaynberg wrote:
>
> mvn package -Dmaven.test.skip=true
>
> -igor
>
>
> On 1/3/07, TH Lim <[EMAIL PROTECTED]> wrote:
>>
>>
>> Sorry to cut in :)
>>
>> ant jar is ok after renaming the the DTD file (for all that matters).
mvn package -Dmaven.test.skip=true
-igor
On 1/3/07, TH Lim <[EMAIL PROTECTED]> wrote:
Sorry to cut in :)
ant jar is ok after renaming the the DTD file (for all that matters). I
still encounter problem with "mvn package". I traced the error back to a
test class wicket.markup.html.form.upload
Sorry to cut in :)
ant jar is ok after renaming the the DTD file (for all that matters). I
still encounter problem with "mvn package". I traced the error back to a
test class wicket.markup.html.form.upload.FileUploadFieldTest (line 97-108).
How do I make this test case successful? Thanks.
Fran
> Don't you have some scripts to help you release it? You said something about
> a script for doing the mvn clean site assembly:assembly thing in all
> projects. Can't you add a line or two to unpack the release and run mvn test
> in it? Is there something I/we can help you with in setting up a goo
On 1/3/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
First we need to know why the file needs to be there. Is there any
reason for the dtd to be in the root directory of the distribution, or
can it reside in another location? Is the dtd actually something we
support, and something that works?
First we need to know why the file needs to be there. Is there any
reason for the dtd to be in the root directory of the distribution, or
can it reside in another location? Is the dtd actually something we
support, and something that works?
Second, if we decide that it should be there, then we hav
On 1/3/07, Frank Bille <[EMAIL PROTECTED]> wrote:
Well it's actually my fault. When I created that unit test I assumed that
we inclueded wicket-xhtml1-strict.dtd in the release. You should be fine
just putting the a file in the root directory (C:\workspace\wicket-1.2.3 )
and call it wicket-xhtml
Well it's actually my fault. When I created that unit test I assumed that we
inclueded wicket-xhtml1-strict.dtd in the release. You should be fine just
putting the a file in the root directory (C:\workspace\wicket-1.2.3) and
call it wicket-xhtml1-strict.dtd. It's not the content that matters but t
I am compiling wicket-1.2.3 from the zip file using "ant jar" and the
compilation was terminated unsuccessfully with the message "[junit] File
does not exists. You must provide an existing file:
C:\workspace\wicket-1.2.3\wicket-xhtml1-strict.dtd". I found
wicket-1.0-xhtml11.dtd in the directories
We don't use ant ourselves. The dtd file should be in the root
directory of the zip. Apparently the assembly descriptor used to build
the download archive didn't pick it up. grmbl.
You can get the dtd from svn or use the one supplied in the wicket-1.2.3 zip.
It hasn't been updated for a while (re
Hmmm, anyone ?
Can anybody pass the tests on wicket-1.2.4 with ant ? I'm using building a
fresh distro with ant and the testInternalDetach test fails. Its looking for
the wicket-xhtml1-strict.dtd file and can't find it .
On 1/1/07, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote:
The FileUploadFiel
The FileUploadFieldTest try's to upload a non-existent file (
wicket-xhtml1-strict.dtd ) Where should this file be ? I'm testing using ant
jar task.
Iman
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.
12 matches
Mail list logo