Wendy Smoak wrote:
Is it going to be struts-core.jar, then? It seems confusing to have a
directory called 'core' build an artifact called 'struts-action'.
I suppose the directory could be called 'action', but it seems kinda silly to have 'action/trunk/action'. 'core' seems
to be what other projects like Cocoon, MyFaces, Shale, etc., are using, although in the first two cases, 'core' is top
level since they don't have the two framework split like we do. I tried dropping the contents of core down to action/,
but then the common build files aren't right and it is more confusing.
I'm am kind of wondering if the other modules shouldn't be prefixed with 'struts-action', i.e. 'struts-action-extras'.
It seems long, but it would be more accurate. The other option would be to dump 'struts' all together:
- action-core.jar
- action-extras.jar
- action-taglibs.jar
- action-apps.jar
- action-faces.jar
- action-el.jar
I don't know if I like so easily giving up the Struts name though.
This work is important as it paves the way to how we will handle Action 2 modules. It would be even nicer if we could
follow or synchronize the product structure/layout with Shale.
Don
I'm having trouble getting the nightly to run, as it seems the default built
isn't installing the snapshot jars correctly. What am I missing here?
It's the paths to 'build' in project.properties -- instead of
"${basedir}/build" it should be "../build". And a few of these in
maven.xml:
- <ant:fileset dir="build/">
+ <ant:fileset dir="../build">
HTH,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
