[jira] Updated: (MWAR-12) Add resource filtering to war plugin

2006-02-20 Thread Brian Topping (JIRA)
[ http://jira.codehaus.org/browse/MWAR-12?page=all ] Brian Topping updated MWAR-12: -- Attachment: MWAR-12.patch > Add resource filtering to war plugin > > > Key: MWAR-12 > URL: http://jira.codehaus.org/b

[maven2 build branches/maven-2.0.x - SUCCESS - update] Tue Feb 21 07:15:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060221.071501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.071501.txt - To unsubscribe, e-mai

[jira] Created: (MNG-2094) need comprehensive docs on the snapshot mechanism

2006-02-20 Thread Brett Porter (JIRA)
need comprehensive docs on the snapshot mechanism - Key: MNG-2094 URL: http://jira.codehaus.org/browse/MNG-2094 Project: Maven 2 Type: Task Components: Documentation: Faqs Reporter: Brett Porter I need to doc

[maven2 build trunk - SUCCESS - update] Tue Feb 21 07:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.070002.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.070002.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

[jira] Closed: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

2006-02-20 Thread Allan Ramirez (JIRA)
[ http://jira.codehaus.org/browse/MDEPLOY-21?page=all ] Allan Ramirez closed MDEPLOY-21: Resolution: Fixed Fixed in SVN. This time its for sure :) > Deploying an artifact from the local directory failed if the associated pom > file is not renamed

[jira] Reopened: (MNG-2083) Path to missing dependency is not shown nor url to download

2006-02-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MNG-2083?page=all ] Carlos Sanchez reopened MNG-2083: - There's a problem when more than one dependecy is missing, some info (install instructions, download url) for the first one is ommitted 2 required artifacts missi

[jira] Closed: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects

2006-02-20 Thread Tuomas Kiviaho (JIRA)
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=all ] Tuomas Kiviaho closed MNGECLIPSE-81: Resolution: Won't Fix The problem Eclipse internal error only exist when using WTP. Maven2 plugin doesn't generate a similar situation. There is an

[jira] Updated: (MNG-2083) Path to missing dependency is not shown nor url to download

2006-02-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MNG-2083?page=all ] Carlos Sanchez updated MNG-2083: Attachment: pom.xml > Path to missing dependency is not shown nor url to download > > > Key: MNG

[jira] Updated: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

2006-02-20 Thread Allan Ramirez (JIRA)
[ http://jira.codehaus.org/browse/MDEPLOY-21?page=all ] Allan Ramirez updated MDEPLOY-21: - Remaining Estimate: 5 hours Original Estimate: 5 hours > Deploying an artifact from the local directory failed if the associated pom > file is not renamed >

[maven2 build branches/maven-2.0.x - SUCCESS - update] Tue Feb 21 06:45:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060221.064502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.064502.txt - To unsubscribe, e-mai

[jira] Updated: (MRM-57) ability to retrieve matched portion of classes, packages and files fields

2006-02-20 Thread Maria Odea Ching (JIRA)
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching updated MRM-57: Attachment: MRM-57-maven-repository-indexing.patch > ability to retrieve matched portion of classes, packages and files fields >

[maven2 build trunk - SUCCESS - update] Tue Feb 21 06:30:01 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.063002.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.063002.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

[jira] Commented: (MNG-1181) MavenEmbedder.execute() doesn't run reactor modules

2006-02-20 Thread Milos Kleint (JIRA)
[ http://jira.codehaus.org/browse/MNG-1181?page=comments#action_59080 ] Milos Kleint commented on MNG-1181: --- the embedder2 class seems to be missing some functionality of the original, namely the reading of models and MavenProjects. can you elaborate on

[jira] Closed: (MNG-2083) Path to missing dependency is not shown nor url to download

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2083?page=all ] John Casey closed MNG-2083: --- Resolution: Fixed fixed and merged. > Path to missing dependency is not shown nor url to download > > >

[jira] Closed: (MNG-2081) Typing error in apt files

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-2081?page=all ] Brett Porter closed MNG-2081: - Assign To: Brett Porter Resolution: Fixed Fix Version: (was: 2.0.4) documentation > Typing error in apt files >

