Re: [Wicket-user] WebTable.TableRow

[Martijn Dashorst]

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 dependencies into the zip and I also include a working build.xml file in the root folder of the downloaded packages for those that love ant.

The supplied non-maven project files should use those libraries found in the lib directory. In the maven 1 days, I had the release build for the quickstart project generate the eclipse files for me, but that is not possible anymore (no more jelly).

Most IDE's auto discover the supplied lib files. The only two caveats currently are:
1. the special resource directory for the spring projects isn't automatically discovered by eclipse et al. Perhaps if we add the directory to the build.xml file eclipse, IDEA and netbeans will pick it up.

2. the dependencies with scope 'test' are not packaged.

Martijn

On 5/3/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:

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?

-Igor

On 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 files.

Martijn

On 5/3/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote:

I think that src/main/resources folder should be included to the buildpath
automatically.

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

--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org

--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org