(Probably?) because that way we can copy the version info from the
maven definition file and thus do not do things double.

Eelco

On 3/30/06, cowwoc <[EMAIL PROTECTED]> wrote:
>
>         If it is internal, why read it from a property file at all? Why isn't
> this hard-coded into the code?
>
> Gili
>
> Igor Vaynberg wrote:
> > i dont see a problem with having a wicket-internal.properties. this can
> > be used for all the internal things we use, version now, and maybe some
> > other stuff. this will only be used by wicket so we can be guaranteed no
> > collissions. lets keep wicket.properties for more general things.
> >
> > -Igor
> >
> >
> > On 3/30/06, *Martijn Dashorst* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >     So how do we process the wicket.properties files for getting the
> >     initializers?
> >
> >     That does work for the initializers for all the new jar file, why
> >     not for wicket.version?
> >
> >
> >     Martijn
> >
> >
> >     On 3/30/06, *Johan Compagner* <[EMAIL PROTECTED]
> >     <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >         yes exactly like igors says,.
> >         Because we are looking up for a wicket properties file (and only
> >         one) which one does it return?? It could be the one from the
> >         extentions
> >         or the one users do provide. We don't have control of that.
> >
> >         We need one single unique properties file for that. Else we
> >         can't load it and be sure we have the right one just like jan
> >         was saying.
> >         I already mentioned this before in an email but i think i send
> >         it to maurice by mistake.
> >
> >         johan
> >
> >
> >         On 3/30/06, * Igor Vaynberg* <[EMAIL PROTECTED]
> >         <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >             but the problem with wicket.properties is that it is also
> >             used by our users! what we need is a unique property file
> >             that our users wont have in their classpath - so that we can
> >             be sure we are reading the proper one.
> >
> >             call it wicket-internal.properties or some such.
> >
> >             -Igor
> >
> >
> >
> >             On 3/30/06, *Martijn Dashorst* <[EMAIL PROTECTED]
> >             <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >                 So you propose that for every property we want to put
> >                 into Wicket we should add a new property file?
> >                 wicket.properties is already there. Why introduce
> >                 another file?
> >
> >                 Martijn
> >
> >
> >                 On 3/30/06, *Johan Compagner* <[EMAIL PROTECTED]
> >                 <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >                     yes i think i already did mention that before
> >                     it should be looking for an unique text file. like
> >                     wicket-version.properties.
> >
> >                     Can maven generate that file martijn? So that we
> >                     look for this?
> >
> >                     johan
> >
> >
> >
> >                     On 3/30/06, *jan_bar* <[EMAIL PROTECTED]
> >                     <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >                         Hi,
> >
> >                         I tried FrameworkSettings.getVersion(), but it
> >                         seems to read
> >                         wicket.properties of my application instead from
> >                         wicketXX.jar. Does it work
> >                         for you?
> >
> >                         Thanks, Jan
> >
> >
> >
> >
> >
> >                         
> > -------------------------------------------------------
> >
> >                         This SF.Net email is sponsored by xPML, a
> >                         groundbreaking scripting language
> >                         that extends applications into web and mobile
> >                         media. Attend the live webcast
> >                         and join the prime developer group breaking into
> >                         this new coding territory!
> >                         
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> >                         
> > <http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642>
> >                         _______________________________________________
> >                         Wicket-user mailing list
> >                         [email protected]
> >                         <mailto:[email protected]>
> >                         
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >                         
> > <https://lists.sourceforge.net/lists/listinfo/wicket-user>
> >
> >
> >
> >
> >
> >                 --
> >                 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
> >
> >
>
>
>
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to