The problem with Struts1 is that its now a maven2 build and I don't
think gump yet supports maven2.
Niall
On 1/20/07, Nathan Bubna [EMAIL PROTECTED] wrote:
VelocityTools is getting a Gump failure because we recently upgraded
our Validator tool to use the
I'm on my way out of town, and I won't be able to run another release
for at least a week.
At this point, I think we should let Struts 2.0.3 lie. If we need to
roll a Stuts 2.0.4 to go past beta, because of the Struts Annotation
tagging, then so be it. But, in the meantime, perhaps we can get
As mentioned in the Struts-Annotations thread, there will be an issue
with building applications with Maven, in that it will pull down an
unnecessary snapshot of the struts-annotatios JAR.
For now, I think we should let Struts 2.0.3 lie as a test build. When
we sort out the build issues, we can
On 1/20/07, Ted Husted [EMAIL PROTECTED] wrote:
At this point, I think we should let Struts 2.0.3 lie. If we need to
roll a Stuts 2.0.4 to go past beta, because of the Struts Annotation
tagging, then so be it. But, in the meantime, perhaps we can get some
people to take 2.0.3 for a spin to see
That's what I saw the other day while creating an app with the archetype.
musachy
On 1/19/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 1/19/07, Musachy Barroso [EMAIL PROTECTED] wrote:
It isn't required at runtime. It is used at compile time by the apt
plugin
to generate the tld file and
I'd like to release struts-annotations so there will be a non-snapshot
version available for the next Struts 2 test build.
I see documentation on the annotations themselves, but I can't find
anything explaining what this jar is or how to use it. Can someone
please point that out, or add it if
I think Rene is done with the changes he was doing, so it should be ready to
go. I can add some documentation to the wiki.
thanks
musachy
On 1/20/07, Wendy Smoak [EMAIL PROTECTED] wrote:
I'd like to release struts-annotations so there will be a non-snapshot
version available for the next
Is there any specific place where I should put the doc? or some kind of
template to use?
thanks
musachy
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
I think Rene is done with the changes he was doing, so it should be ready
to go. I can add some documentation to the wiki.
thanks
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Is there any specific place where I should put the doc? or some kind of
template to use?
I thought perhaps on the Building With Maven page, since this seems to
be a compile-time thing. If you need more room, feel free to add
another
What do I need to do to compile? Apt keeps complaining that it cannot find
the processor factory (that's inside the annotations jar). My maven
knowledge nears zero :)
musachy
On 1/20/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Unfortunately, I think Struts 2.0.3 needs one more try.
I've
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
What do I need to do to compile? Apt keeps complaining that it cannot find
the processor factory (that's inside the annotations jar). My maven
knowledge nears zero :)
Try building struts-annotations locally, then building struts 2.
If that
under annotations:
$ mvn clean install
works fine. Under core:
$ mvn -Dmaven.test.skip=true compile
[INFO] Scanning for projects...
[INFO] snapshot org.apache.struts:struts-annotations:1.0-SNAPSHOT: checking
for updates from snapshots-maven-codehaus
[INFO] snapshot
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Under core:
$ mvn -Dmaven.test.skip=true compile
...
[INFO] [compiler:compile]
Compiling 401 source files to /home/musachy/dev/struts/core/target/classes
[INFO] [apt:execute {execution: default}]
warning: Specified
the Tobago plugin instatiates the apt classes (if fork=true then it uses apt
from command line), and then invokes the compile method, so the classpath
must be the same classpath that the plugin is running under.
Here is a link to the mojo class, in case you want to check it out:
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
the Tobago plugin instatiates the apt classes (if fork=true then it uses apt
from command line), and then invokes the compile method, so the classpath
must be the same classpath that the plugin is running under.
Thanks for catching this
I've ran into an odd problem of my own and while I'm troubleshooting it, I'm
hitting some problems or confusion with Freemarker as it is used for the S2
UI tags. Can anyone help me understand this better?
I was getting a big yellow and red Freemarker trace in my rendered page
because an
Joe,
${error} being null would imply that you have an item in the action
errors Collection that is null. (e.g. {Error1, Error2, null,
Error4}) It seems like that would be an issue that occurs as the
errors are being populated. (I can't think of a valid use case where
you would have a null
Tom:
Thanks for your help... I see now that the syntax I was trying to use was
added in Freemarker 2.3.7
http://freemarker.sourceforge.net/docs/versions_2_3_7.html
Now... is an empty string the right result? maybe ${error?default(!--
null error --)} ?
is that overkill?
Joe
On 1/20/07, Tom
No, not overkill at all. I like that better than my empty string. (The
select tag should probably be updated to output something like that for
null keys and null values)
Tom
Joe Germuska wrote:
Tom:
Thanks for your help... I see now that the syntax I was trying to use
was
added in
19 matches
Mail list logo
