Re: lowering the barriers - one-time-setups issues... Based on Adams and Thilo's responses, I have pushed a bit to get the m2eclipse / xmlbeans stuff improved.
To my surprise, someone posted this morning to the Jira https://issues.sonatype.org/browse/MNGECLIPSE-1694 indicating that the bug might be fixed in the latest m2eclipse (not yet released). I tried that "bleeding-edge" release in a fresh Eclipse 3.6 (Helios) and it did indeed fix that issue - right clicking the projects that use xmlbeans and selecting Maven -> update configuration updated the build paths correctly, so they all built in Eclipse. I've asked to see if there's a "guesstimate" of when this might be released... ----------- Also, I found a likely alternative work-around. This is to regress the version used for the xmlbeans-maven-plugin from 2.3.3 to 2.2.0. This appears to work with 0.10.2 as well as 0.11. I think it doesn't affect our builds, so I plan to backlevel this plugin, until after m2eclipse 0.11 is released. ----------- I asked on the docbkx mailing list about getting a release out - and they say they may try to do one in a week or 2... If both of these get fixed, then the one-time setups become much more "conventional". -Marshall On 8/9/2010 11:31 PM, Adam Lally wrote: > On Mon, Aug 9, 2010 at 11:24 PM, Marshall Schor <[email protected]> wrote: > >> On 8/9/2010 5:22 PM, Adam Lally wrote: >>> On Mon, Aug 9, 2010 at 12:03 PM, Marshall Schor <[email protected]> wrote: >>> >>>> Please post feedback on this build process - is this a good direction, >> and >>>> whether or not you are able to do builds! >>>> >>>> >>> I like some things about Maven, but the experience of using it has >>> definitely been frustrating. Any time you try to do something out of the >>> ordinary, it is a real struggle. I remember experiencing that >> frustration >>> when we first migrated out build to Maven, and now I've been seeing >> Marshall >>> go through it again. >>> >>> However, our previous build process wasn't so great either. Our ant >> scripts >>> had grown organically until they were a mess that wasn't maintainable. >> And >>> without maven to automatically download dependencies like Eclipse jars, >> in >>> order to build UIMA you had to manually obtain Eclipse (and a particular >>> version of it, too) and a couple of other dependencies, which was a pain. >>> >>> I think that I can work with what we have now, even if it's not ideal. I >>> was able to do a build following the instructions, but it's very >> cumbersome >>> and I worry that it will discourage people from becoming involved in the >>> project. >> Was the cumbersome part doing the one-time-setups, or was it something >> afterwards, in doing the builds themselves? >> > Just the one-time setups. I know it is only "one time", so it's not too bad > for a committer to have to do, but for someone who just wants to casually > poke around the UIMA code and maybe try to patch a small issue, it may turn > them off. > > -Adam >
