If one checks out "current", then it is made to appear as if maven and struts2 are adjoining folders, but in the repository, each has its own trunk.
The question that raises is what procedure to follow when tagging the repository so that it could be rebuilt from the tag later? We had just been tagging the struts2 trunk. (And likewise just the struts1 trunk.) Now it sounds like we should tag both the maven trunk and the struts2 trunk, and then expect both to be checked out side by side to build against the tag. There would also be the question of branches. If we were to branch, would we need to branch both the struts2 (or struts1) trunk and the maven trunk together? How much under maven do Struts 1 and Struts 2 actually share? Would be it better or easier to give each its own maven folder? -Ted. On 1/21/07, Rene Gielen <[EMAIL PROTECTED]> wrote:
Sorry for that late reply, was on the road last two days. I just added the profile as discussed in master pom. Works fine AFAIK. I assumed a directory organization like we have in the svn repository, so that we have the maven repository checked out besides struts2 repository, which means the reference in pom.xml goes to ../maven/struts-aanotations. Another solution would be to just assume the struts annotations module is found besides struts2 repo. So that point might to be discussed. - Rene Don Brown schrieb: > I agree, but even then, would maven really download the newer version? > With xwork, we used to have the problem where newer snapshots wouldn't > be downloaded if the local repo has a copy. > > Rene had a good idea to add a profile, much like do we do for xwork, > which will bring in the project and build it first. > > Don > > Joe Germuska wrote: >> wouldn't it be as good or better for someone to deploy a newer >> SNAPSHOT of >> struts-annotation.jar so that it just gets pulled down automatically? >> >> On 1/19/07, Don Brown <[EMAIL PROTECTED]> wrote: >>> >>> You have to build the struts-annotation.jar and install it in your local >>> maven repository: >>> >>> cd maven/struts-annotations >>> mvn install >>> >>> Then 2.0.3 will build correctly. >>> >>> Don >>> >>> Ted Husted wrote: >>> > On 1/19/07, Don Brown <[EMAIL PROTECTED]> wrote: >>> >> The solution is to do a mvn clean and build a fresh >>> >> struts-annotations.jar. In the meantime, I added the TLD back >>> until we >>> >> are sure this situation is resolved. >>> > >>> > From a clean checkout of the Struts 2.0.3 tag and a clean struts m2 >>> > repository, I don't see that the TLD is being generated. >>> > >>> > -Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
