Yes, I learned that yesterday, although the problem seems to lie
somewhere else. I will make sure to updated the uri in a later release
of the maven-jetty-pluto-embedded project.
Nils-H
> You may know this, so apologies if I'm stating the obvious...
>
> Pluto depends on 1.0.x of the standard tagl
I agree, but as I understood from another message, the updated
dependency to TestNG would have to be reversed if we lock the surefire
plugin down to 2.3. If that's not a major issue, I guess that's the
easiest way to solve the problem.
Nils-H
On Feb 17, 2008 3:22 AM, Wendy Smoak <[EMAIL PROTECTED
On Feb 16, 2008 12:29 PM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> If
> I set the plugin version back to the previous release (2.3) it runs
> perfectly. But with the new 2.4 version, the test breaks... 2.4.1
> doesn't work either. So what do we do? I guess hard coding the version
> to 2
On Feb 16, 2008 4:18 PM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> Something is really, really weird... Seems like all loading of tlds
> from jar files has stopped working. If I place the missing tlds in
> web-inf and refer to them in web.xml, I get one step furthere and then
> it fails
On Sun, 2008-02-17 at 12:00 +1100, Jeromy Evans wrote:
> Dave Newton wrote:
> > --- Don Brown <[EMAIL PROTECTED]> wrote:
> >
> >> Well, most of those were patches so I can't really take any credit.
> >> Strangely, many of the patches were from Jeromy...someone should tell
> >> him he can commit
Dave Newton wrote:
--- Don Brown <[EMAIL PROTECTED]> wrote:
Well, most of those were patches so I can't really take any credit.
Strangely, many of the patches were from Jeromy...someone should tell
him he can commit his own patches now :)
Maybe he forget ;)
I was saving my patches
If we go back to with Surefire 2.3 we have to make sure we're only using
TestNG 5.1 because there was an API change in later versions of TestNG which
causes surefire 2.3 to bomb out.
Al.
- Original Message -
From: "Nils-Helge Garli Hegvik" <[EMAIL PROTECTED]>
To: "Struts Developers L
Just wanted to let you know about the CFP for JavaZone 2008. JavaZone
is one of the biggest Java conferences in Europe. The conference is
organized by javaBin, the Norwegian Java User Group (JUG). It's in my
home town, so I hope to see some of you there :)
Information can be found here: http://www
Actually, wait a sec. I keep forgetting that i can't 'clean install'
with xwork in the profiles
mvn clean install -Pxwork,all << -- fails
Each one runs fine separately.
So nevermind.
On Feb 16, 2008 2:19 PM, James Mitchell <[EMAIL PROTECTED]> wrote:
> Right, I don't trust Maven enoug
You're spot on, Don! I think I remember you mentioning in your blog
(about the forked Maven initiative) the automatic plugin upgrades as a
big drawback. Well, guess what. I've traced it down to beeing an
upgrade of the maven-surefire-plugin which is breaking the test... If
I set the plugin version
Right, I don't trust Maven enough to rely solely on the
maven.repo.local switch, but that's another discussion ;)
I am getting a build failure right now. Is anyone else seeing this?
Failed tests:
testAnnotatedMethodFailure(com.opensymphony.xwork2.validator.ValidatorAnnotationTest)
setUp(c
On Feb 15, 2008 11:37 PM, Al Sutton <[EMAIL PROTECTED]> wrote:
> I've seen some posts about false errors in bamboo, so if bamboo is saying
> things aren't correct I can run a double check in continuum.
>
> My other reason for making this available is that people might find
> continuum useful for o
On Feb 16, 2008 10:19 AM, James Mitchell <[EMAIL PROTECTED]> wrote:
> It's probably a good idea to try the build after moving or removing
> your .m2 dir to fully ensure a clean set of publicly available
> dependencies.
>
> I'll do this right now to make sure...stay tuned.
That's what I did, excep
It's probably a good idea to try the build after moving or removing
your .m2 dir to fully ensure a clean set of publicly available
dependencies.
I'll do this right now to make sure...stay tuned.
On Feb 16, 2008 11:59 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Feb 16, 2008 8:32 AM, Wendy Sm
On Feb 16, 2008 8:32 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> And we need to remove (or comment out) all of the repositories in the
> struts2-parent pom. Otherwise anyone who depends on s2 will get all
> those repositories added to their build. They shouldn't be necessary
> this close to a r
On Feb 16, 2008 9:47 AM, James Mitchell <[EMAIL PROTECTED]> wrote:
> Ya, we probably should not be doing this. If we need a newer version,
> it should at least be available on the snapshot repo.
It's in both struts2-core and the portlet plugin that way. Don's
going to have to release struts-anno
Ya, we probably should not be doing this. If we need a newer version,
it should at least be available on the snapshot repo.
On Feb 15, 2008 9:16 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Why is the dependency on struts-annotations in struts2-core locked to
> a particular snapshot?
>
>
Something is really, really weird... Seems like all loading of tlds
from jar files has stopped working. If I place the missing tlds in
web-inf and refer to them in web.xml, I get one step furthere and then
it fails on the next tag library... What in the world could be causing
this? I can't rule out
On Feb 16, 2008 7:19 AM, Don Brown <[EMAIL PROTECTED]> wrote:
> I've cleared all but a couple issues out of Struts 2.1.1, so I think
> we are ready for a release. The only kinda blocking issue is the
> portlet tests failing, but that seems to have something to do with the
> setup, not our portlet
Nevermind on this one. Classpath issue. Guess I should have looked first
:)
On Sat, Feb 16, 2008 at 9:57 AM, Blake Byrnes <[EMAIL PROTECTED]> wrote:
> I haven't logged this yet, but is anyone else noticing that package level
> properties files are not being found right now? My whole project s
I would like to fix the failing portlet test. I hope to get some time
tonight or tomorrow to look more into it.
Nils-H
On Feb 16, 2008 3:19 PM, Don Brown <[EMAIL PROTECTED]> wrote:
> I've cleared all but a couple issues out of Struts 2.1.1, so I think
> we are ready for a release. The only kinda
2008/2/16, Don Brown <[EMAIL PROTECTED]>:
> Any objections to rolling a release(*) in the next day or so?
To release, see the new *easier* instructions to roll out a release:
http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Struts+2.1.x+Distribution
Obviously I am open to all q
I haven't logged this yet, but is anyone else noticing that package level
properties files are not being found right now? My whole project stopped
finding anything that was not in my global resources file. I haven't gotten
a chance to dig around in JIRA or in the app yet.
On Sat, Feb 16, 2008 a
I still want to fix WW-2441, it's minor and I doubt anyone would even
notice it, but still, it makes us look bad if the interactive demo is
broken. I'm gonna fix it right now, so it shouldn't be a problem.
-Wes
On Sun, 2008-02-17 at 01:19 +1100, Don Brown wrote:
> I've cleared all but a couple is
--- Don Brown <[EMAIL PROTECTED]> wrote:
> Well, most of those were patches so I can't really take any credit.
> Strangely, many of the patches were from Jeromy...someone should tell
> him he can commit his own patches now :)
Maybe he forget ;)
I'd like to work on some of the docs before we relea
Well, most of those were patches so I can't really take any credit.
Strangely, many of the patches were from Jeromy...someone should tell
him he can commit his own patches now :)
Don
On 2/17/08, Wes Wannemacher <[EMAIL PROTECTED]> wrote:
> Sheesh Don! With my flakey wifi card, I can hardly even k
I've cleared all but a couple issues out of Struts 2.1.1, so I think
we are ready for a release. The only kinda blocking issue is the
portlet tests failing, but that seems to have something to do with the
setup, not our portlet code, so we could even punt that one.
Any objections to rolling a rel
Yay Maven... *ducks* :)
Don
On 2/17/08, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> I know. I've tried locally as well. It's not very obvious what the
> problem could be. This test has been running without problems for a
> long time no (after some initial start up problems...), so there'
Sheesh Don! With my flakey wifi card, I can hardly even keep up right
now! I went to bed last night and there were 29 issues to play with to
get to 2.1.1, now there are 5, but I'm sure WW-2494 won't take long and
another is the omnibus ticket.
Anyhow, leave WW-2441 for me, I'm gonna work on it to
I know. I've tried locally as well. It's not very obvious what the
problem could be. This test has been running without problems for a
long time no (after some initial start up problems...), so there's no
reason it suddenly should fail.
Nils-H
On Feb 16, 2008 3:08 PM, Don Brown <[EMAIL PROTECTED]
I explicitly removed the 2.4 servlet jar that was leaking in, but that
only seemed to fix the method not found exception I was seeing. I
even tried including jstl but that didn't seem to help.
Don
On 2/17/08, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> I don't know why the test have sta
I don't know why the test have started to fail, but it appears that
some updated dependency version somewhere has caused a
dependency-classloader-clash The prime suspect is a conflicting
version of servlet-api indirectly included somewhere...
Nils-H
On Feb 16, 2008 3:01 PM, <[EMAIL PROTECTED
2008/2/16, Don Brown <[EMAIL PROTECTED]>:
> Is anyone else seeing this problem with the Tiles plugin?
For me the build went fine. What version of Maven are you using? For
me it's 2.0.7.
Antonio
-
To unsubscribe, e-mail: [EMAIL P
33 matches
Mail list logo