[jira] Commented: (MNG-5041) Scope of dependecies defined in Dependecy Management can't be overriden
[ http://jira.codehaus.org/browse/MNG-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260161#action_260161 ] Arnaud Heritier commented on MNG-5041: -- Benjamin did you try with the depMgt in a parent pom and the dep in a child ? It is how I understand the explained testcase. Emmanuel, can you provide a little testcase to reproduce it ? > Scope of dependecies defined in Dependecy Management can't be overriden > --- > > Key: MNG-5041 > URL: http://jira.codehaus.org/browse/MNG-5041 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.2, 3.0.3 > Environment: Linux x64 JDK 1.60_24 >Reporter: Emmanuel Hugonnet >Assignee: Benjamin Bentmann >Priority: Blocker > Attachments: MNG-5041.zip > > > If I define a dependency with in a parent pom using dependency management I > can't override the scope of the dependency management declaration in a child > pom. > If I use the dependency plugin the tree is as expected (the child override > the parent) but if I use the effective-pom I get what is declared in the > dependency management. > This seems a Maven 3.0.x bug -- 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-5041) Scope of dependecies defined in Dependecy Management can't be overriden
[ http://jira.codehaus.org/browse/MNG-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260166#action_260166 ] Emmanuel Hugonnet commented on MNG-5041: Yes, Silverpeas poms on github ;) )After more investigations using the latest help plugin and effective pom all is working fine. It seems to come from a bug in the assembly plugin (2.2beta5) which was fixed in 2.2.1. The fact that the dependency plugin display wrong informations lead us to creating this bug. Sorry for the inconvenience. > Scope of dependecies defined in Dependecy Management can't be overriden > --- > > Key: MNG-5041 > URL: http://jira.codehaus.org/browse/MNG-5041 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.2, 3.0.3 > Environment: Linux x64 JDK 1.60_24 >Reporter: Emmanuel Hugonnet >Assignee: Benjamin Bentmann >Priority: Blocker > Attachments: MNG-5041.zip > > > If I define a dependency with in a parent pom using dependency management I > can't override the scope of the dependency management declaration in a child > pom. > If I use the dependency plugin the tree is as expected (the child override > the parent) but if I use the effective-pom I get what is declared in the > dependency management. > This seems a Maven 3.0.x bug -- 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: (MANTTASKS-216) pom ant task does not considers settings.xml and proxy
[
http://jira.codehaus.org/browse/MANTTASKS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260170#action_260170
]
Ravi commented on MANTTASKS-216:
Hi,
Can someone pick this up, it needs urgent attention?
Appreciate your help.
Regards,
Ravi.
> pom ant task does not considers settings.xml and proxy
> --
>
> Key: MANTTASKS-216
> URL: http://jira.codehaus.org/browse/MANTTASKS-216
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: pom task
>Affects Versions: 2.1.0, 2.1.1
>Reporter: Ravi
>
> We use pom for our project and ant to build the zip file of the release. Ant
> script uses the "pom" ant task, but when it executes it, it seems to ignore
> the proxy defined in the settings.xml. Our repositories are outside our
> domain, so we need the proxies. I tried using "proxy" task as well, but that
> also didn't help. I also specifying the settings file with the task, but it
> didn't work.
> xmlns:mvn="antlib:org.apache.maven.artifact.ant">
>username="user" password="pass" />
>
>
>
> Can you please suggest what's going on? Here is the output of the ant script
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dist>ant assemble -v
> Apache Ant version 1.7.1 compiled on June 27 2008
> Buildfile: build.xml
> Detected Java version: 1.6 in: C:\java\jdk1.6.0_20\jre
> Detected OS: Windows XP
> parsing buildfile
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dist\build.xml with URI =
> file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-
> dist/build.xml
> Project base dir set to:
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dist
> [antlib:org.apache.tools.ant] Could not load definitions from resource
> org/apache/tools/ant/antlib.xml. It could not be found.
> Importing file
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dist\auto-deploy-build.xml
> from C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dis
> t\build.xml
> parsing buildfile
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\server-dist\auto-deploy-build.xml
> with URI = file:/C:/projects/eclipseWorkspace-3.6/vs-2.
> 1.11/server-dist/auto-deploy-build.xml
> [property] Loading Environment env.
> parsing buildfile
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/maven-ant-tasks-2.1.1.jar!/org/apache/maven/artifact/ant/antlib
> .xml with URI =
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/maven-ant-tasks-2.1.1.jar!/org/apache/maven/artifact/ant/antlib.x
> ml
> parsing buildfile
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/svnant.jar!/org/tigris/subversion/svnant/svnantlib.xml
> with URI
> =
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/svnant.jar!/org/tigris/subversion/svnant/svnantlib.xml
> parsing buildfile
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/ant-contrib.jar!/net/sf/antcontrib/antlib.xml
> with URI = jar:fi
> le:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/ant-contrib.jar!/net/sf/antcontrib/antlib.xml
> parsing buildfile
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/ant-classloadertask.jar!/net/jtools/classloadertask/antlib.xml
> with URI =
> jar:file:/C:/projects/eclipseWorkspace-3.6/vs-2.1.11/server-dist/lib/ant-classloadertask.jar!/net/jtools/classloadertask/antlib.xml
> Trying to override old definition of task classloader
> Property "agent.home.dir" has not been set
> [echo] maven to use: mvn
> Property "agent.home.dir" has not been set
> [echo] agent.home.dir: ${agent.home.dir}
> [echo] os: Windows XP
> [dependencies] Maven Ant Tasks version: 2.1.1
> [dependencies] Loading Maven settings file:
> C:\projects\eclipseWorkspace-3.6\vs-2.1.11\settings.xml
> [dependencies] Loading Maven settings file:
> C:\apache-maven-2.0.9\conf\settings.xml
> [dependencies] Using local repository: c:\Documents and
> Settings\sukhravi\.m2\repository
> [pom] Loading Maven settings file: c:\Documents and
> Settings\sukhravi\.m2\settings.xml
> [pom] Loading Maven settings file:
> C:\apache-maven-2.0.9\conf\settings.xml
> [dependencies] Downloading: com/db/ged/vs/vs/2.1.11/vs-2.1.11.pom from
> repository ga at http://longad2.uk.db.com:9500/maven2
> [dependencies] Unable to locate resource in repository
> [dependencies] [INFO] Unable to find resource 'com.db.ged.vs:vs:pom:2.1.11'
> in repository ga (http://longad2.uk.db.com:9500/maven2)
> [dependencies] Downloading: com/db/ged/vs/vs/2.1.11/vs-2.1.11.pom from
> repository nexus-ged-maven-repo at
> http://cu011.cubit.dbcde.com/content/groups/
> GedItMavenRepo
> [dependencies] Error transferring file: Connection timed out: connect
> [dependencies] [WARNING] Unable to get resource 'com.db.ged.vs:vs:pom:2.1.11'
> from repository nexus-ged-maven-repo
[jira] Created: (MSKINS-10) Suppress line wrapping in navigation caused by spaced or hyphens
Suppress line wrapping in navigation caused by spaced or hyphens -- Key: MSKINS-10 URL: http://jira.codehaus.org/browse/MSKINS-10 Project: Maven Skins Issue Type: Improvement Components: Default Skin Environment: Maven 2.2.1, maven-site-plugin 2.2 Reporter: Michael Hinterseher Priority: Minor Long navigation entries are wrapped by browser. This reduces the usability of the navigation tree. In combination with the nice on mouse over showing the full text the navigation readability would improve if line wrapping would be suppressed. Change items in navigation from to Or define a class and a style for it. -- 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: (MSKINS-10) Suppress line wrapping in navigation caused by spaced or hyphens
[ http://jira.codehaus.org/browse/MSKINS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260172#action_260172 ] Michael Hinterseher commented on MSKINS-10: --- PS: Please fix the title of this ticket spaced -> spaces :-) > Suppress line wrapping in navigation caused by spaced or hyphens > -- > > Key: MSKINS-10 > URL: http://jira.codehaus.org/browse/MSKINS-10 > Project: Maven Skins > Issue Type: Improvement > Components: Default Skin > Environment: Maven 2.2.1, maven-site-plugin 2.2 >Reporter: Michael Hinterseher >Priority: Minor > > Long navigation entries are wrapped by browser. This reduces the usability of > the navigation tree. > In combination with the nice on mouse over showing the full text the > navigation readability would improve if line wrapping would be suppressed. > Change items in navigation from > > to > > Or define a class and a style for it. -- 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: (SUREFIRE-713) Allow setting of excludes and includes via text files
[ http://jira.codehaus.org/browse/SUREFIRE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260173#action_260173 ] Kristian Rosenvold commented on SUREFIRE-713: - By a quick look at the diff the patch looks good. I tend to view this issue in context with a group of other issues like SUREFIRE-131, SUREFIRE-530, SUREFIRE-526, SUREFIRE-632, SUREFIRE-561, SUREFIRE-528, SUREFIRE-701, SUREFIRE-582. I'm not saying we need to solve all of these issues, not even that the relationship is close; but they seem, to be touching on the same feature set. I think we need to discuss what features we need/want to implement for this cluster of issues as a group rather than adding features piece by piece without an overall plan. > Allow setting of excludes and includes via text files > - > > Key: SUREFIRE-713 > URL: http://jira.codehaus.org/browse/SUREFIRE-713 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: Backlog >Reporter: Andrew Bayer > Attachments: excludeIncludeFile.patch > > > It'd be handy in some circumstances to be able to read the excludes (and > includes) from text files. This would allow for dynamically determining which > tests to skip or include (for whatever reason) before the tests are executed, > or for pulling in a list of tests to exclude/include from an external source, > etc. We're planning to use this at Cloudera for segregating "flaky" tests > from our primary test runs (and vice versa). Patch attached, though I'm sure > it could still use work. -- 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: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260174#action_260174 ] Kristian Rosenvold commented on SUREFIRE-690: - The issue you're seeing now is actually a design problem with parallel providers and redirectTestOuputToFile=true. (All the others issues we've been having with 2.7.X-2.8 and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- 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] Issue Comment Edited: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260174#action_260174 ] Kristian Rosenvold edited comment on SUREFIRE-690 at 3/15/11 5:12 AM: -- The issue you're seeing now is actually a design problem with parallel surefire providers and redirectTestOuputToFile=true, because you're running parallel junit (and parallel m3, which is not relevant). (All the others issues we've been having with 2.7.X and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. was (Author: krosenvold): The issue you're seeing now is actually a design problem with parallel surefire providers and redirectTestOuputToFile=true, because you're running parallel junit (and parallel m3, which is not relevant). (All the others issues we've been having with 2.7.X-2.8 and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- 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] Issue Comment Edited: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260174#action_260174 ] Kristian Rosenvold edited comment on SUREFIRE-690 at 3/15/11 5:11 AM: -- The issue you're seeing now is actually a design problem with parallel surefire providers and redirectTestOuputToFile=true, because you're running parallel junit (and parallel m3, which is not relevant). (All the others issues we've been having with 2.7.X-2.8 and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. was (Author: krosenvold): The issue you're seeing now is actually a design problem with parallel providers and redirectTestOuputToFile=true. (All the others issues we've been having with 2.7.X-2.8 and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- 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] Issue Comment Edited: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260174#action_260174 ] Kristian Rosenvold edited comment on SUREFIRE-690 at 3/15/11 5:12 AM: -- The issue you're seeing now is actually a design problem with parallel surefire providers and redirectTestOuputToFile=true, because you're running parallel junit (and parallel m3, which is not relevant). (All the others issues we've been having with 2.7.X and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn off parallel junit *or* redirectTestOuputToFile. was (Author: krosenvold): The issue you're seeing now is actually a design problem with parallel surefire providers and redirectTestOuputToFile=true, because you're running parallel junit (and parallel m3, which is not relevant). (All the others issues we've been having with 2.7.X and redirectTestOuputToFile= true have been just basic thread safety issues that affect all users of redirectTestOuputToFile). Until we fixed SUREFIRE-700 there was no way to fix this issue, but now that this is done it should be much simpler. I am working on this for 2.8.1. Until then, the only way to make this reliable is either to turn of parallel junit *or* redirectTestOuputToFile. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- 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-115) Require property rule evaluates empty property to "true"
Require property rule evaluates empty property to "true" Key: MENFORCER-115 URL: http://jira.codehaus.org/browse/MENFORCER-115 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0 Reporter: Michael Osipov I want to enforce a property to be set to any value. -Dprop=value => correct -Dprop= => fails as expected -Dprop => not correct This is incorrect behavior. The EnforceRuleHelper evaluates the property to "true". This means that "true" has to be explicitly excluded in the regex. This is ugly. There must be an option to enforce an non-empty property. -- 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-116) Require property rule interpolation does not work like profile activation
Require property rule interpolation does not work like profile activation
-
Key: MENFORCER-116
URL: http://jira.codehaus.org/browse/MENFORCER-116
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.0
Reporter: Michael Osipov
Priority: Critical
The main benefit of profile activation is that a profile is activated by a
property set *outside* of maven. It does not make any sense to active by a
property if it is defined in the POM.
If I set the following in my properties section:
{noformat}
{noformat}
This would evaluate the property to "true" and pass the enforcer rule. It makes
absolutely no sense. Properties should be evaluated the same way as in the
profile activation. POM properties are always present, thus making the hole
enforcer thing obsolete.
This issue is related to MENFORCER-115.
--
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: (MWAR-251) parent project dependencyManagement for test submodule causes adding unnecessary libraries to war
parent project dependencyManagement for test submodule causes adding unnecessary libraries to war - Key: MWAR-251 URL: http://jira.codehaus.org/browse/MWAR-251 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1-beta-1 Reporter: Vedran Vidović Attachments: ParentProject.zip Unnecessary libraries are added in a war when we define transitive test dependencies of submodule used in test scope of war project: - create a parent project with a war submodule and a jar submodule (in attachment: ParentProject, WarProject, TestProject) - use depencencyManagement in parent pom.xml for setting versions of dependencies - add a dependency to jar submodule (which is declared in parent pom.xml in dependencyManagement) - add jar submodule as a dependency to war submodule in test scope - call "mvn clean package" on parent project --> dependencies of jar submodule will be copied to war's WEB-INF/lib directory (IT SHOULDN'T HAPPEN) - if we don't add dependency for jar submodule to dependencyManagement in parent pom.xml problem doesn't appear See attached zip of mvn project with two submodules. -- 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
Unable to set targetJdk
Hi, i just decided to use PMD plugin to get some info about complexity. I used this in my pom.xml: * org.apache.maven.plugins maven-pmd-plugin 2.5 1.5 * bit i always get: Can't use annotations when running in JDK 1.4 mode! how this can be solved ?? regards.
[jira] Created: (MDEP-307) Version range doesn't work
Version range doesn't work
--
Key: MDEP-307
URL: http://jira.codehaus.org/browse/MDEP-307
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Win XP, Eclipse 3.6.1
Reporter: SirWayne
Assignee: Brian Fox
Priority: Critical
I want to use a version range in my dependencies, but it doesn't work. If i use
the fix version, all works fine. In my repo the version is
org.eclipse.emf:common:jar:2.6.0
{code:xml}
org.eclipse.emf
common
[2.5.0,4.0.0)
{code}
Error
[ERROR] An error occurred during dependency resolution of the following
artifact:
org.eclipse.emf:common:null
Caused by: No versions are present in the repository for the artifact with a
range [2.5.0,4.0.0)
org.eclipse.emf:common:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
myrepo(http://myRepo/m2repository)
Path to dependency:
1) xyz:jar:1.0.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] Updated: (MSKINS-10) Suppress line wrapping in navigation caused by spaces or hyphens
[ http://jira.codehaus.org/browse/MSKINS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSKINS-10: -- Summary: Suppress line wrapping in navigation caused by spaces or hyphens (was: Suppress line wrapping in navigation caused by spaced or hyphens ) > Suppress line wrapping in navigation caused by spaces or hyphens > -- > > Key: MSKINS-10 > URL: http://jira.codehaus.org/browse/MSKINS-10 > Project: Maven Skins > Issue Type: Improvement > Components: Default Skin > Environment: Maven 2.2.1, maven-site-plugin 2.2 >Reporter: Michael Hinterseher >Priority: Minor > > Long navigation entries are wrapped by browser. This reduces the usability of > the navigation tree. > In combination with the nice on mouse over showing the full text the > navigation readability would improve if line wrapping would be suppressed. > Change items in navigation from > > to > > Or define a class and a style for it. -- 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: (SUREFIRE-713) Allow setting of excludes and includes via text files
[ http://jira.codehaus.org/browse/SUREFIRE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260217#action_260217 ] Andrew Bayer commented on SUREFIRE-713: --- Sounds reasonable to me. I'll try to extend what I've already got to allow specifying exclude/include patterns as -D properties, at the very least. > Allow setting of excludes and includes via text files > - > > Key: SUREFIRE-713 > URL: http://jira.codehaus.org/browse/SUREFIRE-713 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: Backlog >Reporter: Andrew Bayer > Attachments: excludeIncludeFile.patch > > > It'd be handy in some circumstances to be able to read the excludes (and > includes) from text files. This would allow for dynamically determining which > tests to skip or include (for whatever reason) before the tests are executed, > or for pulling in a list of tests to exclude/include from an external source, > etc. We're planning to use this at Cloudera for segregating "flaky" tests > from our primary test runs (and vice versa). Patch attached, though I'm sure > it could still use work. -- 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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
site:attach-descriptor removes all comments and filters the content --- Key: MSITE-566 URL: http://jira.codehaus.org/browse/MSITE-566 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site descriptor Affects Versions: 2.2 Reporter: SebbASF The site:attach-descriptor goal processes the site.xml file, and removes all comments, including the licence header. Furthermore, it filters the source, replacing pom.* and project.* properties (any others?) This needs to be clearly documented under the goal and in the page "Configuring the Site Descriptor". Also, comments really ought to be retained. -- 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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
[ http://jira.codehaus.org/browse/MSITE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260239#action_260239 ] Lukas Theussl commented on MSITE-566: - Did you try 2.3-SNAPSHOT? This should be fixed with MSITE-488. > site:attach-descriptor removes all comments and filters the content > --- > > Key: MSITE-566 > URL: http://jira.codehaus.org/browse/MSITE-566 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor >Affects Versions: 2.2 >Reporter: SebbASF > > The site:attach-descriptor goal processes the site.xml file, and removes all > comments, including the licence header. > Furthermore, it filters the source, replacing pom.* and project.* properties > (any others?) > This needs to be clearly documented under the goal and in the page > "Configuring the Site Descriptor". > Also, comments really ought to be retained. -- 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-2315) Add option to exclude all transitive dependencies for a particular one
[ http://jira.codehaus.org/browse/MNG-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260245#action_260245 ] Lo-Tan commented on MNG-2315: - I have come across this and found it would be useful as well. The use case for us was all of our projects build normally (EAR + skinny WARs), but when we get to the final deployment, our resulting EAR file contains only the libraries we create. We put all the third party libraries into a shared Java EE library (running WebLogic server) and thus, in the EAR we have to exclude all the transitives from all of our projects :( It's harsh to have to do it for each and every transitive. > Add option to exclude all transitive dependencies for a particular one > -- > > Key: MNG-2315 > URL: http://jira.codehaus.org/browse/MNG-2315 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.4 >Reporter: Carlos Sanchez >Priority: Critical > Fix For: 3.1 > > > Something like > > ... > true > -- 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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
[ http://jira.codehaus.org/browse/MSITE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260259#action_260259 ] SebbASF commented on MSITE-566: --- Just tried 2.3-SNAPSHOT, but Maven cannot find it. Has it been published, e.g. to the Nexus repo? > site:attach-descriptor removes all comments and filters the content > --- > > Key: MSITE-566 > URL: http://jira.codehaus.org/browse/MSITE-566 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor >Affects Versions: 2.2 >Reporter: SebbASF > > The site:attach-descriptor goal processes the site.xml file, and removes all > comments, including the licence header. > Furthermore, it filters the source, replacing pom.* and project.* properties > (any others?) > This needs to be clearly documented under the goal and in the page > "Configuring the Site Descriptor". > Also, comments really ought to be retained. -- 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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
[
http://jira.codehaus.org/browse/MSITE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260260#action_260260
]
SebbASF commented on MSITE-566:
---
Actually it did download, but I get an error:
{noformat}
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO] Cannot find mojo descriptor for: 'site:attach-descriptor' - Treating as
non-aggregator.
[INFO]
[INFO] Building Commons Parent
[INFO]task-segment: [site:attach-descriptor]
[INFO]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] A required plugin was not found: Plugin could not be found - check that
the goal name is correct: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.plugins
-DartifactId=maven-site-plugin -Dversion=2.3-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins
-DartifactId=maven-site-plugin -Dversion=2.3-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file -Durl=[u
rl] -DrepositoryId=[id]
org.apache.maven.plugins:maven-site-plugin:maven-plugin:2.3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.apache.maven.plugins:maven-site-plugin:maven-plugin:2.3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
{noformat}
There's only a POM - no jar - in my local repo, though I see one in Nexus.
> site:attach-descriptor removes all comments and filters the content
> ---
>
> Key: MSITE-566
> URL: http://jira.codehaus.org/browse/MSITE-566
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.2
>Reporter: SebbASF
>
> The site:attach-descriptor goal processes the site.xml file, and removes all
> comments, including the licence header.
> Furthermore, it filters the source, replacing pom.* and project.* properties
> (any others?)
> This needs to be clearly documented under the goal and in the page
> "Configuring the Site Descriptor".
> Also, comments really ought to be retained.
--
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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
[ http://jira.codehaus.org/browse/MSITE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260292#action_260292 ] Dennis Lundberg commented on MSITE-566: --- See http://maven.apache.org/guides/development/guide-testing-development-plugins.html > site:attach-descriptor removes all comments and filters the content > --- > > Key: MSITE-566 > URL: http://jira.codehaus.org/browse/MSITE-566 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor >Affects Versions: 2.2 >Reporter: SebbASF > > The site:attach-descriptor goal processes the site.xml file, and removes all > comments, including the licence header. > Furthermore, it filters the source, replacing pom.* and project.* properties > (any others?) > This needs to be clearly documented under the goal and in the page > "Configuring the Site Descriptor". > Also, comments really ought to be retained. -- 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: (MSITE-566) site:attach-descriptor removes all comments and filters the content
[
http://jira.codehaus.org/browse/MSITE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260300#action_260300
]
SebbASF commented on MSITE-566:
---
Thanks, I can now use the snapshot.
2.3-SNAPSHOT fixes the replacement of ${project.name}, but the comments all
still disappear, so I think there's still a problem.
> site:attach-descriptor removes all comments and filters the content
> ---
>
> Key: MSITE-566
> URL: http://jira.codehaus.org/browse/MSITE-566
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.2
>Reporter: SebbASF
>
> The site:attach-descriptor goal processes the site.xml file, and removes all
> comments, including the licence header.
> Furthermore, it filters the source, replacing pom.* and project.* properties
> (any others?)
> This needs to be clearly documented under the goal and in the page
> "Configuring the Site Descriptor".
> Also, comments really ought to be retained.
--
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: (SUREFIRE-690) testSetCompleted called before testSetStarting when using m3 parallel builds
[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260310#action_260310 ] Gin-Ting Chen commented on SUREFIRE-690: Actually Kristian this is only running parallel m3 (-T 1C) at the moment. redirectTestOutputToFile may be on but definitely not parallel junit. > testSetCompleted called before testSetStarting when using m3 parallel builds > > > Key: SUREFIRE-690 > URL: http://jira.codehaus.org/browse/SUREFIRE-690 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.1 >Reporter: Gin-Ting Chen >Assignee: Kristian Rosenvold > > This is running m3 with -T 1C (8 core build machine). > [17:52:38]: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on > project hornet-stinger: Error while executing forked tests.; nested exception > is java.lang.IllegalStateException: testSetCompleted called before > testSetStarting -> [Help 1] > Seems like it doesn't happen as frequently as previously -- 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
