|
Vincent Massol made changes - 08/May/04 04:35 PM
I think it does work, I basically copied the jboss-j2ee-3.2.3.jar as j2ee-1.3.jar on my local repository.
ok. Cool. But what about the other issues I've highlighted in my previous comment?
Thanks I was just thinking about it, if cactus builds on 1.3 why do we need the other version for? Since this was supposed to be just a build problem that we're trying to resolve right?
Doh I see the problem now.
I've just applied your idea of using jboss-j2ee jar for the Ant build. For Maven it's a bit more complex and I think we need to wait till we separate the framework project and others into several subprojects (share/, j2ee12/, j2ee13/). We also need to decide whether we want to do this.
Vincent Massol made changes - 28/Jan/05 06:13 AM
Vincent Massol made changes - 28/Jan/05 06:36 AM
I am closing this issue since it is no longer valid, because Cactus build system is now Maven
Petar Tahchiev made changes - 10/Mar/08 08:12 PM
Petar Tahchiev made changes - 11/Apr/08 12:36 PM
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
in addition we'll need to derive these jboss-j2ee versions from ${cactus.j2ee.version.full}. For example we need to transform "1.3" into "3.2.3". That'll require some scripting in maven.xml. Not nice. However this can solved by splitting the framework/ maven projects into 3 projects: shared/, j2ee12/ and j2ee13/.