[maven2 build branches/maven-2.0.x - FAILED - update] Tue Feb 21 06:15:00 GMT 2006

2006-02-20 Thread continuum
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.061501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MNG-2083) Path to missing dependency is not shown nor url to download

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2083?page=comments#action_59077 ] John Casey commented on MNG-2083: - ready for merge from trunk. > Path to missing dependency is not shown nor url to download > --

[jira] Updated: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

2006-02-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MNG-1797?page=all ] Carlos Sanchez updated MNG-1797: Attachment: MNG-1797-unit-test.patch > Dependency excludes apply to every subsequent dependency, not just the one it > is declared under. > --

[jira] Updated: (MPJAVA-44) Create property to disable compilation warning

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-44?page=all ] Lukas Theussl updated MPJAVA-44: Fix Version: 1.6 > Create property to disable compilation warning > -- > > Key: MPJAVA-44 > URL: http://

[maven2 build trunk - SUCCESS - update] Tue Feb 21 06:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.060001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.060001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

[jira] Updated: (MPJAVA-21) Unable to add something to java:compile classpath

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-21?page=all ] Lukas Theussl updated MPJAVA-21: Fix Version: 1.6 > Unable to add something to java:compile classpath > - > > Key: MPJAVA-21 > URL: h

[jira] Closed: (MNG-1703) is not propagated to child POMs

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-1703?page=all ] Brett Porter closed MNG-1703: - Resolution: Fixed Fix Version: (was: 2.0.4) 2.0.3 > is not propagated to child POMs > ---

Asking for comments on MNG-1181

2006-02-20 Thread Jochen Wiedmann
Hi, may I ask for comments on MNG-1181? About one week ago, I posted a proposal on the bug, which hasn't yet been looked at. I am ready to continue work in that area (in particular now, that I am reading that this "blocker" is deferred to 2.0.4), but I would want to be backed up by the developers

[jira] Updated: (MPJAVA-32) Support maven.compile.debuglevel property

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-32?page=all ] Lukas Theussl updated MPJAVA-32: Fix Version: 1.6 > Support maven.compile.debuglevel property > - > > Key: MPJAVA-32 > URL: http://jira.codeh

[jira] Closed: (MPJAVA-31) please add a property for the encoding of the java:compile goal

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-31?page=all ] Lukas Theussl closed MPJAVA-31: --- Resolution: Won't Fix Use the maven.compile.encoding property. > please add a property for the encoding of the java:compile goal > ---

[jira] Closed: (MPJAVA-30) Compiling gives incorrect warning about target JVM version

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-30?page=all ] Lukas Theussl closed MPJAVA-30: --- Resolution: Fixed Fix Version: 1.6 > Compiling gives incorrect warning about target JVM version > -- >

[maven2 build trunk - FAILED - update] Tue Feb 21 05:30:01 GMT 2006

2006-02-20 Thread continuum
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.053001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (MNGECLIPSE-77) Add support for WSAD specifics on a J2EE project.

2006-02-20 Thread Eugene Kuleshov (JIRA)
[ http://jira.codehaus.org/browse/MNGECLIPSE-77?page=all ] Eugene Kuleshov updated MNGECLIPSE-77: -- Fix Version: (was: 0.0.8) > Add support for WSAD specifics on a J2EE project. > - > > Key

[jira] Closed: (MPJAVA-4) Compile fails using forked compiler when directory contains spaces

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-4?page=all ] Lukas Theussl closed MPJAVA-4: -- Resolution: Fixed Fix Version: 1.6 Should be fixed now as Maven 1.1 comes with ant 1.6.5. > Compile fails using forked compiler when directory contains spaces >

[jira] Closed: (MPJAVA-39) Plug-in ignores source generated during Maven run

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-39?page=all ] Lukas Theussl closed MPJAVA-39: --- Resolution: Duplicate > Plug-in ignores source generated during Maven run > - > > Key: MPJAVA-39 >

