[jira] Commented: (CONTINUUM-734) Can't use continuum behind https proxy
[
http://jira.codehaus.org/browse/CONTINUUM-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89626
]
Damon Rand commented on CONTINUUM-734:
--
Though I use continuum at home this is the primary issue stopping us from using
it where I work.. Sorry I haven't tried the latest builds either though..
> Can't use continuum behind https proxy
> --
>
> Key: CONTINUUM-734
> URL: http://jira.codehaus.org/browse/CONTINUUM-734
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Richard van der Hoff
> Assigned To: Emmanuel Venisse
> Fix For: 1.1-alpha-1
>
> Attachments: mod_proxy_http.so
>
>
> As noted in CONTINUUM-240, it's not currentlyy possible to run the continuum
> webapp behind an https proxy, as all the links are http://...
> My apache setup is something along the lines of:
> {code:xml}
>
> SSLEngine on
> ProxyPass / http://localhost:8080/
> ProxyPassReverse / http://localhost:8080/
> ProxyPreserveHost On
>
> {code}
> and my jetty config:
> {code:xml}
>
>
> 8080
>
>
> {code}
> The links are correct, except that they have s/https/http/.
> Why does the webapp need to use absolute links anyway?
--
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: (MPMD-51) Sometimes PMD.xml doesn't contain the class name and this displays null in the verbose mode
[ http://jira.codehaus.org/browse/MPMD-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MPMD-51: Assignee: Daniel Kulp (was: Brian Fox) Fix Version/s: 2.2 > Sometimes PMD.xml doesn't contain the class name and this displays null in > the verbose mode > --- > > Key: MPMD-51 > URL: http://jira.codehaus.org/browse/MPMD-51 > Project: Maven 2.x Pmd Plugin > Issue Type: Bug >Reporter: Brian Fox > Assigned To: Daniel Kulp > Fix For: 2.2 > > > Example pmd.xml: > > > name="G:\checkout\dsms-3.0\application\client-management-application\src\main\java\com\stchome\dsms\appl\formdatasources\clientmanagement\ClientRegistryDataHelper.java"> > package="com.stchome.dsms.appl.formdatasources.clientmanagement" > externalInfoUrl="http://pmd.sourceforge.net/rules/imports.html#UnusedImports"; > priority="4"> > Avoid unused imports such as > 'com.stchome.dsms.appl.formdatasources.clientmanagement.util.AppResource' > > > > In this case, we should just print the file name if either the package or > class name is null -- 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] Closed: (MPMD-40) deploy the pmd.xml with site:deploy
[ http://jira.codehaus.org/browse/MPMD-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MPMD-40. --- Resolution: Fixed It now writes the file to both locations. Thus, it should deploy to the site, but also not break anything. > deploy the pmd.xml with site:deploy > --- > > Key: MPMD-40 > URL: http://jira.codehaus.org/browse/MPMD-40 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Stephan Heilner > Assigned To: Daniel Kulp >Priority: Minor > Fix For: 2.2 > > Attachments: maven-pmd-plugin.patch, maven-pmd-plugin.patch > > > It would be extremely useful if the pmx.xml file is deployed along with the > pmd.html file when you run a mvn site or mvn site:deploy. I'm trying to > write a internal report based on the results from my continuous build system > (cruisecontrol). Instead of screen-scraping that html, if that xml version > was deployed too, I could digest that create my report. -- 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] Closed: (MPMD-47) pmd should support multiple source roots
[ http://jira.codehaus.org/browse/MPMD-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MPMD-47. --- Resolution: Fixed It now will use project.compileSourceRoots and project.testCompileSourceRoots (if includeTests is true) to find all the source directories. > pmd should support multiple source roots > > > Key: MPMD-47 > URL: http://jira.codehaus.org/browse/MPMD-47 > Project: Maven 2.x Pmd Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Brian Fox > Assigned To: Daniel Kulp > Fix For: 2.2 > > > pmd and cpd don't read the source roots to find other locations for source to > check. -- 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] Closed: (MPMD-51) Sometimes PMD.xml doesn't contain the class name and this displays null in the verbose mode
[ http://jira.codehaus.org/browse/MPMD-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MPMD-51. --- Resolution: Fixed > Sometimes PMD.xml doesn't contain the class name and this displays null in > the verbose mode > --- > > Key: MPMD-51 > URL: http://jira.codehaus.org/browse/MPMD-51 > Project: Maven 2.x Pmd Plugin > Issue Type: Bug >Reporter: Brian Fox > Assigned To: Daniel Kulp > Fix For: 2.2 > > > Example pmd.xml: > > > name="G:\checkout\dsms-3.0\application\client-management-application\src\main\java\com\stchome\dsms\appl\formdatasources\clientmanagement\ClientRegistryDataHelper.java"> > package="com.stchome.dsms.appl.formdatasources.clientmanagement" > externalInfoUrl="http://pmd.sourceforge.net/rules/imports.html#UnusedImports"; > priority="4"> > Avoid unused imports such as > 'com.stchome.dsms.appl.formdatasources.clientmanagement.util.AppResource' > > > > In this case, we should just print the file name if either the package or > class name is null -- 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] Closed: (MPMD-30) No way to PMD test the test sources in src/test/java
[
http://jira.codehaus.org/browse/MPMD-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp closed MPMD-30.
---
Resolution: Fixed
I added an includeTests config item to have it include all the testSourceRoots
when searching for files.
> No way to PMD test the test sources in src/test/java
>
>
> Key: MPMD-30
> URL: http://jira.codehaus.org/browse/MPMD-30
> Project: Maven 2.x Pmd Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Daniel Kulp
> Assigned To: Daniel Kulp
> Fix For: 2.2
>
>
> There currently isn't ANY way to have PMD check the test sources in
> src/test/java.
> For the checkstyle plugin, you can do something like:
> ${basedir}/src
> which would allow it to check ALL the java files in src including the ones in
> src/test/java. For PMD, however, the sourceDirectory field is readonly so
> is not settable in the pom.xml.
> Log of discussion on IRC:
> [16:28:29] pmd: // TODO: use source roots instead
> [16:28:29] String sourceDirectory =
> project.getBuild().getSourceDirectory();
> [16:28:30] :)
> [16:28:43] ugh
> [16:28:49] it's not even using an expression??
> [16:28:59] nope
> [16:29:08] should be ${project.compileSourceRoots}, and not
> @readonly
> [16:29:24] dkulp: only thing I can say is to fix the plugin and
> deploy a snapshot...
> [16:29:39] Or not pmd the tests for now.
> [16:30:52] btw, you don't want to always run source-checking stuff
> on all sources
> [16:31:07] generated sources usually don't follow coding style for
> instance
> [16:31:30] Right. That's why i want "${basedir}/src" and not
> "target/"
> [16:31:32] so using compileSourceRoot is tricky..
> [16:31:49] well you can do that for checkstyle and specify
> includes/excludes
> [16:31:58] fair enough
> [16:32:04] Right. checkstyle works OK.
> [16:32:09] but overriding that list should be enough, I would think
> [16:32:26] we should actually be able to mark sourceRoots as being
> generated or not
--
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: (MRM-212) configure checksum policy for proxied repository
[ http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89640 ] Wendy Smoak commented on MRM-212: - Archiva definitely needs this feature. Right now, it will not proxy the latest release of maven-gpg-plugin due to a bad checksum. We need to fix the bad checksums in central and make it stop happening-- is it the deploy plugin causing the problem? [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-gpg-plugin Version: 1.0-alpha-3 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-gpg-plugin:pom:1.0-alpha-3 from the specified remote repositories: central (http://localhost:8080/archiva/repository/releases), ... >From the log file: INFO | jvm 1| 2007/03/10 10:23:52 | 2007-03-10 10:23:52,526 [SocketListener0-2] WARN ProxyRequestHandler- The checksum 'e4525958537d3b438ede7acb73bd10ba' did not match the remote value: D41D8CD98F00B204E9800998ECF8427E INFO | jvm 1| 2007/03/10 10:23:52 | 2007-03-10 10:23:52,526 [SocketListener0-2] WARN ProxyRequestHandler- Skipping repository Central Repository: Checksum failures occurred while downloading org/apache/maven/plugins/maven-gpg-plugin/1.0-alpha-3/maven-gpg-plugin-1.0-alpha-3.pom > configure checksum policy for proxied repository > > > Key: MRM-212 > URL: http://jira.codehaus.org/browse/MRM-212 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Reporter: nicolas de loof >Priority: Critical > Fix For: 1.0 > > Attachments: 2006-10-26-checksum-policy.patch, MRM-212.patch > > > Some artifact on repo1.maven.org have bad checksum. This need fix, but this > also make archiva not usable as a replacement for maven-proxy. > As maven itself allow to configure a checksum policy, a new configuration > parameter on proxied repo would be nice. -- 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: (MPMD-53) pmd mojos need a skip flag similar to surefire
pmd mojos need a skip flag similar to surefire -- Key: MPMD-53 URL: http://jira.codehaus.org/browse/MPMD-53 Project: Maven 2.x Pmd Plugin Issue Type: Improvement Components: CPD, PMD Affects Versions: 2.1 Reporter: Brian Fox there needs to be an easy way to disable the tests, putting the whole plugin inside profiles isn't always feasible in very large projects. We want them on by default but occasionally need to disable them. Because some of the tests add a significant amount of time to the overall build, simply making them not fail isn't good enough...we just need it to do nothing. -- 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: (MCHECKSTYLE-71) need a skip flag similar to surefire
need a skip flag similar to surefire Key: MCHECKSTYLE-71 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-71 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Brian Fox there needs to be an easy way to disable the tests, putting the whole plugin inside profiles isn't always feasible in very large projects. We want them on by default but occasionally need to disable them. Because some of the tests add a significant amount of time to the overall build, simply making them not fail isn't good enough...we just need it to do nothing. -- 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: (MEV-455) bad checksums on repo1.maven.org
[ http://jira.codehaus.org/browse/MEV-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89641 ] Wendy Smoak commented on MEV-455: - The pom for the latest release of maven-gpg-plugin has a bad checksum, which I noticed when Archiva refused to proxy it (MRM-212). http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-gpg-plugin/1.0-alpha-3/ INFO | jvm 1| 2007/03/10 11:04:14 | 2007-03-10 11:04:14,790 [SocketListener0-2] WARN ProxyRequestHandler- The checksum 'e4525958537d3b438ede7acb73bd10ba' did not match the remote value: D41D8CD98F00B204E9800998ECF8427E INFO | jvm 1| 2007/03/10 11:04:14 | 2007-03-10 11:04:14,790 [SocketListener0-2] WARN ProxyRequestHandler- Skipping repository Central Repository: Checksum failures occurred while downloading org/apache/maven/plugins/maven-gpg-plugin/1.0-alpha-3/maven-gpg-plugin-1.0-alpha-3.pom > bad checksums on repo1.maven.org > > > Key: MEV-455 > URL: http://jira.codehaus.org/browse/MEV-455 > Project: Maven Evangelism > Issue Type: Bug >Reporter: nicolas de loof > > I'm using Archiva as a maven proxy, that verify checksums when downloading > artifact. My archiva.log shwo some invalid checksum on http://repo1.maven.org > : > commons-chain/commons-chain/1.1/commons-chain-1.1.pom > org/codehaus/plexus/plexus-compiler/1.5.2/plexus-compiler-1.5.2.pom > commons-validator/commons-validator/1.3.0/commons-validator-1.3.0-sources.jar > struts/struts/1.2.9/struts-1.2.9-sources.jar > junit/junit/3.8.2/junit-3.8.2.pom > junit/junit/3.8.2/junit-3.8.2.jar > junit/junit/3.8.2/junit-3.8.2-sources.jar > junit/junit/3.8.2/junit-3.8.2-javadoc.jar > easymock/easymock/1.2_Java1.3/easymock-1.2_Java1.3-sources.jar > org/codehaus/plexus/plexus-compilers/1.5.2/plexus-compilers-1.5.2.pom > org/apache/maven/surefire/surefire-providers/2.0/surefire-providers-2.0.pom > org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml > it/could/webdav/0.4/webdav-0.4.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.jar > it/could/webdav/0.4/webdav-0.4.pom > it/could/webdav/0.4/webdav-0.4.jar -- 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: (MNG-2867) Guide building maven not up to date
Guide building maven not up to date --- Key: MNG-2867 URL: http://jira.codehaus.org/browse/MNG-2867 Project: Maven 2 Issue Type: Bug Components: Documentation: Guides Affects Versions: 2.0.5 Environment: N/A Reporter: Thomas LECAVELIER Priority: Trivial Hello, Since the release of maven 2.0.5, the guide to building m2 is not up to date. When a user want to build maven from svn, he has to define a variable for version 2.0.6 (the current trunk), not for 2.0.5. -- 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: (MNG-2867) Guide building maven not up to date
[ http://jira.codehaus.org/browse/MNG-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas LECAVELIER updated MNG-2867: --- Attachment: MNG-2867-site.patch A correction proposal. Replace from 2.0.5 to 2.0.6. > Guide building maven not up to date > --- > > Key: MNG-2867 > URL: http://jira.codehaus.org/browse/MNG-2867 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: 2.0.5 > Environment: N/A >Reporter: Thomas LECAVELIER >Priority: Trivial > Attachments: MNG-2867-site.patch > > > Hello, > Since the release of maven 2.0.5, the guide to building m2 is not up to date. > When a user want to build maven from svn, he has to define a variable for > version 2.0.6 (the current trunk), not for 2.0.5. -- 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: (MPMD-53) pmd mojos need a skip flag similar to surefire
[ http://jira.codehaus.org/browse/MPMD-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MPMD-53: Fix Version/s: 2.2 > pmd mojos need a skip flag similar to surefire > -- > > Key: MPMD-53 > URL: http://jira.codehaus.org/browse/MPMD-53 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement > Components: CPD, PMD >Affects Versions: 2.1 >Reporter: Brian Fox > Assigned To: Daniel Kulp > Fix For: 2.2 > > > there needs to be an easy way to disable the tests, putting the whole plugin > inside profiles isn't always feasible in very large projects. We want them on > by default but occasionally need to disable them. Because some of the tests > add a significant amount of time to the overall build, simply making them not > fail isn't good enough...we just need it to do nothing. -- 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: (MGPG-3) [PATCH] Please add a --no-tty option to the gpg command line when running non interactively
[PATCH] Please add a --no-tty option to the gpg command line when running non interactively --- Key: MGPG-3 URL: http://jira.codehaus.org/browse/MGPG-3 Project: Maven 2.x GPG Plugin Issue Type: Wish Reporter: Christian Schulte Priority: Blocker Attachments: no-tty.patch The plugin fails to work with Mevenide Netbeans or Continuum cause it cannot write to /dev/tty. The --no-tty command line argument, when given to gpg, makes the plugin work in such environments. The attached patch adds that option to the gpg command line when not running interactively. -- 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-2812) Profile with an undefined os family activation should not activate
[ http://jira.codehaus.org/browse/MNG-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89668 ] Jason van Zyl commented on MNG-2812: I've updated 2.0.x to use plexus-utils 1.4.1 which gets rid of this problem. > Profile with an undefined os family activation should not activate > -- > > Key: MNG-2812 > URL: http://jira.codehaus.org/browse/MNG-2812 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.4, 2.1.x >Reporter: Franz Allan Valencia See > Assigned To: Jason van Zyl > Fix For: 2.0.6, 2.1.x > > > The following profile gets activated eventhough the os family is not the > current os family ... bogus-profile > bogus-family... -- 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: (MNG-2812) Profile with an undefined os family activation should not activate
[
http://jira.codehaus.org/browse/MNG-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2812:
---
Assignee: Jason van Zyl
Description: The following profile gets activated eventhough the os family
is not the current os family ... bogus-profile
bogus-family... (was:
The following profile gets activated eventhough the os family is not the
current os family
{code:xml}
...
bogus-profile
bogus-family
...
{code})
Complexity: (was: Intermediate)
> Profile with an undefined os family activation should not activate
> --
>
> Key: MNG-2812
> URL: http://jira.codehaus.org/browse/MNG-2812
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.4, 2.1.x
>Reporter: Franz Allan Valencia See
> Assigned To: Jason van Zyl
> Fix For: 2.0.6, 2.1.x
>
>
> The following profile gets activated eventhough the os family is not the
> current os family ... bogus-profile
> bogus-family...
--
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] Closed: (MNG-2812) Profile with an undefined os family activation should not activate
[ http://jira.codehaus.org/browse/MNG-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2812. -- Resolution: Fixed > Profile with an undefined os family activation should not activate > -- > > Key: MNG-2812 > URL: http://jira.codehaus.org/browse/MNG-2812 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.4, 2.1.x >Reporter: Franz Allan Valencia See > Assigned To: Jason van Zyl > Fix For: 2.0.6, 2.1.x > > > The following profile gets activated eventhough the os family is not the > current os family ... bogus-profile > bogus-family... -- 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] Closed: (MNG-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1577. -- Resolution: Fixed > dependencyManagement does not work for transitive dependencies > -- > > Key: MNG-1577 > URL: http://jira.codehaus.org/browse/MNG-1577 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0 >Reporter: Joerg Schaible > Assigned To: Jason van Zyl > Fix For: 2.0.6 > > Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch, > mng1577c.patch, mng1577d.patch, mng1577e-trunk.patch, mng1577e.patch, > mng1577f.patch, mng1577trunk.patch > > > The dependencyManagement does not work for transient dependencies. The > specified version is ignored. > Use case: > Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT > and B-SNAPSHOT > Project A is child of Main and depends directly on commons-beanutils (version > inherited from Main) > Project B is child of Main and depends directly on commons-digester (version > inherited from Main) > Project C is child of Main and depends directly on A & B (versions inherited > from Main) > A is compiled and tests are run using commons-beanutils-1.7.0 > B is compiled and tests are run using commons-digester-1.6 and > commons-beanutils-1.6, since digester is dependend on this > C is compiled and tests are run using commons-beanutils-1.7.0 > Integration tests of B did not verify, that B is behaving as expected in this > scenario. B might fail with 1.7.0 and it is not even recognized. > If I add beanutils also as direct dependency to B, it works fine, but then > are transitive dependency useless. It should be possible to define at least > in the dependencyManagement, that the versions of transient dependencies also > defined in the dependencyManagement have priority. > - Jörg -- 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: (MNG-2868) Replicate MNG-1577 on trunk
Replicate MNG-1577 on trunk --- Key: MNG-2868 URL: http://jira.codehaus.org/browse/MNG-2868 Project: Maven 2 Issue Type: Task Components: Artifacts and Repositories Affects Versions: 2.1.x Reporter: Jason van Zyl Fix For: 2.1-alpha-1 I need to get patrick to rework the patch for MNG-1577 for trunk or take a swing at it myself. -- 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: (MNG-2868) Replicate MNG-1577 on trunk
[ http://jira.codehaus.org/browse/MNG-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2868: --- Fix Version/s: 2.1-alpha-1 > Replicate MNG-1577 on trunk > --- > > Key: MNG-2868 > URL: http://jira.codehaus.org/browse/MNG-2868 > Project: Maven 2 > Issue Type: Task > Components: Artifacts and Repositories >Affects Versions: 2.1.x >Reporter: Jason van Zyl > Fix For: 2.1-alpha-1 > > > I need to get patrick to rework the patch for MNG-1577 for trunk or take a > swing at it myself. -- 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] Closed: (MNG-2793) Snapshot plugins cannot be resolved correctly with java6
[ http://jira.codehaus.org/browse/MNG-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2793. -- Resolution: Fixed > Snapshot plugins cannot be resolved correctly with java6 > > > Key: MNG-2793 > URL: http://jira.codehaus.org/browse/MNG-2793 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 2.0.4, 2.0.5 >Reporter: Daniel Kulp > Assigned To: Jason van Zyl >Priority: Critical > Fix For: 2.0.6 > > Attachments: maven-artifact-manager.patch > > > With java 6, builds that use snapshot repositories are consistently failing > if the snapshots are not available in the local repository. The error is > something like: > [INFO] > > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for > project: null:maven-site-plugin:maven-plugin:2.0-beta-5 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: > org.apache.maven.plugins:maven-plugins:pom:1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: > org.apache.maven:maven-parent:pom:1 from the repository. > [DEBUG] maven-install-plugin: using locally installed snapshot > [DEBUG] maven-install-plugin: resolved to version 2.2-SNAPSHOT from > repository central > [DEBUG] Skipping disabled repository central > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.maven.plugins:maven-install-plugin > Reason: Error getting POM for 'org.apache.maven.plugins:maven-install-plugin' > from the repository: Failed to resolve artifact, possibly due to a repository > list that is not appropriately equipped for this artifact's metadata. > org.apache.maven.plugins:maven-install-plugin:pom:2.2-SNAPSHOT > from the specified remote repositories: > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > central (http://repo1.maven.org/maven2) > If the artifacts are first downloaded by building with JDK 1.5, everything > works fine. > After investigating, the problem is in the transforms that the > maven-artifact-manager. With JDK 1.5, the order they run is: > org.apache.maven.artifact.transform.LatestArtifactTransformation > org.apache.maven.artifact.transform.ReleaseArtifactTransformation > org.apache.maven.artifact.transform.SnapshotTransformation > but with Java 6, for some reason, the order is: > org.apache.maven.artifact.transform.SnapshotTransformation > org.apache.maven.artifact.transform.LatestArtifactTransformation > org.apache.maven.artifact.transform.ReleaseArtifactTransformation > The LatestArtifactTransform is what uses to the metadata to determine > the "actual" version number (for the install plugin, 2.2-SNAPSHOT). The > SnapshotTransform then converts that to 2.2-20061118.060401-2 which is what > is then downloaded. However, in the java 6 case, the SnapshotTransform is > run first and since the version is not a "SNAPSHOT" version number, it > doesn't do any processing so then the downloading ends up looking for > 2.2-SNAPSHOT, not the full version, which then fails. > I chatted with brett_ on IRC about this: > [09:46:35] OK. I'm trying to track down why my builds are failing > with JDK 1.6 > [09:46:53] The issue is the transforms are in a different order with > 1.6 than 1.5 > [09:47:17] yikes > [09:47:42] With 1.5, its Latest/Release/Snapshot. > [09:47:46] not sure why that would matter. But I guess sorting the > transforms consistently would help. > [09:47:50] With 1.6, it's Snapshot/Latest/Release > [09:48:06] ok, fairly simple to fix in Maven. > [09:48:10] The Latest needs to be before Snapshot. > [09:49:08] I tried changing the order of things in the > components.xml. Didn't seem to change anything. But this is plexus stuff > which I don't know anything about. > [09:49:22] hmm, it should be populated as a list > [09:49:28] but maybe the list is backed by a map > [09:49:35] Yep. Verified it's and ArrayList > [09:49:51] s/backed/populated by/ > [09:50:48] That would definitely do it. > [09:51:21] Any hints on where to look? > [09:51:48] oh, I would go into plexus > [09:51:52] (or how to debug)? > [09:51:58] sorry, wouldn't > [09:52:13] it's changing too much > [09:52:18] 2.0.5 will be stuck with alpha-10 > [09:52:24] so, need to work around it in Maven > [09:53:00] perhaps just hack the order in the code, and then fix > plexus to honour the order in components.xml in trunk > [0
[jira] Closed: (MNG-2843) Plugins can't get project properties
[
http://jira.codehaus.org/browse/MNG-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-2843.
--
Resolution: Fixed
Patched plexus-container created and deploy and used in the 2.0.6 version of
maven.
> Plugins can't get project properties
>
>
> Key: MNG-2843
> URL: http://jira.codehaus.org/browse/MNG-2843
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.5
>Reporter: David Jackman
> Assigned To: Jason van Zyl
> Fix For: 2.0.6
>
>
> For a plugin to get the project's properties, it should define a field as
> follows:
> /**
> * The whole project.
> * @parameter expression="${project.properties}"
> * @required
> * @readonly
> */
> private java.util.Properties properties;
> However, because of a bug in Plexus (see PLX-327), these properties are
> always empty. This Plexus bug needs to be fixed and Maven should include the
> fixed plexus-container-default library.
--
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: (MPMD-44) Allow to specify the rulesets as described in the docs
[ http://jira.codehaus.org/browse/MPMD-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MPMD-44: Assignee: Daniel Kulp Fix Version/s: 2.2 Component/s: PMD > Allow to specify the rulesets as described in the docs > -- > > Key: MPMD-44 > URL: http://jira.codehaus.org/browse/MPMD-44 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement > Components: PMD >Reporter: Aaron Digulla > Assigned To: Daniel Kulp > Fix For: 2.2 > > > Adding rulesets doesn't work as described in the docs. Looking at the source, > there is no place where the "rulesets" list is used or defined. -- 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: (MPMD-28) Support for multi-projects poms
[ http://jira.codehaus.org/browse/MPMD-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MPMD-28: Assignee: Daniel Kulp Fix Version/s: 2.2 Component/s: PMD CPD > Support for multi-projects poms > --- > > Key: MPMD-28 > URL: http://jira.codehaus.org/browse/MPMD-28 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Torsten Curdt > Assigned To: Daniel Kulp > Fix For: 2.2 > > Attachments: maven-pmd-plugin-20061020-1242.patch, > maven-pmd-plugin-20061020-1445.patch, multiproject.diff > > > Added support for multi-projects so if you set "aggregate" to "true" the > parent project will generate the report and the childs will not execute it > anymore -- 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: (MPMD-52) XRef lnks do not work with aggregated XRef
[
http://jira.codehaus.org/browse/MPMD-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated MPMD-52:
Assignee: Daniel Kulp
Fix Version/s: 2.2
> XRef lnks do not work with aggregated XRef
> --
>
> Key: MPMD-52
> URL: http://jira.codehaus.org/browse/MPMD-52
> Project: Maven 2.x Pmd Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Maarten Winkels
> Assigned To: Daniel Kulp
> Fix For: 2.2
>
> Attachments: maven-pmd-plugin.patch
>
>
> When using JXR with the aggregate property set, the XRef links generated by
> this plugin fail.
> The obvious solution would be to use:
>
>
> ${project.reporting.outputDirectory}/../xref
>
> But this fails. When the relative path is calculated, the PathTool used fails
> to recognize the paths as being relative to each other (on Windows, due to
> the forward, backword slashes).
--
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
