[jira] [Commented] (MSHARED-456) Removed @Deprecated marked code
[ https://issues.apache.org/jira/browse/MSHARED-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995164#comment-14995164 ] Karl Heinz Marbaise commented on MSHARED-456: - Followup [r1713107|http://svn.apache.org/r1713107] > Removed @Deprecated marked code > --- > > Key: MSHARED-456 > URL: https://issues.apache.org/jira/browse/MSHARED-456 > Project: Maven Shared Components > Issue Type: Task > Components: maven-filtering >Affects Versions: maven-filtering-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-filtering-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-464) Upgrade user documentation
[
https://issues.apache.org/jira/browse/MSHARED-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-464.
---
Resolution: Fixed
Assignee: Karl Heinz Marbaise
Fixed in [r1713108|http://svn.apache.org/r1713108]
> Upgrade user documentation
> --
>
> Key: MSHARED-464
> URL: https://issues.apache.org/jira/browse/MSHARED-464
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-filtering
>Affects Versions: maven-filtering-3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-filtering-3.0.0
>
>
> The current usage page contains information using XDoclet:
> {noformat}
> /**
> * @component
> role="org.apache.maven.shared.filtering.MavenResourcesFiltering"
> *role-hint="default"
> * @required
> */
> private MavenResourcesFiltering mavenResourcesFiltering;
> {noformat}
> which should be updated to use annotation based usage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-449) Upgrade to Maven 3.X only.
[ https://issues.apache.org/jira/browse/MSHARED-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-449: Description: Upgrade maven-plugin-testing-harness from 1.2 to 2.1, change maven-artifact to maven-core, JDK 6 (was: Upgrade maven-plugin-testing-harness from 1.2 to 2.1, change maven-artifact to maven-core) > Upgrade to Maven 3.X only. > -- > > Key: MSHARED-449 > URL: https://issues.apache.org/jira/browse/MSHARED-449 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-mapping >Affects Versions: maven-mapping-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-mapping-3.0.0 > > > Upgrade maven-plugin-testing-harness from 1.2 to 2.1, change maven-artifact > to maven-core, JDK 6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5927) maven does not honour configured in some cases
[ https://issues.apache.org/jira/browse/MNG-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995315#comment-14995315 ] Igor Fedorenko commented on MNG-5927: - Pushed axample project to https://github.com/ifedorenko/MNG-5927-dependency-parent-repository > maven does not honour configured in some cases > - > > Key: MNG-5927 > URL: https://issues.apache.org/jira/browse/MNG-5927 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Igor Fedorenko > > There appear to be a bug in artifact descriptor cache implemented in aether > DefaultDependencyCollector. The cache allows use of cached descriptors when > descriptor parent(s) are not accessible from any enabled repository. > This is particularly problematic during multithreaded builds, where timing of > individual module project builds is not guaranteed, and the invalid artifact > descriptor cache implementation can result in infrequent and hard to > troubleshoot dependency resolution failures. > I'll provide small standalone example project that demonstrates the problem > shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-5927) maven does not honour configured in some cases
Igor Fedorenko created MNG-5927: --- Summary: maven does not honour configured in some cases Key: MNG-5927 URL: https://issues.apache.org/jira/browse/MNG-5927 Project: Maven Issue Type: Bug Components: Artifacts and Repositories Reporter: Igor Fedorenko There appear to be a bug in artifact descriptor cache implemented in aether DefaultDependencyCollector. The cache allows use of cached descriptors when descriptor parent(s) are not accessible from any enabled repository. This is particularly problematic during multithreaded builds, where timing of individual module project builds is not guaranteed, and the invalid artifact descriptor cache implementation can result in infrequent and hard to troubleshoot dependency resolution failures. I'll provide small standalone example project that demonstrates the problem shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