[jira] Closed: (MPJAVA-38) sourceModifications handled incorrectly when more than one clause present

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJAVA-38?page=all ] Lukas Theussl closed MPJAVA-38: --- Resolution: Fixed Fix Version: 1.6 > sourceModifications handled incorrectly when more than one clause present > -

[maven2 build branches/maven-2.0.x - SUCCESS - update] Tue Feb 21 05:15:01 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060221.051501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.051501.txt - To unsubscribe, e-mai

[jira] Commented: (MNG-2003) release and update to wagon-file 1.0-alpha-7

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-2003?page=comments#action_59073 ] Brett Porter commented on MNG-2003: --- I've checked - we only need to release wagon-file. The only fixes were WAGON-30 and WAGON-34 > release and update to wagon-file 1.0-alpha-7 >

[jira] Commented: (MPMULTIPROJECT-59) Multiproject plugin problem in Maven 1.1-betaX

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-59?page=comments#action_59072 ] Lukas Theussl commented on MPMULTIPROJECT-59: - I cannot reproduce this with current maven 1.1-beta-3 trunk. Running multiproject:install on your test project instal

[jira] Updated: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-1908?page=all ] Brett Porter updated MNG-1908: -- Fix Version: (was: 2.0.3) 2.1 fix only applied to trunk > snapshots not deployed using m2, or deployed with uniqueVersion = false are > not updated

[jira] Updated: (MNG-2077) resolution fail after installing an artifact using an m2 build that was downloaded from a legacy repository

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-2077?page=all ] Brett Porter updated MNG-2077: -- Version: (was: 2.0.3) 2.1 Fix Version: (was: 2.0.3) 2.1 I'm removeing this fix from the branch due to slowness and instab

[maven2 build branches/maven-2.0.x - SUCCESS - update] Tue Feb 21 04:45:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060221.044501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.044501.txt - To unsubscribe, e-mai

[jira] Closed: (WAGON-34) CLONE -wagon-file failed when used by maven-site-plugin

2006-02-20 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/WAGON-34?page=all ] Brett Porter closed WAGON-34: - Resolution: Fixed > CLONE -wagon-file failed when used by maven-site-plugin > --- > > Key: WAGON-34 >

Re: plugin testing

2006-02-20 Thread Jesse McConnell
http://jira.codehaus.org/browse/MNG-2093 for the regular test case patch and then the plexified approach as well On 2/20/06, Jesse McConnell <[EMAIL PROTECTED]> wrote: > > ok, I fiddled around a bit today with the clean plugin as a basic test > case... > > I really don't like the idea of putting

[jira] Created: (MNG-2093) clean plugin unit test

2006-02-20 Thread Jesse McConnell (JIRA)
clean plugin unit test -- Key: MNG-2093 URL: http://jira.codehaus.org/browse/MNG-2093 Project: Maven 2 Type: Improvement Components: General Reporter: Jesse McConnell Priority: Minor Attachments: clean-plugin-normal-unit-test.patch,

[maven2 build trunk - SUCCESS - update] Tue Feb 21 04:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.040001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.040001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

[maven2 build trunk - SUCCESS - update] Tue Feb 21 03:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.030001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.030001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

[maven2 build trunk - SUCCESS - update] Tue Feb 21 02:30:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.023001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.023001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

RE: Rationale for which bugs make a release?

2006-02-20 Thread Brian E. Fox
I wouldn't -1 for this (especially for a new continuum release), although if there is a work around, I don't know of it. I tried many different things when this first occurred and eventually gave up. I'll patiently wait for 2.0.4 but I had the same impression for 2.0.3: that there was a test case

Re: [vote] [m1] plugin releases

2006-02-20 Thread Lukas Theussl
I don't know, is it a big difference to the beta-2s we have now? The scm plugin is rather crucial as none of the published versions work with namespaces in poms, see http://jira.codehaus.org/browse/MPRELEASE-16. I view this as a bug fix release mainly, I expect another release for maven 1.1-f

Re: [vote] [m1] plugin releases

