[jira] Commented: (MNG-4319) Property expansion does not work for goals in plugin executions
[
http://jira.codehaus.org/browse/MNG-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193415#action_193415
]
Marc Rohlfs commented on MNG-4319:
--
Hi Paul, I think You're right. This issue should have been marked as a
regression. Do You think we might reopen it to get it fixed in 2.2.2? I'd
really like to use some of the new features that were introduced in Maven 2.2,
but this issue prevents me from upgrading.
> Property expansion does not work for goals in plugin executions
> ---
>
> Key: MNG-4319
> URL: http://jira.codehaus.org/browse/MNG-4319
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.0-M1, 2.1.0, 2.2.0, 2.2.1
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_02
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Marc Rohlfs
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-2
>
>
> I am using a (global) property to control the goal(s) of the Assembly Plugin
> to be executed:
> {code:xml}
>
> ${build.assembly.goal}
>
> {code}
> The property is pre-defined in my (parent) POM and may be overwritten using
> the {{-D}} option on the command line or (for convenience) using a profile.
> This is (was) a very convenient way to switch from ZIP (goal {{single}}) to
> directory (goal {{directory-single}}) packaging during development of
> programm packages.
> When I tried to upgrade from Maven 2.0.10 to Maven 2.2.1 I noticed that this
> doesn't work any more. I also tried intermediate versions and it seems that
> 2.0.10 was the last version where it works.
--
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-4288) Move Igor's performance framework tests into Maven tree somewhere appropriate
[ http://jira.codehaus.org/browse/MNG-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193427#action_193427 ] Benjamin Bentmann commented on MNG-4288: The PTs require a patched version of the Eclipse Performance Framework. As far as I understand from [0|http://www.apache.org/legal/3party.html#criteriaandcategories], [1|http://www.apache.org/legal/resolved.html#category-b], [2|http://www.eclipse.org/legal/epl-v10.html], [3|http://www.eclipse.org/legal/eplfaq.php#PROPPROD], we may not keep those sources in ASF repos. It seems however allowed to maintain the source code at say Sonatype, and have Sonatype do a release of the patched version, using ASL for the binary form that could then be consumed by the PTs. > Move Igor's performance framework tests into Maven tree somewhere appropriate > - > > Key: MNG-4288 > URL: http://jira.codehaus.org/browse/MNG-4288 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-2 >Reporter: Jason van Zyl > Fix For: 3.0-alpha-3 > > > Makes more sense to keep the perf tests with Maven tree. Or maybe we'll set > them up like the ITs so when multiple strains of 3.x show up we can easily > test them. -- 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-4261) site plugin doesn't generate reports
[
http://jira.codehaus.org/browse/MNG-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193430#action_193430
]
Olivier Lamy commented on MNG-4261:
---
So maven-site-plugin (branch 3.x) works with the restrictions related
[here|http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin]
The last point (regarding configuration) is not fully implemented yet.
But the site plugin works with the current configuration (using reporting
section from the pom).
> site plugin doesn't generate reports
>
>
> Key: MNG-4261
> URL: http://jira.codehaus.org/browse/MNG-4261
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-3
>Reporter: Olivier Lamy
>Priority: Blocker
> Fix For: 3.0-alpha-3
>
>
> With the current trunk (rev 798335), reports mojo are not populated anymore
> in the site mojo. (expression ${reports} )
--
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-3991) POM validator allows optional but it is not valid.
[
http://jira.codehaus.org/browse/MNG-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193439#action_193439
]
Benjamin Bentmann commented on MNG-3991:
Had to relax the validation to only produce warnings in
[r821758|http://svn.apache.org/viewvc?view=rev&revision=821758]. This is a
compromise to keep backward-compat with extensions like Flex Mojos that use
[custom dependency
scopes|https://docs.sonatype.org/display/FLEXMOJOS/Adding+libraries+to+compilation].
> POM validator allows optional but it is not valid.
> -
>
> Key: MNG-3991
> URL: http://jira.codehaus.org/browse/MNG-3991
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.10, 2.1.0, 2.2.0
>Reporter: Julien HENRY
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> In my project I did a mistake and I wrote
> {code}
>
> org.slf4j
> slf4j-log4j12
> 1.5.0
> optional
>
> {code}
> but in fact I intended to write
> {code}
>
> org.slf4j
> slf4j-log4j12
> 1.5.0
> true
>
> {code}
> I'm very surprised that Maven doesn't detect such a mistake during the
> validate phase. Could it be possible to add a check to allow only valid
> scopes.
> Thanks
--
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: (SCM-496) org.apache.maven.scm.NoSuchCommandScmException: No such command 'list' when the Perforce SCM Provider is used by the SCM Wagon in "maven deploy"
[ http://jira.codehaus.org/browse/SCM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Ashikhmin updated SCM-496: - Attachment: SCM-496-maven-scm-provider-perforce-1.2.patch Hi, I've attached proposed patch for this issue > org.apache.maven.scm.NoSuchCommandScmException: No such command 'list' when > the Perforce SCM Provider is used by the SCM Wagon in "maven deploy" > > > Key: SCM-496 > URL: http://jira.codehaus.org/browse/SCM-496 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce > Environment: Maven 2.2.1, jdk 1.6 SR16, Win32 >Reporter: Louis Lecaroz >Priority: Critical > Attachments: pom.xml, SCM-496-maven-scm-provider-perforce-1.2.patch > > > After having taken a look in the svn in trunk, the AbstractScmProvider & its > implementations except Perforce implement the AbstractScmProvider.list() > method. > As this method is called by the ScmWagon, & because it is not implemented in > the PerforceScmProvider, it generates this exception (generated by the > AbstractScmProvider.list() code ) : > Uploading: > scm:perforce:lleca...@pperforce.server.com:1971://experiments/llecaroz/Maven/Repository/demo/foo/app/tp.sun.java-test-1/1.2-SNAPSHOT/tp.sun.java-test-1-1.2-20090903.105728-1.jar > [INFO] No password found, proceeding without it. > [DEBUG] No such command 'list'. > org.apache.maven.scm.NoSuchCommandScmException: No such command 'list'. > at > org.apache.maven.scm.provider.AbstractScmProvider.list(AbstractScmProvider.java:595) > at > org.apache.maven.scm.provider.AbstractScmProvider.list(AbstractScmProvider.java:579) > at > org.apache.maven.wagon.providers.scm.ScmWagon.checkOut(ScmWagon.java:371) > at > org.apache.maven.wagon.providers.scm.ScmWagon.putInternal(ScmWagon.java:285) > at org.apache.maven.wagon.providers.scm.ScmWagon.put(ScmWagon.java:254) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107) > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java: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) > So I was unable to use the Perforce SCM Provider as SCM Wagn as you will see > in this simplified attached/POM(testcase) to reproduce the issue. > Don't forget to replace the url & username by a working one. > To run it : > -detach this pom > -modify the url to a valid perforce server > -launch "maven deploy" > Tried with svn just by switching the extension from perforce into svn & > modifying the url : no problem... as svn provider implements the list() > method. > So the list() method needs to be implemented in the PerforceScmProvider as > solution. > At this time from my understanding, no project can use perforce as repository. > Thx in advance >
[jira] Issue Comment Edited: (SCM-496) org.apache.maven.scm.NoSuchCommandScmException: No such command 'list' when the Perforce SCM Provider is used by the SCM Wagon in "maven deploy"
[ http://jira.codehaus.org/browse/SCM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193452#action_193452 ] Andrey Ashikhmin edited comment on SCM-496 at 10/5/09 7:23 AM: --- Hi, I've attached a patch for this issue was (Author: ashiand): Hi, I've attached proposed patch for this issue > org.apache.maven.scm.NoSuchCommandScmException: No such command 'list' when > the Perforce SCM Provider is used by the SCM Wagon in "maven deploy" > > > Key: SCM-496 > URL: http://jira.codehaus.org/browse/SCM-496 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce > Environment: Maven 2.2.1, jdk 1.6 SR16, Win32 >Reporter: Louis Lecaroz >Priority: Critical > Attachments: pom.xml, SCM-496-maven-scm-provider-perforce-1.2.patch > > > After having taken a look in the svn in trunk, the AbstractScmProvider & its > implementations except Perforce implement the AbstractScmProvider.list() > method. > As this method is called by the ScmWagon, & because it is not implemented in > the PerforceScmProvider, it generates this exception (generated by the > AbstractScmProvider.list() code ) : > Uploading: > scm:perforce:lleca...@pperforce.server.com:1971://experiments/llecaroz/Maven/Repository/demo/foo/app/tp.sun.java-test-1/1.2-SNAPSHOT/tp.sun.java-test-1-1.2-20090903.105728-1.jar > [INFO] No password found, proceeding without it. > [DEBUG] No such command 'list'. > org.apache.maven.scm.NoSuchCommandScmException: No such command 'list'. > at > org.apache.maven.scm.provider.AbstractScmProvider.list(AbstractScmProvider.java:595) > at > org.apache.maven.scm.provider.AbstractScmProvider.list(AbstractScmProvider.java:579) > at > org.apache.maven.wagon.providers.scm.ScmWagon.checkOut(ScmWagon.java:371) > at > org.apache.maven.wagon.providers.scm.ScmWagon.putInternal(ScmWagon.java:285) > at org.apache.maven.wagon.providers.scm.ScmWagon.put(ScmWagon.java:254) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107) > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java: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) > So I was unable to use the Perforce SCM Provider as SCM Wagn as you will see > in this simplified attached/POM(testcase) to reproduce the issue. > Don't forget to replace the url & username by a working one. > To run it : > -detach this pom > -modify the url to a valid perforce server > -launch "maven deploy" > Tried with svn just by switching the extension from perforce into svn & > modifying the url : no problem... as svn provider implements the list() > method. > So the list() method needs to be implemented in the PerforceScmProvider
[jira] Closed: (MNG-4383) Uninterpolated expressions should cause an error
[
http://jira.codehaus.org/browse/MNG-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4383.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Made validator error out on uninterpolated dependency versions in
[r821772|http://svn.apache.org/viewvc?view=rev&revision=821772].
> Uninterpolated expressions should cause an error
>
>
> Key: MNG-4383
> URL: http://jira.codehaus.org/browse/MNG-4383
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.2.1, 3.0-alpha-2
>Reporter: Paul Benedict
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> I declared a dependency as such:
> {noformat}
> org.slf4j
> slf4j-api
> ${slf4j.version}
> {noformat}
> But did not define the *slf4j.version* property. Obviously ${...} is an
> expression and if the expression is not resolved, why allow it? Here was the
> output:
> {noformat} Downloading:
> http://repo1.maven.org/maven2/org/slf4j/slf4j-api/${slf4j.version}/slf4j-api-${slf4j.version}.pom{noformat}
>
> In terms of usability, an obvious expression should be interpolated. If it
> cannot, it should be a runtime error.
--
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-4383) Uninterpolated expressions should cause an error
[
http://jira.codehaus.org/browse/MNG-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193461#action_193461
]
Paul Benedict commented on MNG-4383:
Awesome! Thanks for fixing this.
> Uninterpolated expressions should cause an error
>
>
> Key: MNG-4383
> URL: http://jira.codehaus.org/browse/MNG-4383
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.2.1, 3.0-alpha-2
>Reporter: Paul Benedict
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> I declared a dependency as such:
> {noformat}
> org.slf4j
> slf4j-api
> ${slf4j.version}
> {noformat}
> But did not define the *slf4j.version* property. Obviously ${...} is an
> expression and if the expression is not resolved, why allow it? Here was the
> output:
> {noformat} Downloading:
> http://repo1.maven.org/maven2/org/slf4j/slf4j-api/${slf4j.version}/slf4j-api-${slf4j.version}.pom{noformat}
>
> In terms of usability, an obvious expression should be interpolated. If it
> cannot, it should be a runtime error.
--
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: (SCM-500) Make the perforce provider suitable for Wagon SCM
Make the perforce provider suitable for Wagon SCM - Key: SCM-500 URL: http://jira.codehaus.org/browse/SCM-500 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.2 Environment: wagon-scm 1.0-beta-6, remapped to SCM 1.2 Reporter: Andrey Ashikhmin Attachments: wagon-scm-patch-against-maven-scm-provider-perforce-1.2.patch Apart form SCM-496, at least two issues must be fixed: 1) add, checkin, and status command should honour clientspec 2) checkin should correctly process ScmFileSet with empty file list (per ScmProvider spec) I'm attaching a patch for these two issues -- 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: (WAGON-286) Confurable SCM comment prefix
Confurable SCM comment prefix - Key: WAGON-286 URL: http://jira.codehaus.org/browse/WAGON-286 Project: Maven Wagon Issue Type: Improvement Components: wagon-scm Affects Versions: 1.0-beta-6 Reporter: Andrey Ashikhmin Attachments: scm.comment.prefix-against-wagon-scm-1.0-beta-6 .patch Currently Wagon SCM check in all files with a comment starting with "Wagon: ". It's desired (and sometimes necessary with certain SCM provider settings) to configure it. maven-release-plugin is configurable in this area. I'm attaching a patch. -- 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: (WAGON-287) Add Perforce support to Wagon SCM for deploy
Add Perforce support to Wagon SCM for deploy Key: WAGON-287 URL: http://jira.codehaus.org/browse/WAGON-287 Project: Maven Wagon Issue Type: Bug Components: wagon-scm Affects Versions: 1.0-beta-6 Environment: Maven SCM 1.2 with SCM-496 and SCM-500 patched Reporter: Andrey Ashikhmin Attachments: p4-patch-against-wagon-scm-1.0-beta-6 .patch Currently Wagon SCM needs several things to allow perforce support (provided SCM-500 is fixed) # Update dependencies to SCM version 1.2 or higher (check plexus-utils also) # providerRepository.setPersistCheckout(true) # As we don't edit or remove files from SCM in ScmWagon.putInternal, it doesn't make sense to override checked out files (the override is in conflict with the read-only flag of files synced from p4) I'm attaching a patch for issues #2 & #3 -- 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-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193496#action_193496 ] Mark Hobson commented on MCHECKSTYLE-105: - Is there any good reason why I can't commit this patch to trunk? I've tried it locally and it seems to work fine. > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0-812221.patch, > update-to-5.0.patch, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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-105) Update to Checkstyle 5.0
[ http://jira.codehaus.org/browse/MCHECKSTYLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193497#action_193497 ] Olivier Lamy commented on MCHECKSTYLE-105: -- I think the main issue is 1.5 required. But if you have to commit this do it quickly because 1.5 end support by sun is [30 October 09|http://java.sun.com/products/archive/eol.policy.html] Yes I know a little bit ironical comment :P > Update to Checkstyle 5.0 > > > Key: MCHECKSTYLE-105 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-105 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Felix Röthenbacher > Fix For: 2.4 > > Attachments: patch.diff, update-to-5.0-812221.patch, > update-to-5.0.patch, update-to-5.0beta2.patch > > > Checkstyle 5.0-beta01 adds support for generics, etc. > See > http://checkstyle.sourceforge.net/5.x/releasenotes.html > for a list of new features. > Note: Prerequisite is that checkstyle-all jar, version 5.0-beta01 is > available from a public Maven repository. > Patch updates plugin to changed API / implementation. -- 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: (MJAVADOC-267) Allow changing the reportOutputDirectory from the commandline
Allow changing the reportOutputDirectory from the commandline - Key: MJAVADOC-267 URL: http://jira.codehaus.org/browse/MJAVADOC-267 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.6 Reporter: Dirk Olmes Attachments: reportOutputDirectory.patch We run the javadoc:aggregate task from the CI server to publish javadocs for a certain release. It's not possible now to specifiy the reportOutputDirectory from the commandline by running mvn -DreportOutputDirectory=/dest/dir javadoc:aggregate Instead, you have to put this config in a profile/property which exposes too much environment specific info in the pom. The attached simple patch allows for specifying the reportOutputDirectory on the cmdline while preserving existing behaviour. -- 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: (MAVENUPLOAD-2606) request to upload the standalone eclipse compiler ecj-3.5.jar to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193562#action_193562 ] Hugues Malphettes commented on MAVENUPLOAD-2606: Hi there, I have uploaded to a public repository the 3.5.0 and 3.5.1 version of the ecj: http://www.intalio.org/public/eclipse-m2repo/org/eclipse/jdt/ecj/ I have uploaded the md5 checksums as downloaded from the main eclipse website and the locations of the original downloads are part of the comments in the pom.xml. the sha1 are missing. I have made sure with a small project that maven does download ecj-3.5.1 correctly. I know of 3 projects looking for this: - the glassfish-jasper project: https://jsp.dev.java.net/issues/show_bug.cgi?id=13 - the buildr4osgi project: http://jira.intalio.org/jira/browse/BOSGI-26 - jetty hightide-on-osgi: I don't have ownership of org.eclipse.jdt however there are already other eclipse jars in this group. Please let me know if I am missing something to have this request fulfilled. In particular I can enable rsynch on this repository. Let me know if that would help. Thanks > request to upload the standalone eclipse compiler ecj-3.5.jar to maven > repository > - > > Key: MAVENUPLOAD-2606 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2606 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Hugues Malphettes > > ecj-3.5.jar is a java compiler developed by eclipse by the JDT/core project: > http://eclipse.org/jdt/core/index.php > The eclipse java compiler is commonly used as a drop-in replacement of the > JDK's javac tool. > It has no dependency and is widely used for example by the jsp compiler > "jasper". > The 2005 version is named core-3.1.1.jar and is currently distributed with > all popular app-servers: jetty-hightide, glassfish, jboss etc. > http://repo2.maven.org/maven2/org/eclipse/jdt/core/3.1.1/ > ecj-3.5 has multiple advantages over core-3.1.1: > - up to date, support for producing java-1.6 bytecode if necessary. > - smaller than core-3.1.1 that comes with a lot of unused eclipse-only > classes. > - when loaded in an OSGi container it does not require eclipse-RCP (see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=289406) > jasper now supports ecj-3.5 and will probably recommend using it: > https://jsp.dev.java.net/issues/show_bug.cgi?id=13 -- 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: (WAGON-286) Confurable SCM comment prefix
[ http://jira.codehaus.org/browse/WAGON-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-286: --- Fix Version/s: 1.0 > Confurable SCM comment prefix > - > > Key: WAGON-286 > URL: http://jira.codehaus.org/browse/WAGON-286 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-scm >Affects Versions: 1.0-beta-6 >Reporter: Andrey Ashikhmin > Fix For: 1.0 > > Attachments: scm.comment.prefix-against-wagon-scm-1.0-beta-6 .patch > > > Currently Wagon SCM check in all files with a comment starting with "Wagon: ". > It's desired (and sometimes necessary with certain SCM provider settings) to > configure it. > maven-release-plugin is configurable in this area. > I'm attaching a patch. -- 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: (WAGON-287) Add Perforce support to Wagon SCM for deploy
[ http://jira.codehaus.org/browse/WAGON-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-287: --- Fix Version/s: 1.0 > Add Perforce support to Wagon SCM for deploy > > > Key: WAGON-287 > URL: http://jira.codehaus.org/browse/WAGON-287 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-scm >Affects Versions: 1.0-beta-6 > Environment: Maven SCM 1.2 with SCM-496 and SCM-500 patched >Reporter: Andrey Ashikhmin > Fix For: 1.0 > > Attachments: p4-patch-against-wagon-scm-1.0-beta-6 .patch > > > Currently Wagon SCM needs several things to allow perforce support (provided > SCM-500 is fixed) > # Update dependencies to SCM version 1.2 or higher (check plexus-utils also) > # providerRepository.setPersistCheckout(true) > # As we don't edit or remove files from SCM in ScmWagon.putInternal, it > doesn't make sense to override checked out files (the override is in conflict > with the read-only flag of files synced from p4) > I'm attaching a patch for issues #2 & #3 -- 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: (SCM-501) Perforce Provider ignores p4 errors from stderr
Perforce Provider ignores p4 errors from stderr --- Key: SCM-501 URL: http://jira.codehaus.org/browse/SCM-501 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.2 Reporter: Ryan Christianson It looks like between 1.1 and 1.2 the ablity to capture errors from p4 was removed. Is there any way to get this back in? It looks like it was added here: SCM-363 Thanks. Ryan -- 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
