Ant is for n00bz... real men use commandline cp and javac, or if
you're really good just type in byte code directly.
Martijn
On Sat, Mar 21, 2009 at 8:23 AM, Igor Vaynberg wrote:
> the real question is, where do the ant folks keep their resources? :)
>
> -igor
>
> On Fri, Mar 20, 2009 at 10:58 P
Laugh.
Don't start that now!
- Brill Pappin
Sent from my mobile.
On 21-Mar-09, at 3:23 AM, Igor Vaynberg wrote:
the real question is, where do the ant folks keep their resources? :)
-igor
On Fri, Mar 20, 2009 at 10:58 PM, Brill Pappin
wrote:
Ahh... yes of course.
I was hoping for a
the real question is, where do the ant folks keep their resources? :)
-igor
On Fri, Mar 20, 2009 at 10:58 PM, Brill Pappin wrote:
> Ahh... yes of course.
>
> I was hoping for a switch that would put the html there as well, and not
> include the extra resource config :)
> Oh well... its not too b
Ahh... yes of course.
I was hoping for a switch that would put the html there as well, and
not include the extra resource config :)
Oh well... its not too big a deal.
- Brill
On 21-Mar-09, at 1:44 AM, James Carman wrote:
On Sat, Mar 21, 2009 at 1:35 AM, Brill Pappin wrote:
Re: "The quick
On Sat, Mar 21, 2009 at 1:35 AM, Brill Pappin wrote:
> Re: "The quickstart allows both."
> Does it? I missed that feature but it would be very handy!
Sure! Take a look at a generated quickstart. There's a
src/main/resources directory with a log4j.properties file in there
(which gets copied over
Re: "The quickstart allows both."
Does it? I missed that feature but it would be very handy!
The only doc I see is the one at:
http://wicket.apache.org/quickstart.html
What options do i pass to get it to do that?
and yes in that case it's an established project... I think this
thread has got
On Sat, Mar 21, 2009 at 1:15 AM, Brill Pappin wrote:
> In fact there have been several instances where having the resources and
> java separate has been helpful to me and the folks I work with. If an
> example is needed, the case were the HTML must be delivered to non
> programmers and then reinte
Now there is a sensible argument!
I've been thinking of doing that exact thing for clarity as the
project gets big, where the integral HTML files that have a 1:1
relationship to the code stay in the src/main/java and the other
resources that are *not* required for operation (like the proper
On 20-Mar-09, at 11:51 AM, Martijn Dashorst wrote:
I don't want that. If someone is anal about what maven is expecting,
then it is their problem. I am in the business of making the best
wicket development experience, from a Wicket perspective. We're using
maven as a tool, we're not in the busin
+1. Wicket IMHO does it the right way for its particular situation.
Wicket differs from most Java project by the sheer number of resources
and by their 1:1 correspondence with Java classes. Maven, I think, is
optimized more for the more common case where a project has only a
handful of resources t
I don't want that. If someone is anal about what maven is expecting,
then it is their problem. I am in the business of making the best
wicket development experience, from a Wicket perspective. We're using
maven as a tool, we're not in the business of supplying maven with new
users.
Putting all res
It's not forcing you to put your stuff there. It merely *also* allows
you to put it there. It's also easy to remove (perhaps we could add a
comment saying to remove it if they want).
On Fri, Mar 20, 2009 at 11:31 AM, Brill Pappin wrote:
> I love the use of the package structure to keep the file
But thats not a fix, thats adding crap to my build I don't want or need.
Maven allows you to do things like that, because frankly no one would
use it if it didn't... have you ever tried to port a legacy app to
Maven?
There is no "assumption" here. See:
http://maven.apache.org/guides/introduc
I love the use of the package structure to keep the file together,
However I don't think we're talking about moving the HTML to a
different structure, they are all still in the same package (although
I've come across cases where I *do* need it outside the package
structure for political and/
chuckle,
semantics :)
However as a long time maven user, I expect it to do one thing and it
does another.
I prefer my content separate and so I don't use the archetype because
it takes too long to fix the module and remove all the un-needed
additions than it does to just create the module b
On Fri, Mar 20, 2009 at 9:35 AM, Wilhelmsen Tor Iver wrote:
> But if it *breaks* the assumptions made by all other plugins used by
> Maven as a build tool, is it then not an archetype that *abuses* Maven
> as a build tool? :)
It also *fixes* it by using a resource declaration. If the maven
commu
> There is no sane reason why anyone would put the html, js,
> css and properties resources in any place except *next* to
> the corresponding.java file. Your .java file can not function
> without the .html file. Your component will fail if the
> .properties file is not available. When the js fi
There is no sane reason why anyone would put the html, js, css and
properties resources in any place except *next* to the
corresponding.java file. Your .java file can not function without the
.html file. Your component will fail if the .properties file is not
available. When the js file can't be fo
> It's a *wicket* archetype that uses Maven as a build tool.
But if it *breaks* the assumptions made by all other plugins used by
Maven as a build tool, is it then not an archetype that *abuses* Maven
as a build tool? :)
What other contexts would you want to use this *wicket* archetype that
does
It's a *wicket* archetype that uses Maven as a build tool.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Mar 19, 2009 at 8:30 PM, Brill Pappin wrote:
> It's a Maven archetype is it not?
>
> - Brill
>
>
> On 19-Mar-09, at 3:22 PM, Jeremy Thomerson wrote:
>
>
>>>
>>> On the subject
It's a Maven archetype is it not?
- Brill
On 19-Mar-09, at 3:22 PM, Jeremy Thomerson wrote:
On the subject of the archetype though, it *should* be doing the
maven
standard thing by default... maybe offering you a choice but the
default
should be into the resources directory.
Why shou
>
>
> On the subject of the archetype though, it *should* be doing the maven
> standard thing by default... maybe offering you a choice but the default
> should be into the resources directory.
>
Why should the *wicket* archetype be doing the *maven* standard thing? This
is the wicket standard wa
On Thu, Mar 19, 2009 at 3:11 PM, Brill Pappin wrote:
> On the subject of the archetype though, it *should* be doing the maven
> standard thing by default... maybe offering you a choice but the default
> should be into the resources directory.
I didn't like it at first, being a maven user, but it
Yes I know, and I have to undo all its extra crap and move the files
to the right place every time...
Its annoying enough that I don't really use it any more because it
takes twice as long to get things back to were they should be than it
does to just create the darn module.
- brill
On 19-
unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/How-can-I-share-text-resources-with-multiple-web-applications--tp22
It also adds a resources specification to fix it.
On Wed, Mar 18, 2009 at 10:36 PM, Brill Pappin wrote:
> With Maven, non compiled files should be in src/main/resources
>
> The quickstart archetype actually does the *wrong* thing and puts them in
> with the java files.
>
> - Brill Pappin
>
> On 1
sed by: java.util.MissingResourceException: Unable to find
>> >>>> property: '
>> >>>> squeeze.presented.by' for component:
>> >>> [class=com.max.web.page.bizopp1Page]
>> >>>>
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/How-can-I-share-text-resources-with-multiple-web-applications--tp22549375p22592795.html
Sent from the Wicke
t;>> at org.apache.wicket.Localizer.getString(Localizer.java:269)
> >>>> .
> >>>>
> >>>>
> >>>> Is there any way to make this work? Is there another approach
> >>>> where I
>
work? Is there another approach
>>>> where I
>>> can
>>>> share the text between these projects?
>>>>
>>>> Thanks for any suggestions.
>>>> Trent
>>>>
>>>
>>> -
With Maven, non compiled files should be in src/main/resources
The quickstart archetype actually does the *wrong* thing and puts them
in with the java files.
- Brill Pappin
On 18-Mar-09, at 4:19 PM, Trent Larson wrote:
Thanks for the suggestion.
For posterity's sake: my problem was actual
Thanks for the suggestion.
For posterity's sake: my problem was actually with the Maven 2 build, where
it ignored the properties file (located in with the Java files) when it
built the jar project.
Trent
On Mon, Mar 16, 2009 at 5:02 PM, Igor Vaynberg wrote:
> see iresourcesettings#addstringres
see iresourcesettings#addstringresourceloader()
make one that loads your properties from some file you keep on the classpath
-igor
On Mon, Mar 16, 2009 at 4:00 PM, Trent Larson wrote:
> I have 2 web applications, and I would like to allow them to share the same
> text files. The only way I've
I have 2 web applications, and I would like to allow them to share the same
text files. The only way I've found is to make each WebApplication class
extend a common ParentApplication class and make a
ParentApplication.properties file to contain the common text; then I package
the common ParentAppl
34 matches
Mail list logo
