[jira] Commented: (MRELEASE-326) Doens't resolve multiproject dependencies properly
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133499#action_133499 ] Ian Rowlands commented on MRELEASE-326: --- Still a problem with 2.0.8 - this means unless you have the dependencies done in a certain way, releases cannot be automated. Doens't resolve multiproject dependencies properly --- Key: MRELEASE-326 URL: http://jira.codehaus.org/browse/MRELEASE-326 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-7 Environment: Windows, JDK 1.6, Maven 2.08 Reporter: Kuno Baeriswyl Attachments: Stacktrace_release-plugin.txt I'd try to make a release:prepare from a multiproject: A (Multiproject POM) B (Core Interfaces) C (Component) D (Core Impl) E (Standalone Client) F (EJB) G (Client) A is the parent project and contains the other project from B to G. Following dependencies are defined : G - F - D - B - A However, when it comes to build the Artifact G, the release plugin aborts, because of missing Artifact F. But it's part of the Multiproject and was just build before. The release plugin checks the remote repository for an existing version. Which is non-sense, since I'm actually try to buld it right now... Since the release plugin has already changed the pom from Snapshot to stable version labels. I can now do mvn install and the missing Artefact will be installed. And the second run of mvn release:prepare will succeed! Though, I don't like this workaround and hope this can be fixed. Thanks Kuno -- 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: (MPXDOC-206) Including DTD breaks xdoc
[ http://jira.codehaus.org/browse/MPXDOC-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPXDOC-206. Assignee: Lukas Theussl Resolution: Cannot Reproduce Including DTD breaks xdoc -- Key: MPXDOC-206 URL: http://jira.codehaus.org/browse/MPXDOC-206 Project: Maven 1.x XDoc Plugin Issue Type: Bug Affects Versions: 1.10.1 Environment: WindowsXP SP2 x86, JDK6 build 1.6.0_05-b13 Reporter: Gregor B. Rosenauer Assignee: Lukas Theussl Priority: Minor Attachments: error-report.txt When including the XDoc-DTD as mentioned in issue MPXDOC-192 site generation fails with a Jelly-Exception. I cannot say if this is an issue with the xdoc-plugin or with jelly. My document starts with ?xml version=1.0 encoding=UTF-8? !DOCTYPE document PUBLIC -//Apache Software Foundation//DTD XDOC 1.0//EN http://maven.apache.org/dtd/xdoc_1_0.dtd; When invoking the goal xdoc:generate-from-pom (called through a custom goal ta30:doku) I get a Jelly-Exception (full report attached): Caused by: org.apache.commons.jelly.JellyTagException: file:C:/Dokumente und Einstellungen/Orth/.maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources/sitemap.jsl:84:51: x:parse Connection timed out: connect Nested exception: Connection t imed out: connect at org.apache.commons.jelly.tags.xml.ParseTagSupport.parse(ParseTagSuppo rt.java:186) at org.apache.commons.jelly.tags.xml.ParseTag.getXmlDocument(ParseTag.ja va:106) at org.apache.commons.jelly.tags.xml.ParseTag.doTag(ParseTag.java:55) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at org.apache.commons.jelly.tags.util.AvailableTag.doTag(AvailableTag.ja va:68) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java: 160) at org.dom4j.rule.Mode.fireRule(Mode.java:59) at org.dom4j.rule.Stylesheet.applyTemplates(Stylesheet.java:185) at org.dom4j.rule.Stylesheet.applyTemplates(Stylesheet.java:159) at org.apache.commons.jelly.tags.jsl.ApplyTemplatesTag.doTag(ApplyTempla tesTag.java:67) ... 112 more Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exc eption: Connection timed out: connect at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at org.apache.commons.jelly.tags.xml.ParseTagSupport.parse(ParseTagSuppo rt.java:168) ... 126 more Leaving out the DTD fixes the issue, but then I cannot edit the xdoc-file in an XML-editor like the excellent visual XMLmind-editor (with xdoc-type-plugin). -- 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: (NMAVEN-121) Have a configurable root namespace for VB assembly
Have a configurable root namespace for VB assembly -- Key: NMAVEN-121 URL: http://jira.codehaus.org/browse/NMAVEN-121 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas Build using NMaven the does not include the root namespace. This is exclusive to VB, where the name space can be specified in the root name space property. -- 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: (MNG-3564) alternative and higher level configuration option to exlusions
alternative and higher level configuration option to exlusions Key: MNG-3564 URL: http://jira.codehaus.org/browse/MNG-3564 Project: Maven 2 Issue Type: New Feature Components: General Affects Versions: 2.0.9 Reporter: manuel aldana maven provides scope (test, runtime etc.) to filter certain dependencies. never the less sometimes it is quite helpful to have a another configuration option, where you decide what to include transitively or what kind of dependency-set is relevant to your current project. using exclusions configuration to accomplish this is often very verbose, non-standard and is difficult to read (it is often not obvious what is meant with all these exclusions). as an example ivy includes such configuration meta-info approach (see http://ant.apache.org/ivy/m2comparison.html). this feature would be nice because when building releases one is more flexible. -- 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: (NMAVEN-121) Have a configurable root namespace for VB assembly
[ http://jira.codehaus.org/browse/NMAVEN-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan ancajas updated NMAVEN-121: --- Attachment: NMAVEN-121.patch to set the root namespace specify the rootNameSpace in the maven-compile-plugin configuration: .. .. plugins plugin groupIdorg.apache.maven.dotnet.plugins/groupId artifactIdmaven-compile-plugin/artifactId extensionstrue/extensions configuration languageVB/language rootNameSpacemy.company/rootNameSpace /configuration /plugin plugins .. .. Have a configurable root namespace for VB assembly -- Key: NMAVEN-121 URL: http://jira.codehaus.org/browse/NMAVEN-121 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas Attachments: NMAVEN-121.patch Build using NMaven the does not include the root namespace. This is exclusive to VB, where the name space can be specified in the root name space property. -- 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: (MNG-3565) Maven shouldn't error if a module appears twice in the reactor
Maven shouldn't error if a module appears twice in the reactor -- Key: MNG-3565 URL: http://jira.codehaus.org/browse/MNG-3565 Project: Maven 2 Issue Type: Improvement Components: Bootstrap Build Affects Versions: 2.0.9 Reporter: Ittay Dror parent \-child1 \-child2 \-- many more modules... parent contains child1 and child2 modules child1/pom.xm contains 'module../child2/module' now if i cd into child1 and build, child2 is built before it. good. but if i run from the top directory i get: Project '..:child2' is duplicated in the reactor Note: the reason not to always run from top is that there are many modules, which are not interrelated, so developer shouldn't wait while another set of modules (maintained by another build) is built (even if nothing gets done, it still takes time). Why not just remove duplicates before sorting? -- 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: (DOXIA-185) Add encoding support
[ http://jira.codehaus.org/browse/DOXIA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133531#action_133531 ] Lukas Theussl commented on DOXIA-185: - The encoding of source/target files is set in the Reader/Writer of a Parser/Sink, ie outside of doxia.So I don't understand why this should be necessary or useful, or am I missing something? Add encoding support Key: DOXIA-185 URL: http://jira.codehaus.org/browse/DOXIA-185 Project: Maven Doxia Issue Type: Improvement Components: Sink API Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton -- 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: (DOXIA-185) Add encoding support
[ http://jira.codehaus.org/browse/DOXIA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133533#action_133533 ] Vincent Siveton commented on DOXIA-185: --- Actually yes it is but do we want to add character encoding directly in Doxia files like HTML does [1]? [1] http://www.w3.org/TR/html4/types.html Add encoding support Key: DOXIA-185 URL: http://jira.codehaus.org/browse/DOXIA-185 Project: Maven Doxia Issue Type: Improvement Components: Sink API Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton -- 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: (MSITE-321) multi module, hierarichal project broken link in site and site:stage
multi module, hierarichal project broken link in site and site:stage Key: MSITE-321 URL: http://jira.codehaus.org/browse/MSITE-321 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module, relative links Affects Versions: 2.0-beta-6 Environment: Mac OS X / maven 2.0.7 Reporter: jens breitenstein Attachments: maven-site-plugin-error.zip when creating the documentation using site or site:stage all module links are broken. Using the URL element only the first level can be fixed. Please see attached sample ZIP containing a multi module project consisting of three pom's which demonstrate the error. Maybe this is closely related to MSITE-316? -- 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: (MNG-3566) Phase prepare-package not available
Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Joerg Schaible The default lifecycle contains a phase prepare-package (according to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html). This is not available for M209, the component.xml in maven-core misses this phase for the 2.0.x series. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3566) Phase prepare-package not available
[ http://jira.codehaus.org/browse/MNG-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133545#action_133545 ] Olivier Lamy commented on MNG-3566: --- +1 on fixing it on the 2.0.x branch ! Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Joerg Schaible The default lifecycle contains a phase prepare-package (according to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html). This is not available for M209, the component.xml in maven-core misses this phase for the 2.0.x series. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3566) Phase prepare-package not available
[ http://jira.codehaus.org/browse/MNG-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133546#action_133546 ] Wendy Smoak commented on MNG-3566: -- Why isn't it named pre-package to match pre-integration-test and pre-site ? Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Joerg Schaible The default lifecycle contains a phase prepare-package (according to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html). This is not available for M209, the component.xml in maven-core misses this phase for the 2.0.x series. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3566) Phase prepare-package not available
[ http://jira.codehaus.org/browse/MNG-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133548#action_133548 ] Benjamin Bentmann commented on MNG-3566: bq. This is not available for M209 Are you aware of the description for this phase, which says: bq. perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package. (*Maven 2.1 and above*) Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Joerg Schaible The default lifecycle contains a phase prepare-package (according to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html). This is not available for M209, the component.xml in maven-core misses this phase for the 2.0.x series. -- 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: (MASSEMBLY-324) DependencySet scope runtime includes jars that are scope provided
[ http://jira.codehaus.org/browse/MASSEMBLY-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133550#action_133550 ] Stephane Gamble commented on MASSEMBLY-324: --- Hi, I was experiencing the same issue. One of my project's dependencies had its scope set to provided in the pom file but was taken by the assembly despite the runtime scope parameter. I changed the output name mapping so that the scope would be part of the dependency file name and it turned out to be considered as a compile dependency. In fact it was just brought as a transitive dependency with a compile scope by another direct dependency. The funny thing is that when I ran the dependency:tree task, I found out that this artifact appeared only once in the dependency tree, with the following information : +- groupId:artifactId:jar:version:provided (scope not updated to compile) It was not mentionned as part of the dependencies of the artifact bringing it with the compile scope. I am not too sure about this scope not updated to compile thing. The phenomena is the same with 2.2-beta-1 but not with 2.1. With 2.1, this dependency was actually considered provided and therefore skipped in the assembly. Maybe you were used to 2.1's behaviour ? The backward compatibility may be missing on this specific point ? You may have done this check already, but make sure there is not another dependency messing up with a compile or runtime scope. Check the dependencies scope directly in the pom files of your local repository as the dependency:tree task may not be 100% reliable for the witch hunt. In my case, the provided dependencies are correctly excluded with the scoperuntime/scope parameter (using assembly:2.2-beta-2, maven-2.0.8 Windows XP). Good luck ! DependencySet scope runtime includes jars that are scope provided - Key: MASSEMBLY-324 URL: http://jira.codehaus.org/browse/MASSEMBLY-324 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Reporter: Michael Mattox I use some jars in provided scope: dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.5/version scopeprovided/scope /dependency in my assembly, I specify scope as runtime: dependencySet outputDirectoryWEB-INF/lib/outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet Yet I still find the servlet-api-2.5.jar in my WAR. SInce the servlet-api is scope provided, it should be provided by the container and not included in the WAR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3566) Phase prepare-package not available
[ http://jira.codehaus.org/browse/MNG-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133552#action_133552 ] Joerg Schaible commented on MNG-3566: - Even following all pointers I found no reason why this phase could/should not be available in M2.0.x. Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Joerg Schaible The default lifecycle contains a phase prepare-package (according to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html). This is not available for M209, the component.xml in maven-core misses this phase for the 2.0.x series. -- 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: (MRELEASE-273) Regression: NullPointerException at end of standalone release:perform
[
http://jira.codehaus.org/browse/MRELEASE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133560#action_133560
]
Kai Grabfelder commented on MRELEASE-273:
-
I think this only happens when you run mvn release:perform
-DconnectionUrl=scm:svn:. in a directory without a pom
Regression: NullPointerException at end of standalone release:perform
---
Key: MRELEASE-273
URL: http://jira.codehaus.org/browse/MRELEASE-273
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-6
Environment: Maven 2.0.7, maven-release-plugin 2.0-alpha-6
Reporter: Max Bowsher
Priority: Blocker
Attachments: release.bug
I executed mvn release:perform -DconnectionUrl=scm:svn:... The actual
performing succeeded, but then the plugin failed with a NullPointerException
- it seems that the plugin attempts to unconditionally run code analogous to
mvn release:clean, but this is inappropriate because release:perform is not
supposed to require a project to be able to run.
Output:
{noformat}
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Thu Aug 02 12:53:49 BST 2007
[INFO] Final Memory: 13M/23M
[INFO]
[INFO] Cleaning up after release...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[DEBUG] Trace
java.lang.NullPointerException
at
org.apache.maven.shared.release.util.ReleaseUtil.getReleasePom(ReleaseUtil.java:73)
at
org.apache.maven.shared.release.util.ReleaseUtil.getStandardPom(ReleaseUtil.java:61)
at
org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.getPomBackup(AbstractBackupPomsPhase.java:37)
at
org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.deletePomBackup(AbstractBackupPomsPhase.java:51)
at
org.apache.maven.shared.release.phase.CreateBackupPomsPhase.clean(CreateBackupPomsPhase.java:70)
at
org.apache.maven.shared.release.DefaultReleaseManager.clean(DefaultReleaseManager.java:427)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:324)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:267)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:260)
at
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 39 seconds
[INFO] Finished at: Thu Aug 02 12:53:49 BST 2007
[INFO] Final Memory: 4M/8M
[INFO]
[jira] Commented: (MRELEASE-340) Don't store the scm password in plaintext in release.properties
[ http://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133568#action_133568 ] Wendy Smoak commented on MRELEASE-340: -- This can be a major issue in corporate environments with strict security rules. In a single sign-on environment, exposing a password in plain text may compromise not only the source code repository, but all other systems the user has access to. Don't store the scm password in plaintext in release.properties --- Key: MRELEASE-340 URL: http://jira.codehaus.org/browse/MRELEASE-340 Project: Maven 2.x Release Plugin Issue Type: Improvement Reporter: Napoleon Esmundo C. Ramirez Priority: Minor The scm password is stored in plaintext in release.properties file. I think it would be safe not to save it there, then always prompt the user for the password every time. -- 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: (ARCHETYPE-166) maven-archetype-mojo
maven-archetype-mojo Key: ARCHETYPE-166 URL: http://jira.codehaus.org/browse/ARCHETYPE-166 Project: Maven Archetype Issue Type: Bug Components: Archetypes Reporter: Marvin Froeder When the new pom.xml is created, the file start looks like this: ?xml version=1.0 encoding=UTF-8? project . Would be better add xml schema data: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; VELO -- 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: (ARCHETYPE-166) Add XML schema on project tag
[ http://jira.codehaus.org/browse/ARCHETYPE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated ARCHETYPE-166: -- Summary: Add XML schema on project tag (was: maven-archetype-mojo) Add XML schema on project tag - Key: ARCHETYPE-166 URL: http://jira.codehaus.org/browse/ARCHETYPE-166 Project: Maven Archetype Issue Type: Bug Components: Archetypes Reporter: Marvin Froeder When the new pom.xml is created, the file start looks like this: ?xml version=1.0 encoding=UTF-8? project . Would be better add xml schema data: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; VELO -- 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: (MSITE-320) Reference documentation
[ http://jira.codehaus.org/browse/MSITE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133590#action_133590 ] Dennis Lundberg commented on MSITE-320: --- Thanks for the list. It makes it much easier for us to know in detail what it is that you (the users) want. I'll try to work on the documentation when I find some time. Reference documentation --- Key: MSITE-320 URL: http://jira.codehaus.org/browse/MSITE-320 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site descriptor Affects Versions: 2.0-beta-6 Environment: All Reporter: Alfonsas Stonis There is no documentation for site. I mean there is some, but this is not enough. For example there is no reference what elements can be included in site.xml. What are tags? No clue. It is not possible to use it as it is now. I do understand I can find out what they do by trying, but at least I need to know what they are. I tried to search on internet for any documentation, but no success. It is very frustrating. I think many users give up using it, just because they can not find what it can do and how to use it. Please provide at least simple list of the elements that are available in site.xml. -- 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: (MAVEN-1857) File manipulation using maven
File manipulation using maven - Key: MAVEN-1857 URL: http://jira.codehaus.org/browse/MAVEN-1857 Project: Maven 1 Issue Type: Test Environment: windows Reporter: Amol Bagul Hi How could I use maven script for file manupulation. If I want to pass some parameter and want to replace those in to the file, could I do this using maven. Regards, -Amol B -- 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
