On Dec 14, 2006, at 3:42 AM, Craig McClanahan wrote:
It's just what the POM says, but I don't know how to override it. In
1.1.1 MyFaces used the myfaces groupId and now they use
org.apache.myfaces. Because of this Maven doesn't know that my
dependency on MyFaces 1.1.5 should override Shale's
On 12/14/06, Greg Reddin [EMAIL PROTECTED] wrote:
shale-master.pom - This is the base POM for the whole project. It
inherits from an org.apache parent. We only have to release a new
version of this if the information contained in it changes, right
(i.e. add new committer, mailing list, svn
On Dec 14, 2006, at 8:53 AM, Niall Pemberton wrote:
As the shale-tiles module has no dependency on the rest of shale and
can be used in a vanilla JSF environment wouldn't it make more sense
to move this to the proposed Tiles project? I think the argument for
having JSF support in Tiles is
On Dec 14, 2006, at 9:22 AM, Wendy Smoak wrote:
Yes, shale-master is released independently. It has to be released in
advance of the framework so we don't have a snapshot as a parent.
Oh, I see. When I first looked at it I couldn't find a version number.
shale-parent.pom - The base POM
This issue appears to be fixed in Subversion.
https://issues.apache.org/struts/browse/SHALE-335
Is anything holding it up from being resolved?
Greg
On 12/14/06, Greg Reddin [EMAIL PROTECTED] wrote:
On Dec 14, 2006, at 9:22 AM, Wendy Smoak wrote:
Whether to release the framework together or in pieces is just
something we need to decide, figure out how to communicate to users,
and then adjust the build to match.
Sounds like that
On Dec 14, 2006, at 10:43 AM, Wendy Smoak wrote:
For the record, I'm for together. While there are some good
arguments for releasing components individually, and it might even be
easier from a technical standpoint, I think we'll have problems
explaining it to users. (I remember not wanting
