[ http://jira.codehaus.org/browse/MOJO-286?page=all ]
Brian Fox reassigned MOJO-286:
--
Assign To: Brian Fox
> Sibling Dependency Not Included in copy-dependencies output during
> multi-project build
>
Sibling Dependency Not Included in copy-dependencies output during
multi-project build
--
Key: MOJO-286
URL: http://jira.codehaus.org/browse/MOJO-286
Project: Mojo
Type: Bug
Rep
[ http://jira.codehaus.org/browse/MOJO-135?page=comments#action_58090 ]
Dirk Sturzebecher commented on MOJO-135:
Just tried the same again with maven 2.0.2 and set my surefire to fork. Works
fine now. That is the result looks good on first inspection
Should be able to specify Cobertura on parent pom for all sub modules
-
Key: MOJO-285
URL: http://jira.codehaus.org/browse/MOJO-285
Project: Mojo
Type: Improvement
Components: cobertura
Repo
[ http://jira.codehaus.org/browse/MOJO-283?page=all ]
Brian Fox updated MOJO-283:
---
Version: 1.0
Fix Version: 1.1
> [dependency-maven-plugin] Override existing output file
> ---
>
> Key: MOJO-
[ http://jira.codehaus.org/browse/MOJO-283?page=comments#action_58073 ]
Brian Fox commented on MOJO-283:
The svn version 1.1 can do this currently. The code is undergoing a major
refactor but hasn't been checked in to svn yet so the current version is usable
[ http://jira.codehaus.org/browse/MOJO-283?page=all ]
Brian Fox reassigned MOJO-283:
--
Assign To: Brian Fox
> [dependency-maven-plugin] Override existing output file
> ---
>
> Key: MOJO-283
>
Alright, build-helper-maven-plugin stays at MOJO. I will realease it.
Thanks
-Dan
On 2/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
This is a good point. I think that we can keep it here.The main thing I was interested in is the artifact attachment, but IMO
that is something that should be m
Only the actual Cobertura jar is needed during test, just like Clover.
Note in MEV-321 that Carlos's solution excludes every dep. The issue is
that CoberturaInstrumentMojo.addCoberturaDependenciesToTestClasspath()
adds the cobertura artifact in such a manner that transitive deps are
pulled in also
Mike Perham wrote:
> Brett, I'm not an expert in Cobertura's usage of ASM. The POM says it
> requires 2.1 and I was not about to jump from 2.1 -> 1.5.3. Instead I
> focused on Cobertura's own best practice which is simply to not put ASM
> in the classpath during runtime.
cool - I'm sure its an i
Brett, I'm not an expert in Cobertura's usage of ASM. The POM says it
requires 2.1 and I was not about to jump from 2.1 -> 1.5.3. Instead I
focused on Cobertura's own best practice which is simply to not put ASM
in the classpath during runtime.
The issue is that Cobertura needs to be in the plug
Mike?
Brett Porter wrote:
> Sorry, I don't understand this.
>
> If older ASM's work with Cobertura, why isn't Cobertura changed to use
> the older ASM (or a range?) Why can't you use exclusions in the plugin,
> even if not changing the cobertura POM?
>
> Also, it shouldn't have been committed be
This is a good point. I think that we can keep it here.
The main thing I was interested in is the artifact attachment, but IMO
that is something that should be made easier in a later version of Maven.
- Brett
jerome lacoste wrote:
> On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>> I'm plen
[webstart] Getting maven variables in jnlp file
---
Key: MOJO-284
URL: http://jira.codehaus.org/browse/MOJO-284
Project: Mojo
Type: Improvement
Components: sandbox
Reporter: Hes Siemelink
Priority: Minor
I wo
[ http://jira.codehaus.org/browse/MOJO-274?page=comments#action_58037 ]
Michael Böckling commented on MOJO-274:
---
Thanks for the correction of the patch format, I was unaware of the guideline.
The thing that it fixed "pom" projects is nice, returning "n
[dependency-maven-plugin] Override existing output file
---
Key: MOJO-283
URL: http://jira.codehaus.org/browse/MOJO-283
Project: Mojo
Type: Improvement
Reporter: Laurent Berteau
Set an option to enable overwr
16 matches
Mail list logo
