[jira] Commented: (MSITE-295) Make the distributionManagement.site.url configurable from the command line

[ http://jira.codehaus.org/browse/MSITE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169907#action_169907 ] Wendy Smoak commented on MSITE-295: --- Did you try it with the build helper plugin and ${buildNumber}

[jira] Commented: (MSITE-295) Make the distributionManagement.site.url configurable from the command line

[ http://jira.codehaus.org/browse/MSITE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169906#action_169906 ] luke w patterson commented on MSITE-295: this feature is needed, it would align with deploy's

Re: [jira] Created: (MECLIPSE-529) File not found - target/classes access denied

It works well when the another project is closed! :super: JIRA j...@codehaus.org wrote: > > File not found - target/classes access denied > - > > Key: MECLIPSE-529 > URL: http://jira.codehaus.org/browse/MECLIPSE-529

[jira] Closed: (MNG-4091) Validate the plugin descriptors and improve error reporting when mismatched with artifact

[ http://jira.codehaus.org/browse/MNG-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-4091. - Resolution: Fixed > Validate the plugin descriptors and improve error reporting when mismatched > with artifact

[jira] Created: (MCHANGES-154) Using an URL for the email template instead of the proiect local file

Using an URL for the email template instead of the proiect local file - Key: MCHANGES-154 URL: http://jira.codehaus.org/browse/MCHANGES-154 Project: Maven 2.x Changes Plugin

[jira] Created: (MCHANGES-153) For multi-module project, sending the email once for the project, not one email for each sub-module

For multi-module project, sending the email once for the project, not one email for each sub-module --- Key: MCHANGES-153 URL: http://jira.codehaus.org/browse/MCHANGES

[jira] Updated: (MNG-4091) Validate the plugin descriptors and improve error reporting when mismatched with artifact

[ http://jira.codehaus.org/browse/MNG-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4091: -- Assignee: Brett Porter Fix Version/s: 2.1.0 > Validate the plugin descriptors and improve error report

[jira] Created: (MNG-4091) Validate the plugin descriptors and improve error reporting when mismatched with artifact

Validate the plugin descriptors and improve error reporting when mismatched with artifact - Key: MNG-4091 URL: http://jira.codehaus.org/browse/MNG-4091 Project: M

[jira] Commented: (MRELEASE-372) add branchBase optional parameter for release:branch goal

[ http://jira.codehaus.org/browse/MRELEASE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169894#action_169894 ] Philippe Laflamme commented on MRELEASE-372: Our SVN structure is as follows: trunk/ b

[jira] Commented: (SCM-392) SCM SVN plugin does not cope with a flat structure

[ http://jira.codehaus.org/browse/SCM-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169889#action_169889 ] Joseph Chan commented on SCM-392: - Another workaround is to create another directory in SVN and add SVN

[jira] Created: (SCM-449) SvnUpdateCommand is updating all the working copy instead of only the fileSet passed in argument

SvnUpdateCommand is updating all the working copy instead of only the fileSet passed in argument Key: SCM-449 URL: http://jira.codehaus.org/browse/SCM-449

[jira] Issue Comment Edited: (MRELEASE-375) release plugin does not work with subversion > 1.5.0

[ http://jira.codehaus.org/browse/MRELEASE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169886#action_169886 ] Olivier Lamy edited comment on MRELEASE-375 at 3/16/09 7:56 PM: Wor

[jira] Closed: (MRELEASE-375) release plugin does not work with subversion > 1.5.0

[ http://jira.codehaus.org/browse/MRELEASE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-375. - Assignee: Olivier Lamy Resolution: Fixed Fix Version/s: 2.0-beta-9 Workaround impleme

[jira] Closed: (MRELEASE-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)

[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-427. - Assignee: Olivier Lamy Resolution: Fixed Fix Version/s: 2.0-beta-9 fixed [rev 755056|

[jira] Commented: (MRELEASE-375) release plugin does not work with subversion > 1.5.0

[ http://jira.codehaus.org/browse/MRELEASE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169884#action_169884 ] Olivier Lamy commented on MRELEASE-375: --- workaround will be implemented by MRELEASE-427. > r

[jira] Closed: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-406. Resolution: Fixed So I close this issue because it's now possible to tag remotely with the svnexe provider. Concern

[jira] Closed: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository

[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-262. Resolution: Fixed I close this issue as it's now possible to tag remotely with svn provider (using ScmTagParameter

[jira] Created: (MRELEASE-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)

Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codeha

[jira] Updated: (SCM-407) git scm:changelog does not have TCK Test yet

[ http://jira.codehaus.org/browse/SCM-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated SCM-407: -- Attachment: SCM-407.2.patch oh sorry Olivier, apologize! I've now attached the missing file in the test compone

[jira] Closed: (SCM-448) CheckInScmResult could return the scm revision (at least for svn provider)

[ http://jira.codehaus.org/browse/SCM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-448. Resolution: Fixed fixed in [rev 755019|http://svn.apache.org/viewvc?rev=755019&view=rev] > CheckInScmResult could r

[jira] Updated: (SCM-448) CheckInScmResult could return the scm revision (at least for svn provider)

[ http://jira.codehaus.org/browse/SCM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-448: - Assignee: Olivier Lamy Fix Version/s: 1.2 > CheckInScmResult could return the scm revision (at least for

[jira] Created: (SCM-448) CheckInScmResult could return the scm revision (at least for svn provider)

CheckInScmResult could return the scm revision (at least for svn provider) -- Key: SCM-448 URL: http://jira.codehaus.org/browse/SCM-448 Project: Maven SCM Issue Type: Ne

[jira] Commented: (SCM-407) git scm:changelog does not have TCK Test yet

[ http://jira.codehaus.org/browse/SCM-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169874#action_169874 ] Olivier Lamy commented on SCM-407: -- Mark, I have some issues with your patch, I can't apply it. It onl

[jira] Closed: (SCM-403) git scm:update command currently only works on the branch 'master'

[ http://jira.codehaus.org/browse/SCM-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-403. Resolution: Fixed fix in [rev 755014|http://svn.apache.org/viewvc?rev=755014&view=rev] Thanks ! > git scm:update co

[jira] Closed: (MSOURCES-38) Add zip goal to create a source zip containing all sources

[ http://jira.codehaus.org/browse/MSOURCES-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier closed MSOURCES-38. - Resolution: Won't Fix This can be done using the predefined source descriptor of the assembly plugin. > Add z

[jira] Commented: (MRELEASE-426) There is no way to specify a branch/tag/revision when performing a release

[ http://jira.codehaus.org/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169864#action_169864 ] Eric commented on MRELEASE-426: --- Typo - I meant ".. The scm plugin allows to specify scmVersion, scmV

[jira] Created: (MRELEASE-426) There is no way to specify a branch/tag/revision when performing a release

There is no way to specify a branch/tag/revision when performing a release -- Key: MRELEASE-426 URL: http://jira.codehaus.org/browse/MRELEASE-426 Project: Maven 2.x Release Plugin

[jira] Commented: (MASSEMBLY-209) Service provider configuration files should be concatenated instead of overwritten

[ http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169852#action_169852 ] Johan Walles commented on MASSEMBLY-209: Affects 2.2-beta-2 as well. > Service provider c

[jira] Commented: (MASSEMBLY-360) When using mulitple Spring dependencies, the files from META-INF (from the Spring jars) overwrite each other in an executable jar-with-dependencies.

[ http://jira.codehaus.org/browse/MASSEMBLY-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169849#action_169849 ] Johan Walles commented on MASSEMBLY-360: See also MASSEMBLY-209. > When using mulitple Sp

[jira] Created: (MRELEASE-425) When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run

When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run Key: MRELEASE-

[jira] Closed: (MNG-4090) Allow attribute based configuration

[ http://jira.codehaus.org/browse/MNG-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MNG-4090. Resolution: Duplicate Duplicate of MNG-3397 > Allow attribute based configuration > --

[jira] Created: (MNG-4090) Allow attribute based configuration

Allow attribute based configuration --- Key: MNG-4090 URL: http://jira.codehaus.org/browse/MNG-4090 Project: Maven 2 Issue Type: Bug Reporter: Gin-Ting Chen Currently we do: {code}

[jira] Created: (MNG-4089) Allow LATEST and RELEASE to peg major version similar to SNAPSHOT

Allow LATEST and RELEASE to peg major version similar to SNAPSHOT - Key: MNG-4089 URL: http://jira.codehaus.org/browse/MNG-4089 Project: Maven 2 Issue Type: Bug Repo

[jira] Created: (MEV-619) httpunit 1.6.2 should mark jtidy dependency as optional

httpunit 1.6.2 should mark jtidy dependency as optional --- Key: MEV-619 URL: http://jira.codehaus.org/browse/MEV-619 Project: Maven Evangelism Issue Type: Bug Components: Depende

[jira] Closed: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2361. --- Resolution: Fixed got the jar from jboss repo > Hibernate Search 3.1.0.GA >

[jira] Closed: (MWAR-186) Upgrade to XStream 1.3.1

[ http://jira.codehaus.org/browse/MWAR-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MWAR-186. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1-beta-1 Fixed in r754672. >

[jira] Created: (MWAR-186) Upgrade to XStream 1.3.1

Upgrade to XStream 1.3.1 Key: MWAR-186 URL: http://jira.codehaus.org/browse/MWAR-186 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.1-alpha-2 Reporter: Dennis Lundberg -- This

[jira] Reopened: (MWAR-184) FATAL ERROR - XPP3 pull parser library not present. Specify another driver.

[ http://jira.codehaus.org/browse/MWAR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MWAR-184: -- Thanks for clarifying that Jörg. > FATAL ERROR - XPP3 pull parser library not present. Specify another d

[jira] Updated: (MWAR-184) FATAL ERROR - XPP3 pull parser library not present. Specify another driver.

[ http://jira.codehaus.org/browse/MWAR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MWAR-184: - Assignee: (was: Dennis Lundberg) Fix Version/s: (was: 2.1-beta-1) > FATAL ERROR - XPP3

[jira] Commented: (ARCHETYPE-57) Support empty directory creation

[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169808#action_169808 ] Marc Pasteur commented on ARCHETYPE-57: --- ok so since the revision 688113 i can effectively ad

[jira] Commented: (MWAR-184) FATAL ERROR - XPP3 pull parser library not present. Specify another driver.

[ http://jira.codehaus.org/browse/MWAR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169807#action_169807 ] Joerg Schaible commented on MWAR-184: - Actually, this particular problem is not yet fixed in XStrea

[jira] Commented: (MEV-554) POM for joda-time-hibernate 1.0 is invalid

[ http://jira.codehaus.org/browse/MEV-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169791#action_169791 ] Grzegorz Borkowski commented on MEV-554: I'm spend long time fighting with my projects, only to

[jira] Created: (MNG-4088) settings.xml profiles are executed after project profiles

settings.xml profiles are executed after project profiles - Key: MNG-4088 URL: http://jira.codehaus.org/browse/MNG-4088 Project: Maven 2 Issue Type: Bug Components: Profiles

[jira] Updated: (MJAVADOC-219) skip parameter is ignored in aggregate goal

[ http://jira.codehaus.org/browse/MJAVADOC-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dirk Olmes updated MJAVADOC-219: Attachment: MJAVADOC-219.zip I'm having the same problem: I want aggregate javadocs but exclude some p