Hi Kaare. No apology needed. I appreciate your response. I am sorry if my email came across as a rant to you or your project. It was not intended to be. I emailed the list as I think that there are larger concerns that could inhibit the forward movement, evangelism, and adoption of Mojo and Maven. I really didn't want to have to ask for your help at all. As a fellow developer, I know how busy you are. That's why I tried to visit the CI servers, to gain a better understanding of the current capabilities of the code. But I couldn't even do that. Does anyone on the list know why I can't hit any of the CI servers? Being able to look at CI results would help me to figure out exactly when the divergence in code happened and what source code to use. It's the trend for plugins not to be "released early, released often" that is my core concern, rather than any specific behavior or project. When a SNAPSHOT needs to be used *now* in a release, the community says to download the source and release it privately. But when one can't download and release from source, that doesn't work very well. I've had a lot of success by having a continuous integration snapshot repository that always contains the latest compiled version and its sources. (That is to say, cruisecontrol always runs "clean source:jar deploy" as its' goals.) Thanks again for listening. Barrett :: Barrett Nuzum Consultant, Skill Development Direct: 918.640.4414 Fax: 972.789.1340
Valtech Technologies, Inc. 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 www.valtech.com <http://www.valtech.com/> making IT business friendly ________________________________ From: Kaare Nilsen [mailto:[EMAIL PROTECTED] Sent: Mon 4/16/2007 8:53 PM To: [email protected] Subject: Re: [mojo-dev] Aspectj-maven-plugin release and/or abandonment? Hi.. First of all I would like to be the first to appologize for the kind of *slow* progress on this plugin, but unfortunatly my calendar has been kind of full for a while now, and I have some problems keeping up with the bug reports at hand. Also there are (as always) kind of a complicated picture where one of them is that I cannot get the new aspectJ binaries to work with the plugin, and I feel that releasing yet another version using old binaries is kind of a bad idea. But this set a side (trying here not to seem like a grumpy developer) I find it a little to passive just to whine about this in the mailing lists (and my private email). What would on the other side be productive for us all is that you guys see if you could create a patch (including testcases) fixing the problem, and I for sure can promise to do quality ensurance on the code applied and release a new version of the plugin. or WDYT ? On 17/04/07, Barrett Nuzum <[EMAIL PROTECTED]> wrote: > Hi Mojoers. > > We have been migrating a relatively complex CI environment to Maven2 over the > past few months and are finally able to see the light at the end of the > tunnel. > > We recently tried to start releasing projects, but needed to use the > aspectj-maven-plugin v 1.0-beta-4 to be able to weave our aspects with our > code. (Long story.) This version is, of course, a SNAPSHOT, and you can't > depend on a snapshot plugin when releasing. Ouch. > > So we decided to try to check out the source code and fork a version of the > snapshot so that we could release. > The project would not compile without Java 1.5, even though the POM specifies > compiler target and source 1.4. > Even then, we had a number of test failures, (when removing the offending > Java 1.5 code) straight from the start. > We're stuck on Java 1.4.2 (and IBM JDK, natch) for a while longer, so this is > not good for us. > > I figured that maybe the code was just broken at the time that I checked it > out, and attempted to visit Codehaus' CI environment, but can't access *any* > of them (http://maestro.ci.codehaus.org/). I always get either a timeout or > HTTP error from a proxy. (CruiseControl, Beetlejuice, Bamboo, and Continuum > all do the same.) > > We've duct taped and stapled the existing binary and metadata into a team > repo from snapshots.repository.codehaus.org, but the experience and solution > seemed pretty far from Maven practices. > > Thought you'd might like to know. > > Barrett > > > :: > Barrett Nuzum > Consultant, Skill Development > Direct: 918.640.4414 > Fax: 972.789.1340 > > Valtech Technologies, Inc. > 5080 Spectrum Drive > Suite 700 West > Addison, Texas 75001 > www.valtech.com <http://www.valtech.com/> > making IT business friendly > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
