[jira] [Resolved] (MNG-5863) default pom's release-profile should invoke source plugin with goal "jar-no-fork" instead of "jar"

[ https://issues.apache.org/jira/browse/MNG-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka resolved MNG-5863. --- Resolution: Won't Fix understood. Another workaround, and probably also the right solution, is to rely

[jira] [Created] (MNG-5863) default pom's release-profile should use goal jar-no-fork instead of jar

Petr Kozelka created MNG-5863: - Summary: default pom's release-profile should use goal jar-no-fork instead of jar Key: MNG-5863 URL: https://issues.apache.org/jira/browse/MNG-5863 Project: Maven

[jira] [Updated] (MNG-5863) default pom's release-profile should invoke source plugin with goal jar-no-fork instead of jar

[ https://issues.apache.org/jira/browse/MNG-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka updated MNG-5863: -- Summary: default pom's release-profile should invoke source plugin with goal jar-no-fork instead of jar

[jira] [Updated] (MNG-5863) default pom's release-profile should invoke source with goal jar-no-fork instead of jar

[ https://issues.apache.org/jira/browse/MNG-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka updated MNG-5863: -- Summary: default pom's release-profile should invoke source with goal jar-no-fork instead of jar (was:

[jira] (SCM-650) HgChangeLogConsumer generates phantom 'null' changeset at the end

[ https://jira.codehaus.org/browse/SCM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka closed SCM-650. Resolution: Fixed Fix Version/s: 1.9 HgChangeLogConsumer generates phantom 'null' changeset at the end

[jira] (SCM-679) enhance scm api to support limited number of returned changesets by changelog command

[ https://jira.codehaus.org/browse/SCM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301488#comment-301488 ] Petr Kozelka commented on SCM-679: -- good idea, I will rewrite the patch enhance scm

[jira] (SCM-679) enhance scm api to support limited number of returned changesets by changelog command

[ https://jira.codehaus.org/browse/SCM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka updated SCM-679: - Attachment: scm-changelog-limit-wrapped.patch request style patch enhance scm api to support

[jira] (SCM-679) enhance scm api to support limited number of returned changesets by changelog command

[ https://jira.codehaus.org/browse/SCM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301578#comment-301578 ] Petr Kozelka commented on SCM-679: -- Hi Olivier, attached scm-changelog-limit-wrapped.patch contains

[jira] (SCM-679) enhance scm api to support limited number of returned changesets by changelog command

Petr Kozelka created SCM-679: Summary: enhance scm api to support limited number of returned changesets by changelog command Key: SCM-679 URL: https://jira.codehaus.org/browse/SCM-679 Project: Maven SCM

[jira] (SCM-676) Add property revision to CheckOutScmResult

Petr Kozelka created SCM-676: Summary: Add property revision to CheckOutScmResult Key: SCM-676 URL: https://jira.codehaus.org/browse/SCM-676 Project: Maven SCM Issue Type: Improvement

[jira] (MNG-5218) Allow properties containing ${basedir} to retain same value in sub-modules.

[ https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286044#comment-286044 ] Petr Kozelka commented on MNG-5218: --- @Ondrej: {quote} default relativePath is .., and if it's

[jira] (MNG-5218) Allow properties containing ${basedir} to retain same value in sub-modules.

[ https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285955#comment-285955 ] Petr Kozelka commented on MNG-5218: --- thanks I didn't know ... still, I believe that using this can

[jira] (MNG-5218) Allow properties containing ${basedir} to retain same value in sub-modules.

[ https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285847#comment-285847 ] Petr Kozelka commented on MNG-5218: --- The incompatibility problem could be avoided by introducing a

[jira] (MNG-5219) Regression from M2: Installing non-existing artifact is silently ignored

Petr Kozelka created MNG-5219: - Summary: Regression from M2: Installing non-existing artifact is silently ignored Key: MNG-5219 URL: https://jira.codehaus.org/browse/MNG-5219 Project: Maven 2 3

[jira] Reopened: (SCM-649) Enhance SCM changelog model to hold more data about changes

[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka reopened SCM-649: -- I just implemented simple support of this feature for Bazaar SCM so I hope it's ok to reopen the existing issue.

[jira] Updated: (SCM-649) Enhance SCM changelog model to hold more data about changes

[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka updated SCM-649: - Attachment: scm-richmodel-bazaar.patch Attaching the bazaar patch. Enhance SCM changelog model to hold more

[jira] Commented: (SCM-649) Enhance SCM changelog model to hold more data about changes

[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285387#comment-285387 ] Petr Kozelka commented on SCM-649: -- ... cannot add bazaar component to Jira issue, so I guess next

[jira] Commented: (SCM-649) Enhance SCM changelog model to hold more data about changes

[ https://jira.codehaus.org/browse/SCM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285084#comment-285084 ] Petr Kozelka commented on SCM-649: -- Hi Olivier, done, ack forwarded to your @apache mail Enhance

[jira] Created: (MINDEXER-46) bad url in jira description

bad url in jira description --- Key: MINDEXER-46 URL: https://jira.codehaus.org/browse/MINDEXER-46 Project: Maven Indexer Issue Type: Bug Reporter: Petr Kozelka Priority: Trivial current url

[jira] Created: (SCM-649) Enhance SCM changelog model to hold more data about changes

Enhance SCM changelog model to hold more data about changes --- Key: SCM-649 URL: https://jira.codehaus.org/browse/SCM-649 Project: Maven SCM Issue Type: Improvement

[jira] Created: (SCM-647) SvnChangeLogConsumer parses filename incorrectly when file is copied from existing one

SvnChangeLogConsumer parses filename incorrectly when file is copied from existing one -- Key: SCM-647 URL: https://jira.codehaus.org/browse/SCM-647 Project: Maven

[jira] Created: (SCM-646) git parser should fill changeset revision

git parser should fill changeset revision - Key: SCM-646 URL: https://jira.codehaus.org/browse/SCM-646 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects

[jira] Commented: (SCM-541) GitExe commit should include --allow-empty option

[ https://jira.codehaus.org/browse/SCM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283877#comment-283877 ] Petr Kozelka commented on SCM-541: -- Hello Kathryn, I just tested your suggested option - see

[jira] Commented: (MENFORCER-98) requirePluginVersions rule is not compatible with maven 3.0-beta-1

[ https://jira.codehaus.org/browse/MENFORCER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=275550#comment-275550 ] Petr Kozelka commented on MENFORCER-98: --- on Maven 3.0.3, requirePluginVersions is still not

[jira] Closed: (MANTRUN-151) provide a property always pointing to the currently effective local repository

[ http://jira.codehaus.org/browse/MANTRUN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka closed MANTRUN-151. Resolution: Fixed Fix Version/s: 1.5 seems that version 1.5 uses {{settings.localRepository}}

[jira] Reopened: (MINSTALL-78) install:install should remove leftovers from local repository

[ http://jira.codehaus.org/browse/MINSTALL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka reopened MINSTALL-78: -- You are right that I can configure some sort of explicit purging at buildserver; but this issue mainly

[jira] Created: (MANTRUN-152) Embedded task attachartifact does not work without classifier

Embedded task attachartifact does not work without classifier --- Key: MANTRUN-152 URL: http://jira.codehaus.org/browse/MANTRUN-152 Project: Maven 2.x Antrun Plugin Issue Type: Bug

[jira] Commented: (MINSTALL-66) The plugin should only install attached artifacts to the project if they have a classifier

[ http://jira.codehaus.org/browse/MINSTALL-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=236288#action_236288 ] Petr Kozelka commented on MINSTALL-66: -- in my company we use attached artifacts without

[jira] Created: (MANTRUN-153) install:install should remove leftovers from local repository

install:install should remove leftovers from local repository - Key: MANTRUN-153 URL: http://jira.codehaus.org/browse/MANTRUN-153 Project: Maven 2.x Antrun Plugin Issue Type: Bug

[jira] Created: (MINSTALL-78) install:install should remove leftovers from local repository

install:install should remove leftovers from local repository - Key: MINSTALL-78 URL: http://jira.codehaus.org/browse/MINSTALL-78 Project: Maven 2.x Install Plugin Issue Type: Bug

[jira] Closed: (MANTRUN-153) install:install should remove leftovers from local repository

[ http://jira.codehaus.org/browse/MANTRUN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka closed MANTRUN-153. Resolution: Won't Fix install:install should remove leftovers from local repository

[jira] Created: (MANTRUN-151) provide a property always pointing to the currently effective local repository

provide a property always pointing to the currently effective local repository -- Key: MANTRUN-151 URL: http://jira.codehaus.org/browse/MANTRUN-151 Project: Maven 2.x Antrun

[jira] Commented: (MENFORCER-98) requirePluginVersions rule is not compatible with maven 3.0-beta-1

[ http://jira.codehaus.org/browse/MENFORCER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=234740#action_234740 ] Petr Kozelka commented on MENFORCER-98: --- with Maven 3.0-beta-3 it does not check again

[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232662#action_232662 ] Petr Kozelka commented on MRELEASE-526: --- same problem here; I observe it only on multimodule

[jira] Created: (DOXIA-401) doxia-module-twiki has no syntax for using macros

doxia-module-twiki has no syntax for using macros - Key: DOXIA-401 URL: http://jira.codehaus.org/browse/DOXIA-401 Project: Maven Doxia Issue Type: Bug Components: Module - Twiki

[jira] Created: (MRELEASE-577) release:prepare does not pass argument --settings with current settings.xml to inner maven

release:prepare does not pass argument --settings with current settings.xml to inner maven Key: MRELEASE-577 URL: http://jira.codehaus.org/browse/MRELEASE-577

[jira] Created: (MANTRUN-127) provide more tracking info when a task fails

provide more tracking info when a task fails Key: MANTRUN-127 URL: http://jira.codehaus.org/browse/MANTRUN-127 Project: Maven 2.x Antrun Plugin Issue Type: Improvement Reporter: Petr

[jira] Commented: (DOXIA-68) Adding twiki plugin as build extension makes goal site:site fail.

[ http://jira.codehaus.org/browse/DOXIA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202077#action_202077 ] Petr Kozelka commented on DOXIA-68: --- I wonder if there is a way to make twiki working against

[jira] Created: (MNG-4481) store snapshots in separate local repository

store snapshots in separate local repository Key: MNG-4481 URL: http://jira.codehaus.org/browse/MNG-4481 Project: Maven 2 Issue Type: New Feature Components: Artifacts and Repositories,

[jira] Commented: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent

[ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174620#action_174620 ] Petr Kozelka commented on MRELEASE-317: --- In the meantime I started to use much better

[jira] Created: (MENFORCER-62) requirePluginVesions: avoid checking commandline-invoked mojos

requirePluginVesions: avoid checking commandline-invoked mojos -- Key: MENFORCER-62 URL: http://jira.codehaus.org/browse/MENFORCER-62 Project: Maven 2.x Enforcer Plugin Issue Type:

[jira] Created: (MWAR-181) warSourceExcludes does not work in 2.1-alpha-2

warSourceExcludes does not work in 2.1-alpha-2 -- Key: MWAR-181 URL: http://jira.codehaus.org/browse/MWAR-181 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.1-alpha-2

[jira] Commented: (MRELEASE-394) Support for SCM update after each commit

[ http://jira.codehaus.org/browse/MRELEASE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=156876#action_156876 ] Petr Kozelka commented on MRELEASE-394: --- I just confirm that the same happens to me too,

[jira] Commented: (MSITE-224) [PATCH] please make UTF-8 the default encoding

[ http://jira.codehaus.org/browse/MSITE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129810#action_129810 ] Petr Kozelka commented on MSITE-224: That's true for input encoding. However, for output

[jira] Commented: (MRELEASE-51) release:perform could update the date attribute in the changes.xml

[ http://jira.codehaus.org/browse/MRELEASE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120396 ] Petr Kozelka commented on MRELEASE-51: -- may I suggest that the date be in the xs:dateTime format ? I mean _including_

[jira] Created: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent

release:prepare should fail if any pom depends on SNAPSHOT parent - Key: MRELEASE-317 URL: http://jira.codehaus.org/browse/MRELEASE-317 Project: Maven 2.x Release Plugin Issue

[jira] Commented: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent

[ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119776 ] Petr Kozelka commented on MRELEASE-317: --- More info: the target usecase is that parent pom is released as a separate

[jira] Created: (MAVENUPLOAD-1895) Sync net.sf.buildbox repository

Sync net.sf.buildbox repository --- Key: MAVENUPLOAD-1895 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1895 Project: maven-upload-requests Issue Type: Task Reporter: Petr Kozelka Please

[jira] Updated: (MAVENUPLOAD-1895) Sync net.sf.buildbox repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka updated MAVENUPLOAD-1895: -- Attachment: net.sf.buildbox.sh Sync net.sf.buildbox repository

[jira] Commented: (MRELEASE-154) mvn release:perform does not inherit command line variable

[ http://jira.codehaus.org/browse/MRELEASE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118961 ] Petr Kozelka commented on MRELEASE-154: --- This problem also happens for other commandline arguments, like --settings.

[jira] Commented: (MNG-2917) Ant classpath issue in maven 2.0.6

[ http://jira.codehaus.org/browse/MNG-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106543 ] Petr Kozelka commented on MNG-2917: --- I just want to confirm that this really helped to me too. In particular, adding the

[jira] Created: (MNG-3164) Enable plugin configuration in settings.xml

Enable plugin configuration in settings.xml --- Key: MNG-3164 URL: http://jira.codehaus.org/browse/MNG-3164 Project: Maven 2 Issue Type: New Feature Components: Settings

[jira] Commented: (MWAR-30) I can't build a war-file without a web.xml.

[ http://jira.codehaus.org/browse/MWAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99851 ] Petr Kozelka commented on MWAR-30: -- Also when using war overlays, it makes pretty good sense to create a war without web.xml

[jira] Created: (MWAR-108) parameter archive not respected - no way to influence MANIFEST.MF

parameter archive not respected - no way to influence MANIFEST.MF --- Key: MWAR-108 URL: http://jira.codehaus.org/browse/MWAR-108 Project: Maven 2.x War Plugin Issue Type: Bug

[jira] Closed: (MWAR-108) parameter archive not respected - no way to influence MANIFEST.MF

[ http://jira.codehaus.org/browse/MWAR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka closed MWAR-108. - Resolution: Fixed oops... I actually edited different POM which of course had no impact on observed war :-) In

[jira] Created: (MSITE-226) Missing escaping of ${project.name} for default site descriptor

Missing escaping of ${project.name} for default site descriptor --- Key: MSITE-226 URL: http://jira.codehaus.org/browse/MSITE-226 Project: Maven 2.x Site Plugin Issue Type: Bug

[jira] Commented: (MSITE-226) Missing escaping of ${project.name} for default site descriptor

[ http://jira.codehaus.org/browse/MSITE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92442 ] Petr Kozelka commented on MSITE-226: more useful part of stacktrace: {quote} ... Caused by:

[jira] Closed: (MNG-2922) M2 website: broken section links on pom.html, settings.html and others

[ http://jira.codehaus.org/browse/MNG-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Kozelka closed MNG-2922. - Resolution: Duplicate found similar report in MNG-2808 , closing M2 website: broken section links on pom.html,

[jira] Created: (MNG-2927) [PATCH] please make UTF-8 the default encoding

[PATCH] please make UTF-8 the default encoding -- Key: MNG-2927 URL: http://jira.codehaus.org/browse/MNG-2927 Project: Maven 2 Issue Type: Improvement Components: Sites Reporting

[jira] Created: (MNG-2922) M2 website: broken section links on pom.html, settings.html and others

M2 website: broken section links on pom.html, settings.html and others -- Key: MNG-2922 URL: http://jira.codehaus.org/browse/MNG-2922 Project: Maven 2 Issue Type: Bug

[jira] Commented: (MNG-2922) M2 website: broken section links on pom.html, settings.html and others

[ http://jira.codehaus.org/browse/MNG-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91907 ] Petr Kozelka commented on MNG-2922: --- same issue at http://maven.apache.org/guides/getting-started/index.html M2 website:

[jira] Created: (MRM-311) incorrectly displayed groupId for dependencies

incorrectly displayed groupId for dependencies -- Key: MRM-311 URL: http://jira.codehaus.org/browse/MRM-311 Project: Archiva Issue Type: Bug Components: web application