[jira] Created: (MECLIPSE-457) Some dependencies are not listed in .classpath
Some dependencies are not listed in .classpath -- Key: MECLIPSE-457 URL: http://jira.codehaus.org/browse/MECLIPSE-457 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path Affects Versions: 2.5.1, 2.5, 2.4, 2.3 Environment: Maven 2.0.9, openSUSE 10.3, java version "1.5.0_15" Reporter: Grzegorz Kossakowski Attachments: myBlock.tar.gz In some situations plug-in does not list all transitive dependencies in .classpath file. The one I identified was with Cocoon-based application. If I have following entries in pom.xml: org.apache.cocoon cocoon-core 2.2.0 org.apache.cocoon cocoon-servlet-service-components 1.0.0 org.apache.cocoon cocoon-template-impl 1.1.0 org.apache.cocoon cocoon-forms-impl 1.1.0 org.apache.cocoon cocoon-ajax-impl 1.0.0 org.apache.cocoon cocoon-flowscript-impl 1.0.0 javax.servlet servlet-api 2.4 provided then output is fine, but when I change cocoon-servlet-service-components to 1.1.0-SNAPSHOT generated .classpath file does not contain dependency on excalibur-sourceresolve that is coming from: cocoon-core -> cocoon-pipeline-components cocoon-pipeline-impl -> excalibur-sourceresolve To make this bug more interesting I should share my observation that if I remove dependency on cocoon-ajax-impl then sourceresolve appears in .classpath again. However, this dependency is still there because cocoon-forms-impl has dependency on cocoon-ajax-impl. Sight... Couldn't this plug-in use the same dependency mechanism as compilation or dependency plug-in that resolve dependencies correctly? I attach simple application that exhibits described problem. In order to compile it with snapshot dependency you need to checkout and build Cocoon's trunk that can be found at: http://svn.eu.apache.org/repos/asf/cocoon/trunk/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MENFORCER-4) Typos in Version Range Specification document
Typos in Version Range Specification document - Key: MENFORCER-4 URL: http://jira.codehaus.org/browse/MENFORCER-4 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Reporter: Grzegorz Kossakowski Assignee: Brian Fox Priority: Minor In http://maven.apache.org/plugins/maven-enforcer-plugin/rules/versionRanges.html there two typos in table: (1.0,2.0) 1.0 >= x <= 2.0 should be: (1.0,2.0) 1.0 > x < 2.0 and: [1.0,2.0] 1.0 > x < 2.0 should be: (1.0,2.0) 1.0 >= x <= 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2339) ${project.*} are interpreted in the wrong place
[
http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122231
]
Grzegorz Kossakowski commented on MNG-2339:
---
Guys, the situation with this issue is really, really annoying.
The issue is more than one year old, affects so many people that most of them
(including me) sees it as the most ugliest unresolved bug in Maven. I don't
know why you require any IT even if there are many projects (Apache Cocoon,
Jetty plug-in, Spring to name a few) that exhibit behaviour described in this
issue.
At Apache Cocoon, we have many poms polluted just because of this issue and our
users who being worried about whole Maven thing are hit by it at the nearly
beginning, see: http://article.gmane.org/gmane.text.xml.cocoon.user/63302 for
latest example. It's not perfect first expierience, don't you think?
Demanding any additional action for such embarrassing bug is just a PITA, IMHO.
Sorry for a little rant but I think it's the time to say: enough is enough.
Devoted Maven user,
Grzegorz
> ${project.*} are interpreted in the wrong place
> ---
>
> Key: MNG-2339
> URL: http://jira.codehaus.org/browse/MNG-2339
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.4
>Reporter: Emmanuel Venisse
>Assignee: Kenney Westerhof
>Priority: Critical
> Fix For: 2.0.9
>
>
> If a plugin use ${project.version}, this parameter is interpreted with the
> version of the current project and not the plugin version. I think we have
> the same pb with dependencies and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT,
> ${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT
> instead of 2.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
