You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/05/11 07:59:49 UTC

[jira] Closed: (SLING-1517) Get rid of Maven 3 warnings

     [ https://issues.apache.org/jira/browse/SLING-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-1517.
-----------------------------------


> Get rid of Maven 3 warnings
> ---------------------------
>
>                 Key: SLING-1517
>                 URL: https://issues.apache.org/jira/browse/SLING-1517
>             Project: Sling
>          Issue Type: Improvement
>          Components: API, Commons, General, JCR, Launchpad, Maven Plugins, Scripting
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>            Priority: Minor
>             Fix For: Scripting JSP-Taglib 2.1.0, Scripting JSP 2.0.10, Scripting JavaScript 2.0.8, Parent 9, Maven Sling Plugin 2.0.6, Maven JCROCM Plugin 2.0.6, Launchpad Bundles 6, JCR Resource 2.0.8, JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access Manager 2.0.6, Commons Mime 2.1.6, Commons JSON 2.0.6, API 2.1.0, JCM OCM 2.0.6
>
>
> Maven 3 has a stricter, yet backwards-compatbile, POM parser. Sling poms use a few deprecated features which should be changed:
> * ${pom.version} -> ${project.version}
> * ${artifactId} -> ${project.artifactId}
> * ensure all plugins and reports have versions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.