2006-02-20 Thread Jason van Zyl
+1 Lukas Theussl wrote: Hi, Please vote on the release of the following m1 plugins: [] maven-artifact-plugin-1.8 [] maven-jxr-plugin-1.5 [] maven-scm-plugin-1.6 The artifact and scm releases are necessary now that the repository and release plugins are demoted, the jxr plugin was just waitin

Re: [vote] [m1] plugin releases

2006-02-20 Thread dan tran
maven-scm-api and providers will be 1.0 in a couple of weeks. Isn't it worth to wait for that release first for maven-scm-plugin? -D On 2/20/06, John Casey <[EMAIL PROTECTED]> wrote: > > +1 > > Lukas Theussl wrote: > > Hi, > > > > Please vote on the release of the following m1 plugins: > > > >

[maven2 build branches/maven-2.0.x - SUCCESS - checkout] Tue Feb 21 00:30:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060221.003001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060221.003001.txt - To unsubscribe, e-mai

Re: Rationale for which bugs make a release?

2006-02-20 Thread Brett Porter
Hi Brian, Some will be coming back in, but this probably won't be one. It's a difficult and risky fix with a known workaround (IIRC). It's a shame it got introduced initially, but now with a test case it will be easier to maintain after it is fixed. You're welcome to voice a -1 on the release vot

Re: [vote] [m1] plugin releases

2006-02-20 Thread John Casey
+1 Lukas Theussl wrote: Hi, Please vote on the release of the following m1 plugins: [] maven-artifact-plugin-1.8 [] maven-jxr-plugin-1.5 [] maven-scm-plugin-1.6 The artifact and scm releases are necessary now that the repository and release plugins are demoted, the jxr plugin was just waitin

[maven2 build trunk - SUCCESS - checkout] Tue Feb 21 00:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060221.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060221.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

Re: How to store and access plugin resources in maven 2

2006-02-20 Thread dan tran
use this.getClass().getClassLoader().getResourceAsStream( resourceLocation ); to copy your resource to where ever you want. -D On 2/20/06, Scott Ryan <[EMAIL PROTECTED]> wrote: > > In Maven 1 there was a way to store resources with your plugin that you > could easily access inside the plugin to

[maven2 build branches/maven-2.0.x - SUCCESS - update] Mon Feb 20 23:45:01 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060220.234502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060220.234502.txt - To unsubscribe, e-mai

[vote] [m1] plugin releases

2006-02-20 Thread Lukas Theussl
Hi, Please vote on the release of the following m1 plugins: [] maven-artifact-plugin-1.8 [] maven-jxr-plugin-1.5 [] maven-scm-plugin-1.6 The artifact and scm releases are necessary now that the repository and release plugins are demoted, the jxr plugin was just waiting for the first JXR relea

How to store and access plugin resources in maven 2

2006-02-20 Thread Scott Ryan
In Maven 1 there was a way to store resources with your plugin that you could easily access inside the plugin to copy out the resources etc. I used this for delivering templates etc. I accessed the directory via the plugin-resources parameter and it worked very well. Is there such a parameter av

Re: plugin testing

2006-02-20 Thread Jesse McConnell
ok, I fiddled around a bit today with the clean plugin as a basic test case... I really don't like the idea of putting setters on the mojo...not sure why, but it bugs me, probably because it is really only putting them there for testing purposes which is generally a no-no. 1) so I did it once wit

[maven2 build trunk - SUCCESS - update] Mon Feb 20 23:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060220.230001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060220.230001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

Re: Resource Filtering for War Plugin

2006-02-20 Thread Brian Topping
That's probably all we need to close discussion on it then. Brett had the idea of doing as plugin configuration. I'd rather err on the side of too verbose than confuse people. -b On Feb 20, 2006, at 3:22 AM, Stephen Duncan wrote: I'm like Brett, I haven't needed filtering in the webapp

Re: Rationale for which bugs make a release?

2006-02-20 Thread Carlos Sanchez
Take a look at my last attachment to see how an it test should be made as simple as possible On 2/20/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I tried to make it as easy as possible but maybe I could have done more. > This is a complicated issue because of the classloading so it requires > ins

