I just wanted to report back and say that, after our installer team
updated the distribution to maintain the individual JARs (and thus not
overwrite the files with clashing filenames), that solved the problem!
Thanks to Martin Grigorov and Andrew Geery for helping point me in the
direction of t
https://issues.apache.org/jira/browse/WICKET-5713
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Oct 1, 2014 at 11:11 PM, Garret Wilson
wrote:
> On 10/1/2014 5:17 PM, Martin Grigorov wrote:
>
>> ...
>> Are you aware of JDK APIs (e.g. ClassLoader) or Servle
On 10/1/2014 5:17 PM, Martin Grigorov wrote:
...
Are you aware of JDK APIs (e.g. ClassLoader) or Servlet APIs (e.g.
SevletContext) that make it simple to find the list of resources in a
folder in the classpath ?
E.g. "give me a list of all files with extension '.properties' in
/META-INF/wicket/ ?
On Wed, Oct 1, 2014 at 9:49 PM, Garret Wilson
wrote:
> On 10/1/2014 3:31 PM, Martin Grigorov wrote:
>
>> Apache Isis uses
>> http://simplericity.org/jetty-console/jetty-console-maven-plugin/ to
>> generate an executable .jar that contains all dependencies in WEB-INF/lib/
>> folder inside. Exactly
On 10/1/2014 3:31 PM, Martin Grigorov wrote:
Apache Isis uses
http://simplericity.org/jetty-console/jetty-console-maven-plugin/ to
generate an executable .jar that contains all dependencies in WEB-INF/lib/
folder inside. Exactly as you need it.
Yeah, in another subproject I had already created
Apache Isis uses
http://simplericity.org/jetty-console/jetty-console-maven-plugin/ to
generate an executable .jar that contains all dependencies in WEB-INF/lib/
folder inside. Exactly as you need it.
About IIinitializer:
this is the simple plugin system Wicket uses. It loads all
/wicket.properties
I think I've found the source of the problem (even though I don't
understand the internal details). Our installer creates an uber-JAR that
has all the dependencies exploded and then placed inside a single JAR
file. I looked inside wicket-extensions-7.0.0-M3.jar, and it has a file
wicket.propert
The .properties file is packed inside wicket-extensions.jar, not in his
application.
I have no other ideas but to attach a remote debugger
to
org.apache.wicket.resource.loader.InitializerStringResourceLoader#loadStringResource(java.lang.Class,
java.lang.String, java.util.Locale, java.lang.String,
As a sanity check, is the property file with the property
UploadProgressBar.starting
in the jar file? Perhaps it didn't get copied over by the Maven build
process into the jar but the IDE was properly copying it over...
Andrew
On Wed, Oct 1, 2014 at 11:38 AM, Garret Wilson
wrote:
> On 10/1/201
On 10/1/2014 12:33 PM, Martin Grigorov wrote:
Hi,
Do you by chance manipulate the list of IStringResourceLoader's in
DEPLOYMENT mode ?
I don't think I touched anything related to IStringResourceLoader. The
only thing I've done relating to modes is this:
//turn on Wicket development mo
Hi,
Do you by chance manipulate the list of IStringResourceLoader's in
DEPLOYMENT mode ?
See org.apache.wicket.settings.ResourceSettings#getStringResourceLoaders()
org.apache.wicket.resource.loader.InitializerStringResourceLoader is
responsible to load the resource bundle
wicket-extensions/src/ma
In data domenica 20 gennaio 2013 17:16:48, Sven Meier ha scritto:
> If you don't provide a filename to the ExportToolbar constructor, a
> String resource with key "datatable.export-file-name" is used.
>
> Normally a default is provided here:
>
> /wicket-extensions/src/main/java/org/apache/wicket/
If you don't provide a filename to the ExportToolbar constructor, a
String resource with key "datatable.export-file-name" is used.
Normally a default is provided here:
/wicket-extensions/src/main/java/org/apache/wicket/extensions/Initializer.properties
I'm not sure why this is not present in y
13 matches
Mail list logo