I'd also like to try a full-fledged zero-config MailReader.
On 1/31/07, Don Brown <[EMAIL PROTECTED]> wrote:
I think we should use annotations where ever possible and the blank
archetype seems like a good place to start.
Don
+1!
Ian Roughley schrieb:
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of the
bootstap tutorial, I didn't see any explicit reference to needing to
move the files from the com/myComp/myApp directory into the mirrored
class
I think we should use annotations where ever possible and the blank
archetype seems like a good place to start.
Don
Ian Roughley wrote:
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of
the bootstap tutorial, I didn't see a
Ok Ted, I'll only modify the starter application.
However, looking through the validation and localization sections of the
bootstap tutorial, I didn't see any explicit reference to needing to
move the files from the com/myComp/myApp directory into the mirrored
class directory, if you used the
The blank application contains the files from the bootstrap tutorial.
* http://struts.apache.org/2.x/docs/bootstrap.html
The tutorial files are put "out of the way" so that people don't need
to delete them just to get started. But, they are still there for
reference. So, no, don't make the same
I was going to run with this. Did you want me to make the same
deletions to the blank application? After all, since they are not in
the correct directory, the files are not being used.
/Ian
Ted Husted wrote:
Once things are sorted out, it would be nice to revert it to match the
Struts Blan
Once things are sorted out, it would be nice to revert it to match the
Struts Blank application, but for now, it seems like we should strip
it down.
On 1/30/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
I have been looking through the s2 maven archetypes, and would like to
propose that we don't in
+1
On 1/30/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
I have been looking through the s2 maven archetypes, and would like to
propose that we don't include resources that are at a package level
(i.e. validation and conversion). The reason being that maven2
currently does not support this featur
I have been looking through the s2 maven archetypes, and would like to
propose that we don't include resources that are at a package level
(i.e. validation and conversion). The reason being that maven2
currently does not support this feature (see
http://jira.codehaus.org/browse/ARCHETYPE-54),
