Hello,
i downloaded the latest wicket-*-1.2-rc3 drop and installed everything.
I get the following error in wicket-examples-1.2-rc3 in ParsedHTML.java:
WebTable.TableRow cannot be resolved to a type.
Juergen Donnerstag has described extensively his problems with that.
Has anybody else got the
WebTable is from httpunit and we are using 1.6.1 currently. In case
you are using maven the jar should be downloaded automatically. Why
did you download the jars yourself?
Juergen
On 5/3/06, middledot [EMAIL PROTECTED] wrote:
Hello,
i downloaded the latest wicket-*-1.2-rc3 drop and installed
Hello Jurgen,
I did not download any jars. I've downloaded the latest drop rc3 and
installed in Eclipse.
I thought that the drop is designed in such a way so that it's ready to go
in Eclipse without any further work, apart maybe from some dependencies.
I'm sure that a lot of people coming to
Could be, I'm not sure. Matjin is our build master may be he can
answer the question.
Juergen
On 5/3/06, middledot [EMAIL PROTECTED] wrote:
Hello Jurgen,
I did not download any jars. I've downloaded the latest drop rc3 and
installed in Eclipse.
I thought that the drop is designed in such a
it is given you have the jars :)you should do mvn eclipse:eclipse - that will download all the jars and build an eclipse project files.-IgorOn 5/3/06,
Juergen Donnerstag [EMAIL PROTECTED] wrote:
Could be, I'm not sure. Matjin is our build master may be he cananswer the question.JuergenOn 5/3/06,
Ah... I think I know the problem...The scope of the jwebunit stuff is 'TEST'. This means that the files don't end up in the final zip. Maven 2 makes life so much easier :-)If you need the jars to work *now* I suggest what Igor mentioned: running mvn eclipse:eclipse in the root folder.
MartijnOn
Hi,
i don't want to be a nuisance but since the release of Wicket 1.2 is
imminent and you have requested to submit bugs and issues, i've decided to
put myself in a position of somewone who's just heard about wicket and wants
to give it a try. So i decided to install all wicket libraries from
Hi Les,Thanks for testing them all out... With all these packages to build, I hardly get to doing this myself (as you have unfortunately discovered). And you're not being a nuisance *AT ALL*. This is why we release often, so these problems can get out of the way. Really thanks for checking this
i launched eclipse, installed all the projects in eclipse with new-newproject
most packages compiled but some needed extra *.jarsOnce all needed jars were installed all compiled.we ship eclipse project files with all our projects that are ready to go so why would you set up the project yourself?
Hi,
Thanks Igor. Your suggestion fixed the problem.
I think that src/main/resources folder should be included to the buildpath
automatically.
I know what you are saying Igor. However, if someone downloads the released
packages such as for example the latest rc3 drop then you would expect that
I think that src/main/resources folder should be included to the buildpathautomatically.
it is in the eclipse project files we ship. of course if you are creating the eclipse project yourself you have to add it manually, no way for us to do it automatically.-Igor
I don't think the .classpath and .project files are actually in the zip and tar.gz files.MartijnOn 5/3/06, Igor Vaynberg
[EMAIL PROTECTED] wrote:
I think that src/main/resources folder should be included to the buildpathautomatically.
it is in the eclipse project files we ship. of course if you
well, in that case you either have to know mvn eclipse:eclipse or know to add the resources folder to the classpath.why dont we include those files?-IgorOn 5/3/06,
Martijn Dashorst [EMAIL PROTECTED] wrote:
I don't think the .classpath and .project files are actually in the zip and tar.gz
They rely on the maven repository to be present. As mentioned earlier, not everybody wants to use maven. As core developers we need that standard, and as such our build procedure is focused around that. This doesn't mean that we should impose maven on *all* our users.
As a courtesy we package all
14 matches
Mail list logo