place. The code that I did all
of this with is listed at the github location above and is also published
to the official maven repo as well for public consumption (version 1.2
being the one that has this fixed in for proper reactor support).
Thanks,
On Sat, Dec 21, 2013 at 6:00 PM, Sejal Patel wro
Hey guys, I was hoping that someone might be able to help me out with an
issue I'm having on a plugin I've written.
The high level of what the plugin does is automatically change the version
number of a project to match whatever the name of the git branch name is
that it is on without any physical
+1 on maven 2.1
-1 on maven 2.0.x (please don't mess with the current maintenance releases.
even feature enhancements should be minimal. just fix regressions mostly)
On Sun, May 4, 2008 at 4:14 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> +1 for 2.1
>
> Arnaud
>
> On Sun, May 4, 2008 at 12:02
Hi Sebastien, you are right that this is a common problem and has no clean
solution. Partly because of this limitation, at my job I've instituted some
rules as part of the project standards. Any "resources" instead of being
placed in the src/main/resources are now placed in src/main/packages and
I'
+1 from me. after a rocky start with those early RC having issues, seems you
guys did great in resolving everything and making sure it all works great.
cudos for a great release run and hard work to ensure integrity and quality
went into this release.
On Mon, Apr 7, 2008 at 6:10 PM, Arnaud HERITIE
Hmm, well jason, it really is as simple as the super pom (that pom-4.0.0
thingy) listing out all of the plugins and specifying a specific version
number on them. I'm taking a peek at the RC5 version of the superpom (havn't
gotten around to 6, 7, or 8 now) and it looks like it is using the most
rece
Ah man that sucks. I just finished checking the results of the 217 projects
we have in cruise control using RC5 (which all worked perfectly as far as I
can tell) and now there is an RC6. Can I just blindly say I accept it :)
What is the problem with the site plugin quickly? I'd like to see if it
i
I hate holding things up but I didn't get a chance to run it through the
ringer today. Most likely I should be able to do so tomorrow and if
everything passes you'll get my go ahead as well :)
On Mon, Mar 31, 2008 at 4:36 PM, John Casey <[EMAIL PROTECTED]> wrote:
> +1 here, seems to be working we
There is no rush on this right? If not, I'll see if I can use this on
Monday. I'd rather not be doing work related stuff on the weekends ;)
On Sat, Mar 29, 2008 at 12:32 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> Phew! You had me scared there as the IT for 3473 uses 2.4 and 2.4.1 to
> generat
n locked down so it is version 2.5 that is being used.
I know I need to file this as a bug but wanted to give you guys a heads up
quickly and to figure out if this is an eclipse plugin bug or an RC4 bug but
either way the 2 are not playing nicely with each other.
On Fri, Mar 28, 2008 at 8:45 AM,
Today is a busy day unfortunately (fridays always are), I won't be able to
run through our 200+ project suite with the new version until Monday.
On Fri, Mar 28, 2008 at 5:28 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Thanks !
> I have tested this rc on some corporate builds and all builds are
simple fix in the poms if that causes a problem. I'm
> worried about stuff like James found (MNG-3119).
>
> -Original Message-
> From: Sejal Patel [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 26, 2008 9:56 PM
> To: Maven Developers List
> Subject: Re: [pre vote t
; -Original Message-
> From: Sejal Patel [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 26, 2008 6:47 PM
> To: Maven Developers List
> Subject: Re: [pre vote take 3] 2.0.9-RC3
>
> +1 for now. Seems to work with my personal projects at home. I'll see how
> well it
+1 for now. Seems to work with my personal projects at home. I'll see how
well it works on our projects at work and make sure it doesn't break
anything that used to work with 2.0.8.
I'll give my final answer probably in a little over 24 hours from now (want
to make sure it works with all of our pr
Ah yes I did miss that.I've been seeing a combination of plugins not being
locked down and in other threads people using the 2.0.9 snapshot having
problems with their plugins and didn't see that you had locked them down
specifically. I also just now see in the previous thread why they are being
loc
Not to be a party pooper but given all the discussions that are cropping up
over and around this release, I feel like a vote of -1 is in order.
On Wed, Mar 19, 2008 at 11:42 AM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> >Well, the auto-update of the archetype-plugin certainly has caused a
> LOT
>
Ok so it sounds like you are good to go for a beta-2 and I'm pretty sure we
are all aware that there are a lot of little issues like what you nicely
bulleted out that prevent this from being a 2.2 final release.
It is great that you took the time to create this list though. Will make it
much much
+1
On Thu, Feb 21, 2008 at 2:01 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Hi all,
> I'd like to propose that we release both the assembly plugin and one of
> its shared-component dependencies: maven-repository-builder. See below for
> more information on what's included in these releases. I hav
+1
On Fri, Feb 15, 2008 at 6:51 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> As you might expect, all the good bugs were found in 2.4.1 [looks like
> some folks were waiting for SP1 to start testing... ;-)]
>
> We solved 5 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=
the
> issues slated for that release yet. I think they're mostly patches,
> but I'll need to set aside some time to apply them and call for the
> release.
>
> Sorry for the delay.
>
> -john
>
> On Feb 13, 2008, at 11:42 AM, Sejal Patel wrote:
>
> >
Hey guys I'm curious, what is the states of the new beta2 release? I'd like
to be able to get started on using it from an official release.
On Jan 31, 2008 6:32 PM, Paul Gier <[EMAIL PROTECTED]> wrote:
> Ok, no problem. Here are a few other issues that should be quick to fix
> when
> you have a
e able to get your fix in.
>
> -john
>
> On Jan 30, 2008 3:24 PM, Sejal Patel <[EMAIL PROTECTED]> wrote:
>
> > I've updated 277 with a patch. Not sure that you really need proof to
> see
> > that a chunk of code that says "project.getBaseDir()" follo
big help, particularly if they include tests that
> exhibit the failure behavior, as this can take some time to replicate
> (even if they are small fixes, you're familiar with the problem,
> while I'm not).
>
> Thanks,
>
> -john
>
> On Jan 30, 2008, at 12:04 PM
My suggestion is before releasing 2.2-beta-2, that the following issues be
addressed (simple 1 liner fixes)
http://jira.codehaus.org/browse/MASSEMBLY-277 (null pointer exception)
http://jira.codehaus.org/browse/MASSEMBLY-278 (config to not fail out on
missing descriptor)
If you like, I can even g
Hey guys, I was looking to do a few things with the assembly plugin and so I
siffed through the code and notice a few things. I couldn't find any
developers listed on the assembly plugin page so I ask here (and I'm more
then happy to make the changes myself if needed).
1) org.apache.maven.plugin.a
25 matches
Mail list logo