[maven2 build trunk - SUCCESS - update] Mon Feb 20 22:00:00 GMT 2006

2006-02-20 Thread continuum
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060220.22.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060220.22.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

RE: Rationale for which bugs make a release?

2006-02-20 Thread Brian E. Fox
I tried to make it as easy as possible but maybe I could have done more. This is a complicated issue because of the classloading so it requires installation of a dependency in the repository to fully reproduce the issue. See the updated comment in the issue for the exact steps I just took to reprod

Re: Rationale for which bugs make a release?

2006-02-20 Thread Carlos Sanchez
Well, the easier the test case is to use the faster it's solved. If i have to spend a lot of time just setting up the environment it's likely that it'll be delayed. Please see my attached test cases for a better test case fully automated. On 2/20/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The j

Re: jdk 1.4 and 1.5 in same install?

2006-02-20 Thread David Blevins
We're not going enforce a forked-compiler/forked-tests hack on any projects that want to run in gbuild. That's the maven 1 way to solve problems. I'll setup another continuum install at some point and happily wait for the right feature. -David. On Feb 20, 2006, at 1:38 AM, Emmanuel Veni

RE: Rationale for which bugs make a release?

2006-02-20 Thread Brian E. Fox
The jar is included in the other attachment. It's hard to see with all the other comments, but this is how to reproduce: "Install the jar in test-1.0.zip to the local repo and build the plugin in test-case. Run the plugin by using mvn test:enhance In 2.0 it will print where it found the factory c

Re: Rationale for which bugs make a release?

2006-02-20 Thread Carlos Sanchez
The test case attached doesn't work, there're missing dependencies On 2/20/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I guess I'm a little confused about how something is decided which > release a fix goes into. Here's a good example: MNG-1898. This is > functionality that was broken between 2.

Rationale for which bugs make a release?

2006-02-20 Thread Brian E. Fox
I guess I'm a little confused about how something is decided which release a fix goes into. Here's a good example: MNG-1898. This is functionality that was broken between 2.0 and 2.0.1. It is listed as a blocker and has reproducible test cases associated with it, yet this one didn't make the 2.0.3

Re: RE: [m2] java 5's apt.exe as a compiler option?

2006-02-20 Thread Eddie O'Neil
JB-- The goal of the APT compiler wasn't to replace the patch at Codehaus; rather it was to make it possible to use "apt.exe" in place of "javac.exe" during the compilation phase. Since apt.exe is just a superset of javac.exe, it seemed to make sense to have the Plexus compiler implementations

[jira] Closed: (MPJXR-3) Uses pom.build.sourceDirectory instead of maven.compile.src.set

2006-02-20 Thread Lukas Theussl (JIRA)
[ http://jira.codehaus.org/browse/MPJXR-3?page=all ] Lukas Theussl closed MPJXR-3: - Resolution: Fixed Fix Version: 1.5 > Uses pom.build.sourceDirectory instead of maven.compile.src.set > -

[jira] Updated: (MNG-1703) is not propagated to child POMs

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1703?page=all ] John Casey updated MNG-1703: Fix Version: (was: 2.0.3) 2.0.4 > is not propagated to child POMs > > > Key: MN

[jira] Updated: (MNG-1994) Execution order of child plugins is arbitrary if inheritance is involved

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1994?page=all ] John Casey updated MNG-1994: Fix Version: (was: 2.0.3) 2.0.4 > Execution order of child plugins is arbitrary if inheritance is involved > -

[jira] Updated: (MNG-2081) Typing error in apt files

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2081?page=all ] John Casey updated MNG-2081: Fix Version: (was: 2.0.3) 2.0.4 > Typing error in apt files > - > > Key: MNG-2081 > URL: http://jira.codehaus.or

[jira] Updated: (MNG-2077) resolution fail after installing an artifact using an m2 build that was downloaded from a legacy repository

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2077?page=all ] John Casey updated MNG-2077: Fix Version: (was: 2.0.3) 2.0.4 > resolution fail after installing an artifact using an m2 build that was > downloaded from a legacy repository > ---

