Yes, it is still an active project. It primarily gets minor bug fixes,
but there is a 1.4 branch that is in development when time permits.
Paul
On Thu, Jun 25, 2009 at 10:28 PM, Balwinder
Kumar wrote:
> Dear Developers,
>
> Forgive my ignorance, I just wanted to know is Struts 1.X is still an act
Dear Developers,
Forgive my ignorance, I just wanted to know is Struts 1.X is still an
active project?
Thanks & Regards,
Balwinder Kumar
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-m
Oh crap, I think I get it now...
I'll bet I applied that patch but didn't do `svn add`
The class is in his patch, but the subversion commits don't reflect
it. To fix it, just grab the class out of his patch and commit it... I
am going to vote -1 on this as well. I don't use REST so I didn't
reall
I don't think I forgot... ->
http://svn.apache.org/viewvc/struts/struts2/trunk/plugins/rest/src/main/resources/struts-plugin.xml?pathrev=780096&view=diff&r1=780096&r2=780095&diff_format=h
Could it be a later commit that removed it?
-Wes
On Thu, Jun 25, 2009 at 9:13 PM, Musachy Barroso wrote:
>
yeah this is broken so I am voting -1. The problem is this bean definition:
MultipartFormDataHandler is no defined anywhere, I think it is related
to this ticket:
https://issues.apache.org/struts/browse/WW-3128
@Wes: missing commit?
musachy
On Tue, Jun 23, 2009 at 12:13 AM, Al Sutton wrote:
It depends on where you want to fix it. Compile scope is the default
so that won't work.
If you mark both asm jars with true in the xwork
poms, it won't come through as a transitive dependency but will be
available for compiling and during the build.
You could modify the struts pom and exclude t
I guess it was never fixed.
@Maven zen masters: how do we fix this? change the scope to "compile"?
musachy
On Thu, Jun 25, 2009 at 9:29 AM, Tomislav
Stojcevich wrote:
> Ah, yes, I see the package difference now, cool.
>
> Will xwork release new version with pom fix? Since pom already in
> repo
Ah, yes, I see the package difference now, cool.
Will xwork release new version with pom fix? Since pom already in
repo it can't be changed so new release is required.
If you still plan on releasing struts 2.1.7 as is, this problem will
probably come up for others.
--tom
On Thu, Jun 25, 2009
I think it has been fixed in xwork pom. Also, there won't be any class
loading problem because the classes are shadowed (moved to a new
package at compilation time), so if you look inside the xwork jar, you
will see that the asm classes have xwork in the package name, this in
fact prevents the prob
fixed where? in struts or xwork pom?
--tom
On Thu, Jun 25, 2009 at 12:14 PM, Musachy Barroso wrote:
> I think this came up before and had been fixed
>
> musachy
>
> On Thu, Jun 25, 2009 at 9:03 AM, Tomislav
> Stojcevich wrote:
>> I see that the asm classes are in the xwork-core-2.1.4.jar
>>
>>
Excluding asm and asm-commons from my struts-core dependency worked.
org.apache.struts
struts2-core
2.1.7
asm
asm
asm
I think this came up before and had been fixed
musachy
On Thu, Jun 25, 2009 at 9:03 AM, Tomislav
Stojcevich wrote:
> I see that the asm classes are in the xwork-core-2.1.4.jar
>
> I don't pull in asm manually, maven pulls it in transitively. The
> 2.1.4 parent pom for xwork has a dependency sect
I see that the asm classes are in the xwork-core-2.1.4.jar
I don't pull in asm manually, maven pulls it in transitively. The
2.1.4 parent pom for xwork has a dependency section that is inherited,
so asm-3.1 is a dependency of xwork-core and is being pulled into my
web-inf/lib by maven.
See
http
xwork jarjars (is that a word?), asm into the xwork jar, you don't
need to include asm as a dependency for xwork.
musachy
On Thu, Jun 25, 2009 at 8:47 AM, Tomislav
Stojcevich wrote:
> From the maven central repo:
> http://repo2.maven.org/maven2/org/springframework/spring-core/2.5.6.SEC01/spring-c
>From the maven central repo:
http://repo2.maven.org/maven2/org/springframework/spring-core/2.5.6.SEC01/spring-core-2.5.6.SEC01.pom,
it's showing 2.2.3
The version of spring that struts 2.1.7 depends on is 2.5.6 which also
shows asm version of 2.2.3.
But struts-core depends on xworx 2.1.4 which de
find out what version of ASM is distributed with the version of spring
that you have.
On Thu, Jun 25, 2009 at 8:30 AM, Tomislav
Stojcevich wrote:
> That's possible I guess. The versions I'm using all came from the
> maven central repo except for the struts which came from the staging
> repo.
> I
That's possible I guess. The versions I'm using all came from the
maven central repo except for the struts which came from the staging
repo.
I am running java 1.6.
Looking in the manifest of each of the asm jars which is the best why
that I know how to tell, it says Created-By: 1.6.0_02-b05 (Sun
let me be captain obvious, you are using a version of ASM that is not
binary compatible with the spring jars, I think.
musachy
On Thu, Jun 25, 2009 at 7:46 AM, Tomislav
Stojcevich wrote:
> Asking on dev list since it may be a problem with the staged libraries
> and dependencies.
>
> Using 2.1.7 f
Asking on dev list since it may be a problem with the staged libraries
and dependencies.
Using 2.1.7 from maven staging repository.
War packaged inside ear. Ear deployed to Weblogic 10.3 on windoze.
Java 1.6.0_13-b03
false
antlr.*
com.opensymphony.*
ognl.*
org.apache.*
19 matches
Mail list logo
