Henri Yandell wrote: > On 2/5/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
[snip] >> from my personal experience with a different project all I can say is >> that changing the groupId is a task that is not very well supported by >> M2. The available docs are spare, do not work as they are described or >> are out of date. So changing the groupId is a task that should be done >> for a reference project that volunteers to go through all the hassle with >> a direct helping hand from some Maven folks. > > My understanding was that once we started doing m2 builds we would be > changing group ids. What I really mean here is deploying to an m2 > repository rather than doing m2 builds. So if Jochen's plan is to do > an m2 build and send it to the m2 repository, then this point is moot. M2 will publish to the M2 repo. The location is simply defined by the groupId ... whatever it is. We can use commons-xxx as well as org.apache.commons, there's no technical restriction. It is simply our decision. [snip] > We've definitely been shifting in the last few Commons releases to > building the actual 1.2 release and then voting on it, rather than > building releases with -rc2 in the jar name etc. It's just been a > tribal change on the lists currently (Craig kicked off a thread about > it a few months ago). I know, but it is not yet supported by the current (released) tool chain of Maven. [snip] >> Please also ensure, that you build from the labeled source code in >> Subversion. That's the main advantage for me using reelase plugin. > > By labeled, do you mean the svn tag? Yes. [snip] - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