[jira] Updated: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1797?page=all ] John Casey updated MNG-1797: Fix Version: (was: 2.0.3) 2.0.4 > Dependency excludes apply to every subsequent dependency, not just the one it > is declared under. > --

[jira] Updated: (MNG-1898) Plugin classpath broken from 2.0 to 2.0.1

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1898?page=all ] John Casey updated MNG-1898: Fix Version: (was: 2.0.3) 2.0.4 > Plugin classpath broken from 2.0 to 2.0.1 > - > > Key: MNG-1898 >

[jira] Updated: (MNG-2048) Quote args in mvn script

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2048?page=all ] John Casey updated MNG-2048: Fix Version: (was: 2.0.3) 2.0.4 > Quote args in mvn script > > > Key: MNG-2048 > URL: http://jira.codehaus.org/

[jira] Updated: (MNG-1509) Profile activation by os doesn't work

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1509?page=all ] John Casey updated MNG-1509: Fix Version: (was: 2.0.3) 2.0.4 > Profile activation by os doesn't work > - > > Key: MNG-1509 > URL:

[jira] Updated: (MNG-1181) MavenEmbedder.execute() doesn't run reactor modules

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1181?page=all ] John Casey updated MNG-1181: Fix Version: (was: 2.0.3) 2.0.4 > MavenEmbedder.execute() doesn't run reactor modules > --- > > K

[jira] Updated: (MNG-1123) publish m2 component javadoc and reports

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1123?page=all ] John Casey updated MNG-1123: Fix Version: (was: 2.0.3) 2.0.4 > publish m2 component javadoc and reports > > > Key: MNG-1123 >

[jira] Updated: (MNG-1775) No property expansion in profile activation

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1775?page=all ] John Casey updated MNG-1775: Fix Version: (was: 2.0.3) 2.0.4 > No property expansion in profile activation > --- > > Key: MNG-1775 >

[jira] Updated: (MNG-1856) legacy layout tag in a profile does not show up in child pom.

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1856?page=all ] John Casey updated MNG-1856: Fix Version: (was: 2.0.3) 2.0.4 > legacy layout tag in a profile does not show up in child pom. >

[jira] Updated: (MNG-1999) Reporting inheritance does not work properly

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1999?page=all ] John Casey updated MNG-1999: Fix Version: (was: 2.0.3) 2.0.4 > Reporting inheritance does not work properly > > > Key: MNG-1999 >

[jira] Updated: (MNG-2078) Fixup super pom to activate the profile only when -DperformRelease=true.

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-2078?page=all ] John Casey updated MNG-2078: Fix Version: (was: 2.0.3) 2.0.4 > Fixup super pom to activate the profile only when -DperformRelease=true. > -

[jira] Closed: (MEV-338) JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists on ibiblio

2006-02-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MEV-338?page=all ] Carlos Sanchez closed MEV-338: -- Resolution: Fixed Fixed, jpox renamed to jpox-parent and jpox-core to jpox > JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists on ibiblio >

[jira] Reopened: (MEV-338) JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists on ibiblio

2006-02-20 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MEV-338?page=all ] Carlos Sanchez reopened MEV-338: > JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists on ibiblio > -- > >

[jira] Commented: (MDEPLOY-25) deploy:deploy-file installs the file in the local repository too (but it should not do that)

