[jira] Commented: (MNG-3639) Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9
[ http://jira.codehaus.org/browse/MNG-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141572#action_141572 ] Dennis Lundberg commented on MNG-3639: -- For the record, running the commons-plugin failed for me on Windows using Maven 2.0.8. I got the same error message then, that Niall got when he ran with Maven 2.0.9. This was *before* I added the exclusions, but *after* I upgraded to Ant 1.7.1. > Ant 1.7.0 Task not found after upgrading from Maven 2.0.8 to 2.0.9 > -- > > Key: MNG-3639 > URL: http://jira.codehaus.org/browse/MNG-3639 > Project: Maven 2 > Issue Type: Bug > Components: Ant tasks >Affects Versions: 2.0.8 >Reporter: Niall Pemberton >Assignee: John Casey > Fix For: 2.0.10 > > Attachments: mvn-2.0.8-output.txt, mvn-2.0.9-output.txt, pom.xml > > > Apache Commons has a maven ant plugin (called commons-build-plugin[1]) which > has a dependency on Ant 1.7.0 and uses the loadresource task (which was added > to Ant in version 1.7.0). The plugin works fine for maven 2.0.8, but after > upgrading to 2.0.9 fails with the message "Could not create task or type of > type: loadresource." (see attached output). > This has been raised on the maven dev list in the following thread: > http://markmail.org/message/tv37c37fjyzx6l6k > I am attaching a simple pom.xml that reproduces this problem with the > following command: > mvn commons:jira-page > (N.B. create either a "xdocs" or "src/xdoc" directory in the project) > [1] > http://svn.apache.org/viewvc/commons/proper/commons-build-plugin/tags/commons-build-plugin-1.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: (MENFORCER-17) add a new rule to enforce that no repositories are defined in the poms.
[ http://jira.codehaus.org/browse/MENFORCER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MENFORCER-17: --- Fix Version/s: 1.0 > add a new rule to enforce that no repositories are defined in the poms. > --- > > Key: MENFORCER-17 > URL: http://jira.codehaus.org/browse/MENFORCER-17 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 1.0 > > > repositories in the poms are against best practices -- 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: (MENFORCER-24) create a rule to check that certain profiles are activated.
[ http://jira.codehaus.org/browse/MENFORCER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MENFORCER-24: --- Fix Version/s: 1.0 > create a rule to check that certain profiles are activated. > --- > > Key: MENFORCER-24 > URL: http://jira.codehaus.org/browse/MENFORCER-24 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 1.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: (MENFORCER-46) include feature of sizewatch-plugin into enforcer plugin
[ http://jira.codehaus.org/browse/MENFORCER-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MENFORCER-46: --- Fix Version/s: 1.0 > include feature of sizewatch-plugin into enforcer plugin > > > Key: MENFORCER-46 > URL: http://jira.codehaus.org/browse/MENFORCER-46 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement >Reporter: Roman Stumm >Assignee: Brian Fox > Fix For: 1.0 > > Attachments: verifysize.zip > > > As discussed in the last days, here is the project and source of the > verifysize plugin that allows to check an artifact for max./min. size. > Use it / include it into the enforcer plugin. > For more information, refer to : > http://code.google.com/p/agimatec-maven-plugins/ > Roman -- 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: (MPIR-124) License report is empty in offline
License report is empty in offline -- Key: MPIR-124 URL: http://jira.codehaus.org/browse/MPIR-124 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: license Affects Versions: 2.1 Reporter: Vincent Siveton But we got an info log. -- 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: (MPIR-124) License report is empty in offline
[ http://jira.codehaus.org/browse/MPIR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-124. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r676142 > License report is empty in offline > -- > > Key: MPIR-124 > URL: http://jira.codehaus.org/browse/MPIR-124 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: license >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > But we got an info log. -- 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: (MPIR-121) dependency.locations.enabled should set to true by default
[
http://jira.codehaus.org/browse/MPIR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-121.
Assignee: Vincent Siveton
Resolution: Fixed
fixed in r676151, snapshot deployed
> dependency.locations.enabled should set to true by default
> --
>
> Key: MPIR-121
> URL: http://jira.codehaus.org/browse/MPIR-121
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Task
> Components: dependencies
>Affects Versions: 2.1
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 2.1
>
>
> According the javadoc
> {noformat}
> /**
> * Display the repository locations of the dependencies. Requires Maven
> 2.0.5+.
> *
> * @since 2.1
> * @parameter expression="${dependency.locations.enabled}"
> default-value="false"
> */
> private boolean dependencyLocationsEnabled;
> {noformat}
> Since POM has a prerequisites to 2.0.6, dependencyLocationsEnabled should be
> set to true by default
--
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: (MCHECKSTYLE-98) Maven Checkstyle is too strict and not follow Maven's team conventions!
[ http://jira.codehaus.org/browse/MCHECKSTYLE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141578#action_141578 ] Dennis Lundberg commented on MCHECKSTYLE-98: Adding scope=protected to the Javadoc* modules is a good idea. However I don't think we should add the allow* options. That lowers the bar for documentation too much. If we set the allow* options, we are saying that it's OK to *not* document parameters and return values for public and protected methods. I don't support that. The configuration addition to the VisibilityModifier module is OK by me. > Maven Checkstyle is too strict and not follow Maven's team conventions! > --- > > Key: MCHECKSTYLE-98 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-98 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Vincent Siveton > Attachments: maven_style_improvements.diff, > site-MPIR-improvements.zip, site-MPIR-r675999.zip > > > The Checkstyle report is an official part of the Maven's project website. > Release manager needs to review it before cutting a release. > Actually, the Maven Checkstyle conf is too strict and not following our > conventions. > Lets take the MPIR project (rev 675999) and see site-MPIR-r675999.zip > attachment. There is a lot of unuseful info/warn ie "Missing a Javadoc > comment" or "Expected @param tag for..." > I propose to modify the current Maven style (see > maven_style_improvements.diff). You could see results in > site-MPIR-improvements.zip -- 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: (MAVENUPLOAD-2147) iText 2.1.3 released
iText 2.1.3 released Key: MAVENUPLOAD-2147 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2147 Project: Maven Upload Requests Issue Type: Task Reporter: Bruno Lowagie Hello, I have just released iText 2.1.2. You can download different bundles from this URL: http://itext.ugent.be/library/maven/ This is the core bundle: http://itext.ugent.be/library/maven/itext-2.1.3-bundle.jar There are also 3 bundles for subprojects: RUPS, Toolbox and RTF. best regards, Bruno -- 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-3663) IT 0088 failing for Maven 2.1-SNAPSHOT on Windows
IT 0088 failing for Maven 2.1-SNAPSHOT on Windows
-
Key: MNG-3663
URL: http://jira.codehaus.org/browse/MNG-3663
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.1-alpha-1
Environment: Windows, Maven 2.1-SNAPSHOT
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: org.apache.maven.it0088.PomInterpolationTest.txt,
test.properties
Running the [Hudson
bundle|http://www.nabble.com/Re%3A-Community-Help-with-Maven-ITs-p18415443.html]
on Windows delivers:
{noformat}
Tests in error:
testitMNG3380(org.apache.maven.integrationtests.MavenITmng3380ManagedRelocatedTransdepsTest)
testit0088(org.apache.maven.integrationtests.MavenIT0088Test)
Tests run: 166, Failures: 0, Errors: 2, Skipped: 0
{noformat}
As the attached test results show, the interpolation of
{{${project.build.directory}}} does not return a path with normalized file
separators.
--
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-3663) IT 0088 failing for Maven 2.1-SNAPSHOT on Windows
[
http://jira.codehaus.org/browse/MNG-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3663:
---
Component/s: (was: Inheritance and Interpolation)
IT Failures
> IT 0088 failing for Maven 2.1-SNAPSHOT on Windows
> -
>
> Key: MNG-3663
> URL: http://jira.codehaus.org/browse/MNG-3663
> Project: Maven 2
> Issue Type: Bug
> Components: IT Failures
>Affects Versions: 2.1-alpha-1
> Environment: Windows, Maven 2.1-SNAPSHOT
>Reporter: Benjamin Bentmann
>Priority: Minor
> Attachments: org.apache.maven.it0088.PomInterpolationTest.txt,
> test.properties
>
>
> Running the [Hudson
> bundle|http://www.nabble.com/Re%3A-Community-Help-with-Maven-ITs-p18415443.html]
> on Windows delivers:
> {noformat}
> Tests in error:
>
> testitMNG3380(org.apache.maven.integrationtests.MavenITmng3380ManagedRelocatedTransdepsTest)
> testit0088(org.apache.maven.integrationtests.MavenIT0088Test)
> Tests run: 166, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
> As the attached test results show, the interpolation of
> {{${project.build.directory}}} does not return a path with normalized file
> separators.
--
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-3664) Various unit tests from maven-core fail when run from a directory with space in its path
Various unit tests from maven-core fail when run from a directory with space in
its path
Key: MNG-3664
URL: http://jira.codehaus.org/browse/MNG-3664
Project: Maven 2
Issue Type: Bug
Components: IT Failures
Affects Versions: 2.1-alpha-1
Environment: WinXP & Xubuntu, Sun JDK 1.6.0
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: file-urls.patch,
org.apache.maven.project.MavenProjectDynamismTest.txt
OK, not an IT failure but I guess unit test failures count, too ;-)
When running the Hudson package from a base directory with a space, say "M:\hud
son", the bootstrap job fails with
{noformat}
Tests in error:
testBuildFromRepository_StoreProjectByCoordOnlyIfUncached(org.apache.maven.project.workspace.ProjectCachingTest)
testBuildFromRepository_DontCheckCacheForRELEASEMetaVersion(org.apache.maven.project.workspace.ProjectCachingTest)
testBuildFromRepository_DontCheckCacheForLATESTMetaVersion(org.apache.maven.project.workspace.ProjectCachingTest)
testBuildFromFile_StoreByCoordAndFileIfUncached(org.apache.maven.project.workspace.ProjectCachingTest)
testBuildSectionGroupIdInterpolation(org.apache.maven.project.MavenProjectDynamismTest)
testRoundTrip(org.apache.maven.project.MavenProjectDynamismTest)
testShouldPreserveAddedResourceInRestoredState(org.apache.maven.project.MavenProjectDynamismTest)
testShouldPreserveAddedFilterInRestoredState(org.apache.maven.project.MavenProjectDynamismTest)
testShouldIncorporateChangedBuildDirectoryViaExpressionsOnNextConcreteCalculation(org.apache.maven.project.MavenProjectDynamismTest)
testShouldPreserveInitialValuesForPropertiesReferencingBuildPaths(org.apache.maven.project.MavenProjectDynamismTest)
testShouldAlignCompileSourceRootsInConcreteState(org.apache.maven.project.MavenProjectDynamismTest)
{noformat}
due to test code suffering from [Common Bug
#6|http://www.nabble.com/Re%3A-Common-Bugs-p16522914.html], see attached
Surefire report.
Applying the attached patch only makes the show go on until maven-core which
then fails with
{noformat}
Tests in error:
test_addExtension_usingModel_ShouldLoadExtensionComponent(org.apache.maven.extension.DefaultExtensionManagerTest)
test_addExtension_usingModel_ShouldLoadCustomLifecycleMappingAndArtifactHandler(org.apache.maven.extension.DefaultExtensionManagerTest)
{noformat}
The console output of these tests is
{noformat}
[WARNING]
DEPRECATION: The POM for the artifact
'org.apache.maven.core.test:test-extension:jar' was invalid or not found on any
repositories.
This may not be supported by future versions of Maven and should be
corrected as soon as possible.
Error given: POM 'org.apache.maven.core.test:test-extension' not found
in repository: Unable to download the artifact from any repository
org.apache.maven.core.test:test-extension:pom:1
from the specified remote repositories:
central
(file:/M:/hud%20son/runtime/jobs/maven-2.1.x-bootstrap/workspace/trunk/maven-core/target/test-classes/org/apache/maven/extension/test-extension-repo/)
for project org.apache.maven.core.test:test-extension
{noformat}
and suggests that something (maven-artifact?) is not properly decoding the file
URL of central back to "M:\hud son\..."
--
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
