Currently, if we want to publish the jars to the maven repo the release manager would need to make sure the current pom.xml compiles and runs all tests successfully with "mvn clean install". You'd run the normal ant build as well to generate the jar we want to deploy to a maven repository. Then we would run a "mvn deploy:deploy-file" and provide all the necessary parameters, which would include the pom to insure our dependency information is correct. ( http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html). This would create the needed structures/meta for the jars to function appropriately in the maven repo.
If we are using maven for the whole build then it would require mvn deploy:deploy . After each of these process you would scp the results to the people.apache.org:/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository. It is also possible to have both of these automatically copy to the people.apache.org location. Brandon On 2/14/07, Jeff Butler <[EMAIL PROTECTED] > wrote:
Yes - I should have asked that question with more subtlety. I guess the bottom line is that it is *possible* to get the jars to the repository without doing a maven build, but doing a maven build makes it much easier to publish to the repository. And our history shows that we are unlikely to get the jars to the repository with the build process we are using now. Right? Jeff On 2/14/07, Larry Meadors <[EMAIL PROTECTED] > wrote: > > IMO, that is like "Can we clean a toilet with a toothbrush?" > > Yes, we can, but who wants to offer up their toothbrush? Not me! :-) > > The question to me is: > > "Can we get the iBATIS jars to the maven repository without doing a > maven build, and is it the right way to do it?" > > Yes we can, but no it's not. > > Larry > > > On 2/14/07, Brandon Goodin <[EMAIL PROTECTED]> wrote: > > "Can we get the iBATIS jars to the maven repository without doing a > maven > > build?" > > > > Yes > > > > > > On 2/14/07, Jeff Butler < [EMAIL PROTECTED]> wrote: > > > > > > In my own little perfect world, I'm -1. The iBATIS ant build is so > simple > > now - I hate to see it mucked up just to supply the Maven meta-bs as > Clinton > > so eloquently put it. > > > > > > However, I would like to see the iBATIS jars in the Maven repository > - if > > for no other reason than to help those who can't figure out how to set > a > > classpath without a tool. If a maven build makes that possible then I > guess > > I'd be +2, but reluctantly. > > > > > > I think that supporting both Ant and Maven is problematical - seems > like > > we should just pick one for simplicity going forward. > > > > > > So I guess I can't give a single vote. Can someone definitively > answer > > this question: Can we get the iBATIS jars to the maven repository > without > > doing a maven build? That's the key point for me. > > > > > > Jeff Butler > > > > > > > > > > > > On 2/14/07, Clinton Begin < [EMAIL PROTECTED] > wrote: > > > > > > > Hi all, > > > > > > > > It strikes me that there was enough discussion around the Maven > build > > > > to warrant an official vote for Maven support. > > > > > > > > +2 => Replace our Ant build entirely with a Maven build. > > > > > > > > +1 => Support Maven by including a Maven build alongside our Ant > build. > > > > > > > > 0 => Don't care or I don't know enough about Maven to decide. > > > > > > > > -1 => Do not support maven. > > > > > > > > Cheers, > > > > Clinton > > > > > > > > > > > > > > >
