[jira] Commented: (SCM-569) CVS checkout giving error
[ http://jira.codehaus.org/browse/SCM-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232777#action_232777 ] Rémy Sanlaville commented on SCM-569: - It seems that your problem is related to [maven-scm-plugin plugin|http://maven.apache.org/scm/plugins/index.html] and not to our [scmchangelog-maven-plugin plugin|http://mojo.codehaus.org/scmchangelog-maven-plugin/]. Post your problem to [maven user mailing list|http://maven-users.828.n2.nabble.com/] or create an issue in the [maven-scm-plugin plugin issue tracker|http://jira.codehaus.org/browse/SCM] CVS checkout giving error - Key: SCM-569 URL: http://jira.codehaus.org/browse/SCM-569 Project: Maven SCM Issue Type: Bug Reporter: Monica Dube I am getting following error when do CVS checkout using maven. Please help me [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.The cvs command failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55 6) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.The cvs command failed. at org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:398) at org.apache.maven.scm.plugin.CheckoutMojo.checkout(CheckoutMojo.java:128) at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:93) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more -- 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-640) org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
[ http://jira.codehaus.org/browse/SUREFIRE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232778#action_232778 ] Michael Hinterseher commented on SUREFIRE-640: -- I removed redirectTestOutputToFile. I will post in case the problem occurs again. org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser --- Key: SUREFIRE-640 URL: http://jira.codehaus.org/browse/SUREFIRE-640 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.6 Environment: Maven 2.2.1 Reporter: Michael Hinterseher Priority: Minor Since update to Surefire 2.6 our CI server is breaking builds every now and then with: ... Results : Tests run: 42, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser [INFO] [INFO] For more information, run Maven with the -e switch ... Up to now I was not able to reproduce the issue. It looks like a concurrency issue. Configuration: configuration systemPropertyVariables net.sourceforge.cobertura.datafiletarget/cobertura/cobertura.ser/net.sourceforge.cobertura.datafile java.awt.headlesstrue/java.awt.headless /systemPropertyVariables redirectTestOutputToFiletrue/redirectTestOutputToFile /configuration Probably due to 42 tests ;-) -- 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: (MCHANGES-200) Problem with login to jira over https and proxy
[
http://jira.codehaus.org/browse/MCHANGES-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232781#action_232781
]
Krashan Brahmanjara commented on MCHANGES-200:
--
Hi
You forget about my mail from 23/Jul/10 4:40 AM.
Problem is in invalid java code with incorrect login algorithm to ssl site.
Resolution and fix is above. With this fix everything works well and users can
login to ssl site.
Problem with login to jira over https and proxy
---
Key: MCHANGES-200
URL: http://jira.codehaus.org/browse/MCHANGES-200
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira-report
Environment: Jdk 1.6_18
Jira Enterprise Edition, Version: 3.13.3-#344)
Reporter: Krashan Brahmanjara
Attachments: AbstractJiraDownloader.java
I cannot get changes log from JIRA but url used by maven is correct.
I mean url
https://jira.prv.pl/secure/IssueNavigator.jspa?view=rsspid=INSCSresolution=1sorter/field=issuetypesorter/order=ASCtempMax=100reset=truedecorator=none
get correct xml in browsers like FF or IE however untrusted certificate info
are displayed..
BTW
Login phase is very long.
Deatils
{noformat}
[DEBUG] Using proxy: 10.4.1.1 at port 3118
[DEBUG] JIRA lives at: https://jira.prv.pl
[DEBUG] Login URL:
https://jira.prv.pl/login.jsp?os_destination=/secure/os_username=TR$%^os_password=*
[DEBUG] Successfully logged in into JIRA.
[DEBUG] download jira issues from url
https://jira.prv.pl/secure/IssueNavigator.jspa?view=rsspid=INSCSresolution=1sorter/field=issuetypesorter/order=ASCtempMax=100reset=truedecorator=none
[INFO] Downloading from JIRA at:
https://jira.prv.pl/secure/IssueNavigator.jspa?view=rsspid=INSCSresolution=1sorter/field=issuetypesorter/order=ASCtempMax=100reset=truedecorator=none
[WARNING] Downloading from JIRA failed. Received: [503]
{noformat}
Pom configuration
{code:xml}
issueManagement
systemjira/system
urlhttps://jira.prv.pl/browse?id=INSCS/url
/issueManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.3/version
reportSets
reportSet
reports
/reports
/reportSet
/reportSets
configuration
onlyCurrentVersiontrue/onlyCurrentVersion
filterresolution=1amp;sorter/field=issuetypeamp;sorter/order=ASC/filter
statusIdsClosed/statusIds
jiraPasswordx/jiraPassword
jiraUserTR/jiraUser
onlyCurrentVersiontrue/onlyCurrentVersion
/configuration
/plugin
{code}
--
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: (MRELEASE-496) Branch not working in batch mode
[ http://jira.codehaus.org/browse/MRELEASE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232796#action_232796 ] Michael Wenig commented on MRELEASE-496: This seems to be fixed in 2.0 with MRELEASE-377 Branch not working in batch mode Key: MRELEASE-496 URL: http://jira.codehaus.org/browse/MRELEASE-496 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-9 Environment: Apache Maven 2.1.0 (r755702; 2009-03-19 06:10:27+1100) Java version: 1.6.0_10 Java home: /usr/java/jdk1.6.0_10/jre Default locale: en_AU, platform encoding: UTF-8 OS name: linux version: 2.6.30.8-64.fc11.x86_64 arch: amd64 Family: unix Reporter: Matt Milliss Attachments: patch_branch_version_defaults.txt Creating a branch batch mode fails. From a trunk version 09.20.00-SNAPSHOT I try to create a branch with the version 09.20.01-SNAPSHOT. The following command to branch in non-batch mode works fine, mvn release:branch -DbranchName=09.20.00_BRANCH -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false when prompted for the branch version I enter 09.20.01-SNAPSHOT, this works as expected and the branch is created with the version 09.20.01-SNAPSHOT. In batch mode the following command creates a branch with the same version as trunk mvn release:branch -DbranchName=09.20.00_BRANCH -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -Dproject.rel.my.org:myProject=09.20.01-SNAPSHOT --batch-mode -- 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-4774) Setting MAVEN_OPTS adds new lifecycles to be executed
Setting MAVEN_OPTS adds new lifecycles to be executed - Key: MNG-4774 URL: http://jira.codehaus.org/browse/MNG-4774 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0-beta-2 Reporter: ccadete If MAVEN_OPTS is set like this: export MAVEN_OPTS=-Xms256m -Xmx512m Maven, adds ms256m and mx512m to the lifecycle to be executed. The output: [DEBUG] === REACTOR BUILD PLAN [DEBUG] Project: project:my-project:pom:0.0.1-SNAPSHOT [DEBUG] Tasks: [ms256m, mx512m, clean, package] then it fails with [ERROR] Unknown lifecycle phase ms256m. You must specify a valid lifecycle phase or a goal in the format plugin-prefi x:goal or plugin-group-id:plugin-artifact-id[:plugin-version]:goal - [Help 1] Maven should not add ms256m, mx512m as lifecycle of the project. -- 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-4774) Setting MAVEN_OPTS adds new lifecycles to be executed
[
http://jira.codehaus.org/browse/MNG-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232803#action_232803
]
Benjamin Bentmann commented on MNG-4774:
I'm not able to reproduce this (using bsh on Mac and Ubuntu) so we need some
more information about your environment. E.g. what's the output of {{echo
$MAVEN_OPTS}}, what shell are you using?
Also, does this issue show up in 3.0-beta-2 only or also in beta-1? I wonder
whether the changes for MNG-3529 cause this.
Setting MAVEN_OPTS adds new lifecycles to be executed
-
Key: MNG-4774
URL: http://jira.codehaus.org/browse/MNG-4774
Project: Maven 2 3
Issue Type: Bug
Affects Versions: 3.0-beta-2
Reporter: ccadete
If MAVEN_OPTS is set like this:
export MAVEN_OPTS=-Xms256m -Xmx512m
Maven, adds ms256m and mx512m to the lifecycle to be executed. The output:
[DEBUG] === REACTOR BUILD PLAN
[DEBUG] Project: project:my-project:pom:0.0.1-SNAPSHOT
[DEBUG] Tasks: [ms256m, mx512m, clean, package]
then it fails with
[ERROR] Unknown lifecycle phase ms256m. You must specify a valid lifecycle
phase or a goal in the format plugin-prefi
x:goal or plugin-group-id:plugin-artifact-id[:plugin-version]:goal
- [Help 1]
Maven should not add ms256m, mx512m as lifecycle of the project.
--
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: (MRELEASE-496) Branch not working in batch mode
[ http://jira.codehaus.org/browse/MRELEASE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-496. - Resolution: Duplicate Assignee: Brett Porter thanks for letting us know. If anyone has a different experience, please reopen. Branch not working in batch mode Key: MRELEASE-496 URL: http://jira.codehaus.org/browse/MRELEASE-496 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-9 Environment: Apache Maven 2.1.0 (r755702; 2009-03-19 06:10:27+1100) Java version: 1.6.0_10 Java home: /usr/java/jdk1.6.0_10/jre Default locale: en_AU, platform encoding: UTF-8 OS name: linux version: 2.6.30.8-64.fc11.x86_64 arch: amd64 Family: unix Reporter: Matt Milliss Assignee: Brett Porter Attachments: patch_branch_version_defaults.txt Creating a branch batch mode fails. From a trunk version 09.20.00-SNAPSHOT I try to create a branch with the version 09.20.01-SNAPSHOT. The following command to branch in non-batch mode works fine, mvn release:branch -DbranchName=09.20.00_BRANCH -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false when prompted for the branch version I enter 09.20.01-SNAPSHOT, this works as expected and the branch is created with the version 09.20.01-SNAPSHOT. In batch mode the following command creates a branch with the same version as trunk mvn release:branch -DbranchName=09.20.00_BRANCH -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -Dproject.rel.my.org:myProject=09.20.01-SNAPSHOT --batch-mode -- 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: (MRELEASE-159) Support a pattern to generate the release tag
[ http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wenig updated MRELEASE-159: --- Attachment: MRELEASE-159-PATCH-2-0.patch I added a new patch file which is the second one from Dave ported to the final Release-Plugin Version 2.0 Support a pattern to generate the release tag - Key: MRELEASE-159 URL: http://jira.codehaus.org/browse/MRELEASE-159 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: prepare Affects Versions: 2.0-beta-4 Reporter: Joerg Schaible Attachments: MRELEASE-159-PATCH-2-0.patch, MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz, release-manager(updated).patch, release-manager-patch.patch The release-plugin uses currently the pattern artifactId-version to create the version tag. A configuration element would be fine to support different requirements for release tags (in our case v_version, since with svn the module is already part of the path). -- 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: (MRELEASE-159) Support a pattern to generate the release tag
[ http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232806#action_232806 ] Michael Wenig edited comment on MRELEASE-159 at 8/23/10 9:35 AM: - I added a new patch file which is the second one from Dave ported to the final Release-Plugin Version 2.0 Note: The patch was made against a copy of the release-tag in our local svn - so ignore the revision number :-) was (Author: micha123): I added a new patch file which is the second one from Dave ported to the final Release-Plugin Version 2.0 Support a pattern to generate the release tag - Key: MRELEASE-159 URL: http://jira.codehaus.org/browse/MRELEASE-159 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: prepare Affects Versions: 2.0-beta-4 Reporter: Joerg Schaible Attachments: MRELEASE-159-PATCH-2-0.patch, MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz, release-manager(updated).patch, release-manager-patch.patch The release-plugin uses currently the pattern artifactId-version to create the version tag. A configuration element would be fine to support different requirements for release tags (in our case v_version, since with svn the module is already part of the path). -- 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: (MRELEASE-159) Support a pattern to generate the release tag
[ http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232815#action_232815 ] Michael Wenig commented on MRELEASE-159: Please, please include it for the next release! Support a pattern to generate the release tag - Key: MRELEASE-159 URL: http://jira.codehaus.org/browse/MRELEASE-159 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: prepare Affects Versions: 2.0-beta-4 Reporter: Joerg Schaible Attachments: MRELEASE-159-PATCH-2-0.patch, MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz, release-manager(updated).patch, release-manager-patch.patch The release-plugin uses currently the pattern artifactId-version to create the version tag. A configuration element would be fine to support different requirements for release tags (in our case v_version, since with svn the module is already part of the path). -- 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: (MENFORCER-104) Specifying a message with an alwaysFail rule doesn't work
[
http://jira.codehaus.org/browse/MENFORCER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232816#action_232816
]
Eric Haszlakiewicz commented on MENFORCER-104:
--
Thanks!
Specifying a message with an alwaysFail rule doesn't work
-
Key: MENFORCER-104
URL: http://jira.codehaus.org/browse/MENFORCER-104
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.0-beta-1
Reporter: Eric Haszlakiewicz
Assignee: Dennis Lundberg
Fix For: 1.0-beta-2
All the other standard rules allow for a custom message to be displayed.
There was even a previous issue (MENFORCER-6) created that claims that a
message param was added to all rules, but this doesn't work for alwaysFail.
I expect this pom.xml file to display Custom Fail Message, but instead it
just says Always fails!:
{code:xml}
project
modelVersion4.0.0/modelVersion
groupIdcom.example/groupId
artifactIddummytest/artifactId
packagingpom/packaging
version1.0/version
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-enforcer-plugin/artifactId
!--version1.0-beta-1/version --
executions
execution
idenforce-alwaysfail/id
phasepackage/phase
goals
goalenforce/goal
/goals
configuration
rules
alwaysFail
messageCustom Fail Message/message
/alwaysFail
/rules
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
{code}
--
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: (MRELEASE-591) release:update-versions: add option to do a checkin
release:update-versions: add option to do a checkin --- Key: MRELEASE-591 URL: http://jira.codehaus.org/browse/MRELEASE-591 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0 Environment: Maven 2.2.1, Release-Plugin 2.0 Reporter: Michael Wenig Currently release:update-versions only modifies the poms locally. We want to run this on our hudson and expected the goal to change the version AND do a checkin. Unfortunately it does not... This is also unexpected as the documentation defines a scnCommentPrefix (which is not used here): http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html I would suggest a boolean-parameter 'commitChanges' which does a checkin so the functionality is like release:branch without creating a branch -- 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
Re: Maven jar does not preserve file permissions
Please re-post your question on the users list -- this one is for automated notices from the issue tracking system. -Wendy On Mon, Aug 23, 2010 at 1:46 PM, usammmy mythreye...@gmail.com wrote: I have some scripts under src/main/resources/scripts. These scripts are executables. But maven jar is not preserving these file permissions. Any suggestions? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-jar-does-not-preserve-file-permissions-tp2645103p2645103.html Sent from the Maven - Issues mailing list archive at Nabble.com.
Re: Maven jar does not preserve file permissions
Sorry about that. I am deleting this post. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Maven-jar-does-not-preserve-file-permissions-tp2645103p2645128.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Reopened: (MNG-2686) POM dependency scope auto-downgrades from provided to test
[ http://jira.codehaus.org/browse/MNG-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MNG-2686: Assignee: (was: Brett Porter) Reproduced and IT for MNG-1895 extended. Maven doesn't do anything special to resolve a conflict between provided and test scope, it just picks the scope from the nearest dependency. POM dependency scope auto-downgrades from provided to test -- Key: MNG-2686 URL: http://jira.codehaus.org/browse/MNG-2686 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.4 Reporter: Frank Cornelis Priority: Critical My project has a dependency on: XXX:YYY:jar:1.0-SNAPSHOT (selected for null) with transitive dependency: commons-logging:commons-logging:jar:1.1:test and again triggering a transitive dependency on: javax.servlet:servlet-api:jar:2.3:test (selected for test) Later on the project also has a dependency: AAA:BBB-container:pom:1.0-SNAPSHOT:provided (selected for provided) I use this to represent the dependencies provided by the J2EE container in which the application will be deployed. This triggers via: tomcat:catalina:jar:5.5.15:provided (selected for provided) the following funny thing: javax.servlet:servlet-api:jar:2.4:provided (removed - nearer found: 2.3) Leaving me without servlet-api for the compile scope. -- 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-4775) Outdated NOTICE.txt
Outdated NOTICE.txt
---
Key: MNG-4775
URL: http://jira.codehaus.org/browse/MNG-4775
Project: Maven 2 3
Issue Type: Bug
Components: Documentation: General
Affects Versions: 3.0-beta-2
Environment:
http://github.com/bentmann/maven-3/blob/repo/apache-maven/NOTICE.txt
Reporter: Jesse Glick
Priority: Minor
Beta 2 includes a {{NOTICE.txt}} which seems to be out of date, mentioning
JSCH, JTidy, and AspectJ, and not mentioning other things such as Google
Collections. The situation with the proposed Beta 3 code is even worse,
omitting mention of Aether or Guice.
Especially for embedded use, it would be nice to have a complete and current
list of third-party software included in the Maven distribution, i.e.
everything not developed inside the Maven source tree. This is not hard to
determine from the JAR names but those without an internal {{pom.xml}} such as
nekohtml are less obvious.
--
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: (WAGON-218) Link Parsing in http is flawed
[
http://jira.codehaus.org/browse/WAGON-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232855#action_232855
]
Jesse Glick commented on WAGON-218:
---
Why not get rid of nekohtml (+ XNI), saving 152 Kb as well as complexity in the
Maven third-party dependency list, and directly search for {{(?i)a
href=(.+?)}} or similar? After all, the intended use case is to find links
in index listings generated by a small number of distinct pieces of software.
These generators are surely not going to use exotic formatting or attributes of
the kind created by humans editing HTML by hand or with WYSIWYG designers.
I would be happy to supply a patch if there is interest.
Link Parsing in http is flawed
--
Key: WAGON-218
URL: http://jira.codehaus.org/browse/WAGON-218
Project: Maven Wagon
Issue Type: Improvement
Components: wagon-http, wagon-http-lightweight
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
The link parsing in wagon http has a few issues.
a) not all links detected.
b) the various ways that page content is identified via url string
manipulation isn't working in many example cases.
c) the use of jtidy introduces a large dependency and high memory usage.
--
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-4775) Outdated NOTICE.txt
[
http://jira.codehaus.org/browse/MNG-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4775.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-3
Assignee: Benjamin Bentmann
Updated in [r988265|http://svn.apache.org/viewvc?view=revisionrevision=988265].
Outdated NOTICE.txt
---
Key: MNG-4775
URL: http://jira.codehaus.org/browse/MNG-4775
Project: Maven 2 3
Issue Type: Bug
Components: Documentation: General
Affects Versions: 3.0-beta-2
Environment:
http://github.com/bentmann/maven-3/blob/repo/apache-maven/NOTICE.txt
Reporter: Jesse Glick
Assignee: Benjamin Bentmann
Priority: Minor
Fix For: 3.0-beta-3
Beta 2 includes a {{NOTICE.txt}} which seems to be out of date, mentioning
JSCH, JTidy, and AspectJ, and not mentioning other things such as Google
Collections. The situation with the proposed Beta 3 code is even worse,
omitting mention of Aether or Guice.
Especially for embedded use, it would be nice to have a complete and current
list of third-party software included in the Maven distribution, i.e.
everything not developed inside the Maven source tree. This is not hard to
determine from the JAR names but those without an internal {{pom.xml}} such
as nekohtml are less obvious.
--
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: (MENFORCER-96) 'requirePluginVersions' recognizises some released maven-plugins as SNAPSHOTS
[
http://jira.codehaus.org/browse/MENFORCER-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MENFORCER-96.
--
Resolution: Not A Bug
The message says that the versions are not locked down, and adds additional
info that snapshots are not allowed (even if they are explicitly defined). IE
this rule is intended to check that you have defined your preferred versions
somewhere in your pom hierarchy and that you haven't just allowed the defaults
from the super pom to fall through.
'requirePluginVersions' recognizises some released maven-plugins as SNAPSHOTS
-
Key: MENFORCER-96
URL: http://jira.codehaus.org/browse/MENFORCER-96
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.0-beta-1
Reporter: Lars Corneliussen
Have a look at this log. 2.4 can't be a snapshot, can it?
{noformat}
[INFO] [enforcer:enforce {execution: default-cli}]
[WARNING] Rule 2: org.apache.maven.plugins.enforcer.RequirePluginVersions
failed with message:
Some plugins are missing valid versions:(SNAPSHOT are not allowed )
org.apache.maven.plugins:maven-clean-plugin.The version currently in use
is 2.4
org.apache.maven.plugins:maven-deploy-plugin. The version currently in use
is 2.5
org.apache.maven.plugins:maven-install-plugin. The version currently in use
is 2.3
org.apache.maven.plugins:maven-site-plugin. The version currently in use
is 2.1
{noformat}
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-enforcer-plugin/artifactId
version1.0-beta-1/version
configuration
rules
requireReleaseVersion /
requireReleaseDeps
messageAll dependencies must be released!/message
failWhenParentIsSnapshottrue/failWhenParentIsSnapshot
/requireReleaseDeps
requirePluginVersions
banReleasefalse/banRelease
banLatestfalse/banLatest
banSnapshotstrue/banSnapshots
banTimestampsfalse/banTimestamps
!-- unCheckedPlugins
unCheckedPluginorg.apache.maven.plugins:maven-clean-plugin/unCheckedPlugin
unCheckedPluginorg.apache.maven.plugins:maven-deploy-plugin/unCheckedPlugin
unCheckedPluginorg.apache.maven.plugins:maven-install-plugin/unCheckedPlugin
unCheckedPluginorg.apache.maven.plugins:maven-site-plugin/unCheckedPlugin
/unCheckedPlugins --
/requirePluginVersions
/rules
failtrue/fail
/configuration
/plugin
{code}
When I list the plugins as unChecked, it passes.
--
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: (MSHARED-160) Replace pom.* properties with project.* properties in all maven-archiver website examples
Replace pom.* properties with project.* properties in all maven-archiver website examples - Key: MSHARED-160 URL: http://jira.codehaus.org/browse/MSHARED-160 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Brett Randall Priority: Minor Replace pom.* properties with project.* properties in all maven-archiver website examples. pom.* properties are deprecated. There are many occurrences e.g. http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html ( pom.url ) http://maven.apache.org/shared/maven-archiver/examples/manifest.html -- 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