2006-02-20 Thread Geoffrey De Smet (JIRA)
[ http://jira.codehaus.org/browse/MDEPLOY-25?page=comments#action_59036 ] Geoffrey De Smet commented on MDEPLOY-25: - (both in the documentation and in the logging output would be nice) > deploy:deploy-file installs the file in the local repository to

[jira] Created: (MNG-2090) Project descriptor section anchors missing

2006-02-20 Thread Brian Fox (JIRA)
Project descriptor section anchors missing -- Key: MNG-2090 URL: http://jira.codehaus.org/browse/MNG-2090 Project: Maven 2 Type: Bug Components: Documentation: General Reporter: Brian Fox I noticed that the anchors

[jira] Commented: (MDEPLOY-25) deploy:deploy-file installs the file in the local repository too (but it should not do that)

2006-02-20 Thread Geoffrey De Smet (JIRA)
[ http://jira.codehaus.org/browse/MDEPLOY-25?page=comments#action_59035 ] Geoffrey De Smet commented on MDEPLOY-25: - fair enough, but could it deploy:deploy-file at least note that it's also installing it locally? > deploy:deploy-file installs the f

[jira] Commented: (MNG-2089) APT & AspectJ plugins

2006-02-20 Thread Trygve Laugstol (JIRA)
[ http://jira.codehaus.org/browse/MNG-2089?page=comments#action_59034 ] Trygve Laugstol commented on MNG-2089: -- How is this plugin different from the AspectJ plugin at mojo? See http://mojo.codehaus.org/aspectj-maven-plugin/ > APT & AspectJ plugins > -

[jira] Commented: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects

2006-02-20 Thread Eugene Kuleshov (JIRA)
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=comments#action_59032 ] Eugene Kuleshov commented on MNGECLIPSE-81: --- "Maven2 Managed Dependencies" library container does not work this way and I am not sure if we can disable choosing out conta

[jira] Updated: (MNG-1390) @requiresDependencyResolution in process-classes post compile

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1390?page=all ] John Casey updated MNG-1390: Assign To: (was: John Casey) > @requiresDependencyResolution in process-classes post compile > - > > K

[jira] Updated: (MNG-1560) Guide to accessing repository with https client authentication

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1560?page=all ] John Casey updated MNG-1560: Assign To: (was: John Casey) > Guide to accessing repository with https client authentication > -- > >

[jira] Updated: (MNG-868) Use uniform format for and other tags

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-868?page=all ] John Casey updated MNG-868: --- Assign To: (was: John Casey) > Use uniform format for and other tags > -- > > Key: MNG-868 > URL: http://ji

[jira] Updated: (MNG-655) don't load extensions into the main container

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-655?page=all ] John Casey updated MNG-655: --- Assign To: (was: John Casey) > don't load extensions into the main container > - > > Key: MNG-655 > URL: http://

[jira] Updated: (MNG-1906) properties not being replaced before being passed to plugins (specificaly the surefire plugin)

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1906?page=all ] John Casey updated MNG-1906: Assign To: (was: John Casey) > properties not being replaced before being passed to plugins (specificaly the > surefire plugin) >

[jira] Updated: (MNG-1982) wagons should be tolerant of incorrect configurations in entries within settings.xml

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1982?page=all ] John Casey updated MNG-1982: Assign To: (was: John Casey) > wagons should be tolerant of incorrect configurations in entries > within settings.xml > -

[jira] Updated: (MRELEASE-44) release:perform doesn't work at all without release.properties

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MRELEASE-44?page=all ] John Casey updated MRELEASE-44: --- Assign To: (was: John Casey) > release:perform doesn't work at all without release.properties > -- > >

[jira] Updated: (MNG-1489) test repository connection first time (get a file at / ?) for better error reporting

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1489?page=all ] John Casey updated MNG-1489: Assign To: (was: John Casey) > test repository connection first time (get a file at / ?) for better error > reporting > --

[jira] Updated: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MRELEASE-3?page=all ] John Casey updated MRELEASE-3: -- Assign To: (was: John Casey) > release:prepare should not require multimodule artifacts to be in the local > repository > --

[jira] Updated: (MNG-1962) allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation.

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1962?page=all ] John Casey updated MNG-1962: Assign To: (was: John Casey) > allow empty deprecation messages in plugin descriptor/annotation and document > usage of deprecation in descriptor/annotation. > --

[jira] Updated: (MNG-1465) Maven not able to find setter for MavenProjectHelper property

2006-02-20 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-1465?page=all ] John Casey updated MNG-1465: Assign To: (was: John Casey) > Maven not able to find setter for MavenProjectHelper property > - > > K

  1   2   >