[jira] Created: (MSHADE-81) Poor error reporting
Poor error reporting Key: MSHADE-81 URL: http://jira.codehaus.org/browse/MSHADE-81 Project: Maven 2.x Shade Plugin Issue Type: Bug Reporter: Pete Muir When using XmlAppendingTransformer, I get this (fairly useless) error message: on line 1: Premature end of file. - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) 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.apache.maven.plugin.MojoExecutionException: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) at org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) at org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) ... 21 more Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) ... 24 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
[jira] Commented: (MSHADE-81) Poor error reporting
[ http://jira.codehaus.org/browse/MSHADE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=224117#action_224117 ] Pete Muir commented on MSHADE-81: - Actually, printing out resource is a good first step, but not enough, we need the name of the inputstream being worked on :-( Poor error reporting Key: MSHADE-81 URL: http://jira.codehaus.org/browse/MSHADE-81 Project: Maven 2.x Shade Plugin Issue Type: Bug Reporter: Pete Muir When using XmlAppendingTransformer, I get this (fairly useless) error message: on line 1: Premature end of file. - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) 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.apache.maven.plugin.MojoExecutionException: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) at org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) at org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) ... 21 more Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) ... 24 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
[jira] Commented: (MSHADE-81) Poor error reporting
[ http://jira.codehaus.org/browse/MSHADE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=224119#action_224119 ] Pete Muir commented on MSHADE-81: - Without changing the API best bet looks like adding some logging for each file that is transformed around DefaultShader:150 Poor error reporting Key: MSHADE-81 URL: http://jira.codehaus.org/browse/MSHADE-81 Project: Maven 2.x Shade Plugin Issue Type: Bug Reporter: Pete Muir When using XmlAppendingTransformer, I get this (fairly useless) error message: on line 1: Premature end of file. - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) 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.apache.maven.plugin.MojoExecutionException: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) at org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) at org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) ... 21 more Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) ... 24 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
[jira] Commented: (MNG-4530) Add alias feature for moved/renamed dependencies
[
http://jira.codehaus.org/browse/MNG-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=208109#action_208109
]
Pete Muir commented on MNG-4530:
Project Jigsaw calls this provides
The clause provides P indicates that a dependency on module P by some other
module may be satisfied by module M.
Add alias feature for moved/renamed dependencies
Key: MNG-4530
URL: http://jira.codehaus.org/browse/MNG-4530
Project: Maven 2 3
Issue Type: New Feature
Components: Dependencies
Reporter: Paul Gier
There should be an option to link multiple dependency groupId/artifactIds so
that the dependency resolver knows they refer to the same artifact. There
are many dependencies that get renamed to a new groupId/artifactId. This
causes problems because many times the old groupId/artifactId is still pulled
in transitively from other projects. Currently, the only way to do this is
with a tedious combination of excludes tags and enforcer rules. It would
be much simpler if there were a mechanism in the pom and dependency manager
to treat two IDs as the same dependency.
{code:xml}
dependency
groupIdorg.mycomp/groupId
artifactIdlog4j/groupId
version1.0/version
aliases
alias
groupIdlog4j/groupId
artifactIdlog4j/artifactId
alias
/aliases
dependency
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2686) Sun's el-api 2.2
Sun's el-api 2.2 Key: MAVENUPLOAD-2686 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2686 Project: Maven Upload Requests Issue Type: Wish Reporter: Pete Muir Central only has 1.0 release, this is the 2.2 release. License is either GPL+classpath extension or CDDL -- 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: (MANTTASKS-98) NPE if user settings file doesn't exist
NPE if user settings file doesn't exist --- Key: MANTTASKS-98 URL: http://jira.codehaus.org/browse/MANTTASKS-98 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: POM Integration Affects Versions: 2.0.8 Environment: 2.0.08-SNAPSHOT from 18-Nov-2007 Reporter: Pete Muir When running artifact:install file=/path/to/file.jar pom file=/path/to/pom.xml / remoteRepository refId=repo / /artifact:install you get, if ~/.m2/settings.xml is missing, java.lang.NullPointerException at org.apache.maven.settings.SettingsUtils.merge(SettingsUtils.java:110) at org.apache.maven.artifact.ant.AbstractArtifactTask.initSettings(Abstr actArtifactTask.java:264) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractAr tifactTask.java:643) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) -- 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: (MANTTASKS-98) NPE if user settings file doesn't exist
[ http://jira.codehaus.org/browse/MANTTASKS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated MANTTASKS-98: --- Attachment: MANTTASKS-98.patch Patch to fix NPE if user settings file doesn't exist --- Key: MANTTASKS-98 URL: http://jira.codehaus.org/browse/MANTTASKS-98 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: POM Integration Affects Versions: 2.0.8 Environment: 2.0.08-SNAPSHOT from 18-Nov-2007 Reporter: Pete Muir Attachments: MANTTASKS-98.patch When running artifact:install file=/path/to/file.jar pom file=/path/to/pom.xml / remoteRepository refId=repo / /artifact:install you get, if ~/.m2/settings.xml is missing, java.lang.NullPointerException at org.apache.maven.settings.SettingsUtils.merge(SettingsUtils.java:110) at org.apache.maven.artifact.ant.AbstractArtifactTask.initSettings(Abstr actArtifactTask.java:264) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractAr tifactTask.java:643) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) -- 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: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[
http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109690
]
Pete Muir commented on MANTTASKS-23:
Also, the patch breaks support for attached files (they are deployed as
separate artifacts with an updated buildNumber)
antlib:deploy doesn't set correct snapshot version
--
Key: MANTTASKS-23
URL: http://jira.codehaus.org/browse/MANTTASKS-23
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: deploy task
Affects Versions: 2.0.4, 2.0.6, 2.0.7
Environment: win xp, mvn 2.0.2, ant 1.6.5
Reporter: Michal Stochmialek
Fix For: 2.0.8
Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff,
maven-artifact-ant-MNG-2060.patch
I'm trying to deploy to maven remote repository jars produced by
ant. Those jars are in snapshot version.
Whole deployment process is going properly, but something is wrong with names
of deployed files.
When I'm deploying artifacts using normal 'maven deploy', SNAPSHOT in
the name is replaced by the current timestamp and the snapshot number (for
instance: 20060105.123437-3).
But when I'm deploying with antlib, the name isn't changed. SNAPSHOT is
still in the name. And when I deploy snapshot again, the old one is
replaced by the new one (which also different from behavior of normal 'mvn
deploy').
The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is
missing:
?xml version=1.0 encoding=UTF-8?metadata
groupIdfoo/groupId
artifactIdfoo-jar1/artifactId
version1.0-SNAPSHOT/version
versioning
snapshot
buildNumber4/buildNumber
/snapshot
lastUpdated20060209111228/lastUpdated
/versioning
/metadata
Here's an fragment of my ant script:
target name=maven-poms
artifact:pom id=pom.jar1-jar file=maven/pom-jar1-jar.xml /
artifact:pom id=pom.jar2-jar file=maven/pom-jar2-jar.xml /
artifact:pom id=pom.jar3-jar file=maven/pom-jar3--jar.xml /
/target
target name=maven-install-local
depends=maven-poms,generate-jars
artifact:install file=${build.dir}/jar1.jar
pom refid=pom.jar1-jar/
/artifact:install
artifact:install file=${build.dir}/jar2.jar
pom refid=pom.jar2-jar/
/artifact:install
artifact:install file=${build.dir}/jar3.jar
pom refid=pom.jar3-jar/
/artifact:install
/target
target name=maven-deploy-remote depends=maven-install-local
artifact:install-provider artifactId=wagon-ssh version=1.0-alpha-5/
artifact:deploy file=${build.dir}/jar1.jar
pom refid=pom.jar1-jar/
/artifact:deploy
artifact:deploy file=${build.dir}/jar2.jar
pom refid=pom.jar2-jar/
/artifact:deploy
artifact:deploy file=${build.dir}/jar3.jar
pom refid=pom.jar3-jar/
/artifact:deploy
/target
The artifacts poms are in separate files which contain only artifactId,
groupId,
version, dependencies and remote repository url.
I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my
repository
url is specified correctly. And it works. Jar is deployed to remote
repository with
correct version.
--
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: (MANTTASKS-89) Deploy ignores settings.xml for remoteRepository declared in ant build.xml
[ http://jira.codehaus.org/browse/MANTTASKS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109119 ] Pete Muir commented on MANTTASKS-89: This requires MANTTASKS-85 to be fixed. Deploy ignores settings.xml for remoteRepository declared in ant build.xml -- Key: MANTTASKS-89 URL: http://jira.codehaus.org/browse/MANTTASKS-89 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: deploy task Affects Versions: 2.0.7 Reporter: Pete Muir Given artifact:deploy uniqueVersion=true pom file=my.pom / remoteRepository refid=my.repository / /artifact:deploy Any authentication settings declared in settings.xml are ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTTASKS-89) Deploy ignores settings.xml for remoteRepository declared in ant build.xml
[ http://jira.codehaus.org/browse/MANTTASKS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed MANTTASKS-89. -- Resolution: Cannot Reproduce Sorry, this is the result of applying multiple patches. Deploy ignores settings.xml for remoteRepository declared in ant build.xml -- Key: MANTTASKS-89 URL: http://jira.codehaus.org/browse/MANTTASKS-89 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: deploy task Affects Versions: 2.0.7 Reporter: Pete Muir Given artifact:deploy uniqueVersion=true pom file=my.pom / remoteRepository refid=my.repository / /artifact:deploy Any authentication settings declared in settings.xml are ignored. -- 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: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[
http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109121
]
Pete Muir commented on MANTTASKS-23:
When used in MANTTASKS-85, settings.xml is not used for deploy - a call to
updateRepositoryWithSettings(repository); is needed in
createDeploymentArtifactRepository.
antlib:deploy doesn't set correct snapshot version
--
Key: MANTTASKS-23
URL: http://jira.codehaus.org/browse/MANTTASKS-23
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: deploy task
Affects Versions: 2.0.4, 2.0.6, 2.0.7
Environment: win xp, mvn 2.0.2, ant 1.6.5
Reporter: Michal Stochmialek
Fix For: 2.0.8
Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff,
maven-artifact-ant-MNG-2060.patch
I'm trying to deploy to maven remote repository jars produced by
ant. Those jars are in snapshot version.
Whole deployment process is going properly, but something is wrong with names
of deployed files.
When I'm deploying artifacts using normal 'maven deploy', SNAPSHOT in
the name is replaced by the current timestamp and the snapshot number (for
instance: 20060105.123437-3).
But when I'm deploying with antlib, the name isn't changed. SNAPSHOT is
still in the name. And when I deploy snapshot again, the old one is
replaced by the new one (which also different from behavior of normal 'mvn
deploy').
The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is
missing:
?xml version=1.0 encoding=UTF-8?metadata
groupIdfoo/groupId
artifactIdfoo-jar1/artifactId
version1.0-SNAPSHOT/version
versioning
snapshot
buildNumber4/buildNumber
/snapshot
lastUpdated20060209111228/lastUpdated
/versioning
/metadata
Here's an fragment of my ant script:
target name=maven-poms
artifact:pom id=pom.jar1-jar file=maven/pom-jar1-jar.xml /
artifact:pom id=pom.jar2-jar file=maven/pom-jar2-jar.xml /
artifact:pom id=pom.jar3-jar file=maven/pom-jar3--jar.xml /
/target
target name=maven-install-local
depends=maven-poms,generate-jars
artifact:install file=${build.dir}/jar1.jar
pom refid=pom.jar1-jar/
/artifact:install
artifact:install file=${build.dir}/jar2.jar
pom refid=pom.jar2-jar/
/artifact:install
artifact:install file=${build.dir}/jar3.jar
pom refid=pom.jar3-jar/
/artifact:install
/target
target name=maven-deploy-remote depends=maven-install-local
artifact:install-provider artifactId=wagon-ssh version=1.0-alpha-5/
artifact:deploy file=${build.dir}/jar1.jar
pom refid=pom.jar1-jar/
/artifact:deploy
artifact:deploy file=${build.dir}/jar2.jar
pom refid=pom.jar2-jar/
/artifact:deploy
artifact:deploy file=${build.dir}/jar3.jar
pom refid=pom.jar3-jar/
/artifact:deploy
/target
The artifacts poms are in separate files which contain only artifactId,
groupId,
version, dependencies and remote repository url.
I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my
repository
url is specified correctly. And it works. Jar is deployed to remote
repository with
correct version.
--
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: (MANTTASKS-35) Support profiles in pom type
[ http://jira.codehaus.org/browse/MANTTASKS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated MANTTASKS-35: --- Attachment: MANTTASKS-35.patch Here is a patch. Use it like: pom file=pom.xml activeProfile id=foo / activeProfile id=bar if=some.property.is.set / /pom Support profiles in pom type Key: MANTTASKS-35 URL: http://jira.codehaus.org/browse/MANTTASKS-35 Project: Maven 2.x Ant Tasks Issue Type: Improvement Components: POM Integration Reporter: Mark Hobson Attachments: MANTTASKS-35.patch Need to be able to pass in a list of profiles to activate in pom type - there's currently a TODO in Pom.java for this. -- 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
