[jira] (MWAR-286) Please make test-jar also run for war packages
[ https://jira.codehaus.org/browse/MWAR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308205#comment-308205 ] Geoffrey De Smet commented on MWAR-286: --- @Robert that would work: it fixes the problem of having to overwrite the jar plugin on every war module just to deploy the test-jar. But personally, I believe that if the jar plugin is configured to generate a test-jar, it should do that for war modules too. Please make test-jar also run for war packages Key: MWAR-286 URL: https://jira.codehaus.org/browse/MWAR-286 Project: Maven 2.x WAR Plugin Issue Type: Wish Affects Versions: 2.2 Reporter: Marco rietveld Priority: Minor If you configure the jar plugin to also run the test-jar goal, it will only run that if the package type in the pom of the project is jar. However, in the case of wars it's would also be handy to be able to make the test-jars (by simply changing the configuration in one mother pom). We realize that this is an edge-case. However, we (drools/jbpm) work with a project that has _lots_ or submodules including a couple war submodules. Being able to simply have all war submodules generate test-jars without having to modify each individual war submodule's pom.xml would be nice. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (ARCHETYPE-420) curly brackets lost when filtered=true
Dominique Jean-Prost created ARCHETYPE-420: -- Summary: curly brackets lost when filtered=true Key: ARCHETYPE-420 URL: https://jira.codehaus.org/browse/ARCHETYPE-420 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.2 Reporter: Dominique Jean-Prost Attachments: archetype sources.zip, generated_project.zip When using filtered=true on a fileset, files generated lose curly brackets. Please find as an attachment : - the source of the archetype. you will see within the settings for the fileset - a generated project using this artifact -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308223#comment-308223
]
Cedric Meury commented on MSOURCES-62:
--
I have the same problem with Apache Maven 3.0.3 (r1075438; 2011-02-28
18:31:09+0100) (running in Jenkins 1.447.2)
An API incompatibility was encountered.
---
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Priority: Blocker
Attachments: MSOURCES-62.zip
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (ARCHETYPE-420) curly brackets lost when filtered=true
[
https://jira.codehaus.org/browse/ARCHETYPE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308224#comment-308224
]
Dominique Jean-Prost commented on ARCHETYPE-420:
In generated project, you will see that template-application.xhtml contains
this :
{code:xml}
ui:define name=zone-i18n
sfx_t:messageSource var=i18n keyPrefix=com.test. /
/ui:define
ui:define name=zone-posts-techniques
input type=hidden name=_flowExecutionKey
value=#flowExecutionKey /
/ui:define
{code}
instead of
{code:xml}
ui:define name=zone-i18n
sfx_t:messageSource var=i18n keyPrefix=com.test. /
/ui:define
ui:define name=zone-posts-techniques
input type=hidden name=_flowExecutionKey
value=#{flowExecutionKey} /
/ui:define
{code}
curly brackets lost when filtered=true
--
Key: ARCHETYPE-420
URL: https://jira.codehaus.org/browse/ARCHETYPE-420
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 2.2
Reporter: Dominique Jean-Prost
Attachments: archetype sources.zip, generated_project.zip
When using filtered=true on a fileset, files generated lose curly brackets.
Please find as an attachment :
- the source of the archetype. you will see within the settings for the
fileset
- a generated project using this artifact
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308236#comment-308236
]
Olivier Lamy commented on MSOURCES-62:
--
due to
https://github.com/sonatype/plexus-archiver/commit/838ab2e61ab6540631abe8a792292ea672e97a85#src/main/java/org/codehaus/plexus/archiver/jar/Manifest.java
An API incompatibility was encountered.
---
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Priority: Blocker
Attachments: MSOURCES-62.zip
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned MSOURCES-62:
Assignee: Olivier Lamy
An API incompatibility was encountered.
---
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Assignee: Olivier Lamy
Priority: Blocker
Attachments: MSOURCES-62.zip
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-241) Use last plexus-archiver version
Olivier Lamy created MSHARED-241: Summary: Use last plexus-archiver version Key: MSHARED-241 URL: https://jira.codehaus.org/browse/MSHARED-241 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Olivier Lamy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-241) Use last plexus-archiver version
[ https://jira.codehaus.org/browse/MSHARED-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSHARED-241. Resolution: Fixed Fix Version/s: maven-archiver-2.6 Assignee: Olivier Lamy fixed. Use last plexus-archiver version Key: MSHARED-241 URL: https://jira.codehaus.org/browse/MSHARED-241 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: maven-archiver-2.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-62) An API incompatibility was encountered.
[
https://jira.codehaus.org/browse/MSOURCES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MSOURCES-62.
Resolution: Fixed
Fix Version/s: 2.3
fixed.
Thanks for the it test!
An API incompatibility was encountered.
---
Key: MSOURCES-62
URL: https://jira.codehaus.org/browse/MSOURCES-62
Project: Maven 2.x Source Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Christian Schulte
Assignee: Olivier Lamy
Priority: Blocker
Fix For: 2.3
Attachments: MSOURCES-62.zip
The plugin fails when using custom 'manifestEntries' throwing the following
exception:
{code}
[...]
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.archiver.jar.Manifest.getMainSection()Lorg/codehaus/plexus/archiver/jar/Manifest$Section;
at
org.apache.maven.archiver.MavenArchiver.getManifest(MavenArchiver.java:102)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:513)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:288)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:240)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-773) surefire forked processes not always killed after timeout
[
https://jira.codehaus.org/browse/SUREFIRE-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308253#comment-308253
]
Shahaf Abileah commented on SUREFIRE-773:
-
I also see this. I'm using surefire 2.10. I'm on Mac.
In my case, the maven build doesn't complete -- it's hung. I'm not sure if
that's related to the orphaned booter processes, or if that's a separate issue.
For what it's worth, the build does complete consistently if I use
parallelnone/parallel so I suspect it's related to the parallelization.
surefire forked processes not always killed after timeout
-
Key: SUREFIRE-773
URL: https://jira.codehaus.org/browse/SUREFIRE-773
Project: Maven Surefire
Issue Type: Bug
Components: process forking
Affects Versions: 2.8
Environment: 64 bit RHEL 5.5 , 64-bit Java 1.6.0_23
Reporter: David Biesack
Our forked JUnit/surefire processes are not always stopping correctly when
timing out within a Maven build
(running inside our Jenkins CI server, ver 1.425).
The maven build finishes and Jenkins shows a failed/unstable build.
These running processes cause problems later, because the tests may be
holding a resource like a port, and subsequent rebuilds fail because the
tests fail.
For example, even though no Maven builds are currently running, ps shows
about a dozen Java processes running,
with commands such as:
{noformat}
/usr/local/java-1.6_23/jre/bin/java -Xms1g -Xmx5g
-Djava.library.path=/u/jenkinsci/.hudson/jobs/rtolap.jtt.tests/workspace/target/lib
\
-jar
/u/jenkinsci/.hudson/jobs/rtolap.jtt.tests/workspace/target/surefire/surefirebooter1374560535780866887.jar
\
/u/jenkinsci/.hudson/jobs/rtolap.jtt.tests/workspace/target/surefire/surefire65313...
/usr/local/java-1.6_23/jre/bin/java -Xmx2g -Xms1g
-Djava.library.path=/u/jenkinsci/.hudson/jobs/rtolap/workspace/target/lib \
-jar
/u/jenkinsci/.hudson/jobs/rtolap/workspace/target/surefire/surefirebooter6814971258434039335.jar
\
/u/jenkinsci/.hudson/jobs/rtolap/workspace/target/surefire/surefire5806103969370259371tmp
/u/jenkinsci/...
...
{noformat}
We have our Maven surefire preferences set to fork the tests (via a parent
pom)
{code:xml|title=pom.xml excerpt}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.8/version
configuration
forkModeonce/forkMode
forkedProcessTimeoutInSeconds720/forkedProcessTimeoutInSeconds
/configuration
/plugin
{code}
I suspect the timeout is the problem - i.e. perhaps the test is timing out
and the attempt to kill the forked process
fails, leaving it running.
Has anyone seen something similar and/or know how to fix this so that
surefire *really* kills the process?
When this happens, doing
kill processid
(logged in as the process owner) usually does not work, but
kill -9 processid
does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308263#comment-308263 ] Jerry Cwiklik commented on MCHANGES-285: Any idea when the 2.8 releases? The problem fixed here is a blocker for Apache UIMA-AS release. Any chance of getting this released on a quick turn-around? Thanks. SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Fix For: 2.8 Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308264#comment-308264 ] Gary Gregory commented on MCHANGES-285: --- FWIW: This is also breaking the JIRA report for the Apache Commons Codec 1.7 release under VOTE now, but we are proceeding regardless. SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Fix For: 2.8 Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308274#comment-308274 ] Dennis Lundberg commented on MCHANGES-285: -- Yes, I'm working on getting the 2.8 release out. SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Fix For: 2.8 Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at
[jira] (MPLUGIN-225) Make MojoExecution available as Component
Robert Scholte created MPLUGIN-225:
--
Summary: Make MojoExecution available as Component
Key: MPLUGIN-225
URL: https://jira.codehaus.org/browse/MPLUGIN-225
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-annotations
Affects Versions: 3.1
Reporter: Robert Scholte
Priority: Minor
Just like {{MavenProject}} it should be possible to define the
{{MojoExecution}} as:
{code}
@Component
private MojoExecution mojoExecution ;
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308276#comment-308276 ] Jerry Cwiklik commented on MCHANGES-285: Thanks for the update. Do you think you are days or weeks away from releasing 2.8? SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Fix For: 2.8 Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308278#comment-308278 ] Dennis Lundberg commented on MCHANGES-285: -- I've just started the VOTE thread on dev@maven.a.o. If all goes well the release is ~72 hours away. Please join us on the mailing list and cast your vote, if you have the possibility to test the release. SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Fix For: 2.8 Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at
[jira] (MWAR-286) Please make test-jar also run for war packages
[
https://jira.codehaus.org/browse/MWAR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308279#comment-308279
]
Robert Scholte commented on MWAR-286:
-
I understand your point, but it is weird to add the maven-jar-plugin when the
packaging-type is {{war}}. I expect this can be fixed with a small number of
lines.
The result will be: one or two extra tag in the maven-war-plugin configuration
instead of the maven-jar-plugin + configuration + execution.
Please make test-jar also run for war packages
Key: MWAR-286
URL: https://jira.codehaus.org/browse/MWAR-286
Project: Maven 2.x WAR Plugin
Issue Type: Wish
Affects Versions: 2.2
Reporter: Marco rietveld
Priority: Minor
If you configure the jar plugin to also run the test-jar goal, it will only
run that if the package type in the pom of the project is jar.
However, in the case of wars it's would also be handy to be able to make the
test-jars (by simply changing the configuration in one mother pom).
We realize that this is an edge-case. However, we (drools/jbpm) work with a
project that has _lots_ or submodules including a couple war submodules.
Being able to simply have all war submodules generate test-jars without
having to modify each individual war submodule's pom.xml would be nice.
Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
Olivier Lamy created SCM-694: Summary: git checkin command doesn't work with renamed files Key: SCM-694 URL: https://jira.codehaus.org/browse/SCM-694 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-git Affects Versions: 1.8 Reporter: Olivier Lamy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
[
https://jira.codehaus.org/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated SCM-694:
-
Description:
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
git checkin command doesn't work with renamed files
---
Key: SCM-694
URL: https://jira.codehaus.org/browse/SCM-694
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-git
Affects Versions: 1.8
Reporter: Olivier Lamy
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
[
https://jira.codehaus.org/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated SCM-694:
-
Fix Version/s: 1.9
git checkin command doesn't work with renamed files
---
Key: SCM-694
URL: https://jira.codehaus.org/browse/SCM-694
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-git
Affects Versions: 1.8
Reporter: Olivier Lamy
Fix For: 1.9
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
[
https://jira.codehaus.org/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308289#comment-308289
]
Frédéric Camblor commented on SCM-694:
--
Provided [pull request|https://github.com/apache/maven-scm/pull/3] with test
and patch.
git checkin command doesn't work with renamed files
---
Key: SCM-694
URL: https://jira.codehaus.org/browse/SCM-694
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-git
Affects Versions: 1.8
Reporter: Olivier Lamy
Fix For: 1.9
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
[
https://jira.codehaus.org/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned SCM-694:
Assignee: Olivier Lamy
git checkin command doesn't work with renamed files
---
Key: SCM-694
URL: https://jira.codehaus.org/browse/SCM-694
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-git
Affects Versions: 1.8
Reporter: Olivier Lamy
Assignee: Olivier Lamy
Fix For: 1.9
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-694) git checkin command doesn't work with renamed files
[
https://jira.codehaus.org/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed SCM-694.
Resolution: Fixed
applied.
Thanks!
git checkin command doesn't work with renamed files
---
Key: SCM-694
URL: https://jira.codehaus.org/browse/SCM-694
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-git
Affects Versions: 1.8
Reporter: Olivier Lamy
Assignee: Olivier Lamy
Fix For: 1.9
rename a file then you get
{code}
# On branch master
# Changes to be committed:
# (use git reset HEAD file... to unstage)
#
# renamed:foo/bar/wine.xml - foo/newbar/wine.xml
#
{code}
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
