RE: NullPointerException during maven-assembly-plugin

nc. It's also why you should specify in your pom, because > then you are guaranteed to have a consistent version across your teams > (and reproducible in the future). > > --Brian > > -Original Message- > From: Jose Alberto Fernandez [mailto:[EMAIL

RE: NullPointerException during maven-assembly-plugin

his list for more info. >> >> -----Original Message- >> From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] >> Sent: Monday, April 23, 2007 8:36 AM >> To: dev@maven.apache.org >> Subject: Re: NullPointerException during maven-assembly-plugin >> >>

RE: Remove auto-resolution of plugin versions from Maven 2.1

I thought one of the main arguments in all this discussion is to make things simple and easy for users. At least those were the comments against forcing everyone to explicitly set versions for everything. The bundle will free every single user of having to go finding out what version of what to us

RE: Remove auto-resolution of plugin versions from Maven 2.1

Brian E. Fox wrote: > > Everyone keeps referring to bundles that "are known to work together." > Come someone produce an example of plugins that are incompatible with > each other? I haven't seen this and I'm not even sure it's possible > given that plugins can't communicate or even know about e

RE: NullPointerException during maven-assembly-plugin

Brian E. Fox wrote: > > If you haven't specified the version of the plugin in your pom, then the > version each developer has can be different. See the other threads on > this list for more info. > > -Original Message- > From: Jose Alberto Fernandez [mailto:[E

Re: NullPointerException during maven-assembly-plugin

probably updated to the latest version of the assembly plugin. >> >> Please give us a build that is representative of your build so that >> we can fix it. >> >> Thanks, >> >> Jason. >> >>> >>> Jose Alberto Fernandez wrote: >>>&

Re: Remove auto-resolution of plugin versions from Maven 2.1

Wayne Fay wrote: > > On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote: >> So if I say BETA then no alpha bundle (a bundle >> containing alpha software) will be selected. > > Who exactly decides what the quality is for a given release? Outside >

Re: NullPointerException during maven-assembly-plugin

specify the versions of plugins you are using. Your > builds probably updated to the latest version of the assembly plugin. > > Please give us a build that is representative of your build so that > we can fix it. > > Thanks, > > Jason. > >> >> Jose Alber

Re: Remove auto-resolution of plugin versions from Maven 2.1

Wendy Smoak-3 wrote: > > On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote: > >> Well, having the documentation not reflecting the released plugins but >> SNAPSHOTs is not helpful to any user. > > We're discussing this now in a different thread

NullPointerException during maven-assembly-plugin

Hi guys, I posted this on the user list but got no answers. It is an urgent matter as it is affecting some of our developers that are unable to build the project anymore while others can. Talking about unreproducible builds. We are getting the following stack-trace while executing the assembly:di

Re: Remove auto-resolution of plugin versions from Maven 2.1

Wayne Fay wrote: > > I wish I knew how to properly handle the issue of what I will call > laziness wrt reading and using documentation on the part of users. It > might be helpful to add a lot more things to the FAQ (including > comments about web proxies with a link to the "configuring proxy" pa