[
https://jira.codehaus.org/browse/MDEP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306193#comment-306193
]
Jason Chaffee edited comment on MDEP-366 at 8/14/12 8:04 PM:
-
Seeing the
[
https://jira.codehaus.org/browse/MDEP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306193#comment-306193
]
Jason Chaffee commented on MDEP-366:
Seeing the same error.
> NPE when running s
Performance is really bad for large artifacts
-
Key: MDEP-230
URL: http://jira.codehaus.org/browse/MDEP-230
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: unpack
Dependency plugin seems to unpack archive even, if it is already unpacked
-
Key: MDEP-225
URL: http://jira.codehaus.org/browse/MDEP-225
Project: Maven 2.x Dependency Plugin
[
http://jira.codehaus.org/browse/MNG-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175096#action_175096
]
Jason Chaffee commented on MNG-2426:
James,
How does this work with custom packaging and custom ty
[
http://jira.codehaus.org/browse/MNG-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171245#action_171245
]
Jason Chaffee commented on MNG-4114:
As a side note, I apologize for not trying the latest assembly
[
http://jira.codehaus.org/browse/MNG-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171244#action_171244
]
Jason Chaffee commented on MNG-4114:
This looks to be a bug in the maven-assembly plugin. I change
[
http://jira.codehaus.org/browse/MNG-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171243#action_171243
]
Jason Chaffee commented on MNG-4114:
Also note that I tried this with maven-install-plugin 2.2 and
Maven is installing artifacts with the wrong extension and in some cases not
even installing artfiacts it should be installing
--
Key: MNG-4114
[
http://jira.codehaus.org/browse/MARTIFACT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169611#action_169611
]
Jason Chaffee commented on MARTIFACT-35:
Ok, this is the dialogue I was hoping for. :)
Ag
[
http://jira.codehaus.org/browse/MARTIFACT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169606#action_169606
]
Jason Chaffee commented on MARTIFACT-35:
I can understand where you are coming from that yo
[
http://jira.codehaus.org/browse/MARTIFACT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169603#action_169603
]
Jason Chaffee commented on MARTIFACT-35:
I wasn't suggesting supporting N variants. I was
Allow the ability to "plugin" or "inject" different versioning implementations
--
Key: MARTIFACT-35
URL: http://jira.codehaus.org/browse/MARTIFACT-35
Project: Maven Artifact
[
http://jira.codehaus.org/browse/MNG-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167054#action_167054
]
Jason Chaffee commented on MNG-2426:
I am of the opinion that this is a bug in Plexus.
I am real
[
http://jira.codehaus.org/browse/MNG-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164151#action_164151
]
Jason Chaffee commented on MNG-2426:
I just ran into this same issue with maven-2.0.9
> Artifact c
[
http://jira.codehaus.org/browse/MRM-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123370
]
Jason Chaffee commented on MRM-691:
---
The NPE came back when the database update ran.
> Can't get any of the consumers to work
[
http://jira.codehaus.org/browse/MRM-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123361
]
jasonchaffee edited comment on MRM-691 at 2/12/08 1:13 AM:
I shutdown archiva and restarted it and t
[
http://jira.codehaus.org/browse/MRM-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123361
]
Jason Chaffee commented on MRM-691:
---
I shutdown archiva and restarted it and then I ran the repostiory scan and the
NPE's are
Can't get any of the consumers to work without through a NPE
Key: MRM-691
URL: http://jira.codehaus.org/browse/MRM-691
Project: Archiva
Issue Type: Bug
Components: reposi
Please upgrade to ant-1.7.0 from an-1.6.5
-
Key: MANTRUN-79
URL: http://jira.codehaus.org/browse/MANTRUN-79
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Reporter: Jason Chaffee
We hav
[
http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91827
]
Jason Chaffee commented on SUREFIRE-316:
The version is being set in a parent pom that has the . The
configuration
[
http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91815
]
Jason Chaffee commented on SUREFIRE-316:
Ok, I will create a new issue. I have stated on several occasions that I
[
http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91810
]
Jason Chaffee commented on SUREFIRE-316:
> > This works fine in maven-2.0.5.
> >
> > I have the following surefire c
Update depencies to include all ant artifacts so all ant tasks can be used
--
Key: MANTRUN-58
URL: http://jira.codehaus.org/browse/MANTRUN-58
Project: Maven 2.x Antrun Plugin
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68734
]
Jason Chaffee commented on MSUREFIRE-134:
-
Thanks so much Jesse, you are a life saver. :)
> Surefire finds test classes but ignores test methods and configuration
> metho
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68627
]
Jason Chaffee commented on MSUREFIRE-134:
-
Jesse,
It looks pretty good. However, this is one issue with the testng.xml...it
works if I specify classes, but it does not wo
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68542
]
Jason Chaffee commented on MSUREFIRE-134:
-
Can you try JUnit tests with testng and a testng.xml? I would like confirm
that it doesn't work or that there is something screw
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68540
]
Jason Chaffee commented on MSUREFIRE-134:
-
I should add that I started with a clean repository, applied the patch...built
surefire and the surfire plugin. Is there a snaps
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68539
]
Jason Chaffee commented on MSUREFIRE-134:
-
I am not sure...my tests that were being run with a testng.xml file are not
being run now either.
> Surefire finds test classes
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68537
]
Jason Chaffee commented on MSUREFIRE-134:
-
It fixes TestNG, but it breaks JUnit tests that are being run by TestNGthey
no longer run. This a problem because we have bo
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68533
]
Jason Chaffee commented on MSUREFIRE-134:
-
If you do that TestNG will run them as JUnit tests and not honor any of the
annotations. Anyway, this is a pretty nasty bug. I
[ http://jira.codehaus.org/browse/MSUREFIRE-134?page=comments#action_68528
]
Jason Chaffee commented on MSUREFIRE-134:
-
MSUREFIRE-117 IS the same as this bug...or at least they are caused by the same
issue. Jesse is correct that patch in MSUREFIRE-
Surefire doesn't work if testng is in the classpath and a suitexml isn't being
used
---
Key: MSUREFIRE-117
URL: http://jira.codehaus.org/browse/MSUREFIRE-117
Project: Maven 2.x Surefire Plugin
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65336
]
Jason Chaffee commented on MSUREFIRE-105:
-
Ok, the problem that was exposed was related to an experimental feature in
xerces that I was using. I refactored my code and eve
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65256
]
Jason Chaffee commented on MSUREFIRE-105:
-
Just tried it with no luck. I should add that these tests were working before
applying the patch (on linux). Therefore, while t
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65247
]
Jason Chaffee commented on MSUREFIRE-105:
-
The patch fixed the issue, but it exposed another issue. Now, my tests are
running but they are failing due to some xml parser i
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65244
]
Jason Chaffee commented on MSUREFIRE-105:
-
I just tested this on Linux and on Windows and it works on Linux, but not on
Windows. Therefore, I am almost positive it is due
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65203
]
Jason Chaffee commented on MSUREFIRE-105:
-
I will create a test project that I can upload within a couple of days.
Also, I am now having this same problem with multiple pro
[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65177
]
Jason Chaffee commented on MSUREFIRE-105:
-
I have traced this issue to the following line of code in SurefireBooter:
returnCode = CommandLineUtils.executeCommandLine( cli,
Surefire plugin fails with certain dependencies in pom
--
Key: MSUREFIRE-105
URL: http://jira.codehaus.org/browse/MSUREFIRE-105
Project: Maven 2.x Surefire Plugin
Type: Bug
Environment: This was tested with the tr
[ http://jira.codehaus.org/browse/MASSEMBLY-92?page=comments#action_64698 ]
Jason Chaffee commented on MASSEMBLY-92:
Another option would be add configuration to the assembly descriptor that would
allow an author to fail or not fail if this error is
Assembly plugin fails with fatal error if a particular fileset directory does
not exist
---
Key: MASSEMBLY-92
URL: http://jira.codehaus.org/browse/MASSEMBLY-92
Project: Maven 2.x Assembly Pl
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64678 ]
Jason Chaffee commented on MASSEMBLY-89:
Ignore my last message, it appears there was a glitch with eclipse during the
merge and I didn't get part of the update...so, I was m
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64677 ]
Jason Chaffee commented on MASSEMBLY-89:
I just checked out the fix and I still have the same problem. Am I missing
something?
> outputFileNameMapping broken
>
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64601 ]
Jason Chaffee commented on MASSEMBLY-89:
I just reviewed the added unit tests and they do not use an
InterpolationFilterReader to load the assembly descriptors as the
Abstra
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64578 ]
Jason Chaffee commented on MASSEMBLY-89:
I am seeing the same behavior when building the assembly plugin from the trunk.
Basically, it is interpolating all ${artifactId} in
[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=all ]
Jason Chaffee updated MASSEMBLY-90:
---
Attachment: AbstractAssemblyMojo-patch.txt
descriptor.mdo-patch-.txt
component.mdo-patch.txt
> add a DependencySet filter bas
[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=all ]
Jason Chaffee updated MASSEMBLY-90:
---
Attachment: descriptor.mdo
component.mdo
AbstractAssemblyMojo.java
> add a DependencySet filter based on type
> -
[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=all ]
Jason Chaffee updated MASSEMBLY-90:
---
Attachment: AssemblyTypeArtifactFilter.java
AssemblyClassifierArtifactFilter.java
AbstractAssemblyMojo.java
> add a Dependenc
[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=comments#action_64515 ]
Jason Chaffee commented on MASSEMBLY-90:
It would be nice to add a classifier filter as well.
> add a DependencySet filter based on type
> ---
add a DependencySet filter based on type
Key: MASSEMBLY-90
URL: http://jira.codehaus.org/browse/MASSEMBLY-90
Project: Maven 2.x Assembly Plugin
Type: Improvement
Reporter: Jason Chaffee
Attachments: AbstractAssemblyMojo.
51 matches
Mail list logo