Hey Paul. On Mon, Jul 8, 2013 at 9:24 AM, Paul Borș <[email protected]> wrote:
> See the Wicket Free Guid section on the properties files. > https://wicket-guide.googlecode.com/files/Wicket%20free%20guide.pdf#page92 > > Long story short, you can define the language pack at your application > level and overrite the default labels Wicket ships with. > Per say, i use your "ubber" properties file (master properties file) > because of our translatiomn firm ;) > William talks about wicket.properties (IInitializer), not Application.properties. > Have a great day, > Paul Bors > > On Jul 7, 2013, at 5:35 PM, William Speirs <[email protected]> wrote: > > > I'm attempting to create an uber JAR using the Maven shade plugin and > > running into an issue shading wicket, wicket-extensions and > > wicket-devutils. All 3 of these module contain a wicket.properties file > > that point at their respective Initializers. The problem > > is that when I > > create the shaded JAR, the wicket.properties files all want to live in > the > > same place and overwrite each other. I can combine them into a single > > wicket.properties file, but when the properties are loaded > > via addInitializer(properties.getProperty("initializer")); only the last > > one in the file is used. > > > > Has anyone ever created an uber JAR with wicket and wicket-extensions (I > > can drop wicket-devutils if needed)? If so, how did you do it? > > > > If I needed to hack this together, knowing the names of the Initializers, > > can I call them "manually"? > I don't see another solution. Call them manually in the beginning of your MyApp#init() method. > > > > Thanks... > > > > Bill- >
