[jira] Updated: (MGPG-31) Integrate w/ Maven password encryption to avoid need to type passphrase
[
http://jira.codehaus.org/browse/MGPG-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MGPG-31:
-
Fix Version/s: (was: 1.3)
1.4
> Integrate w/ Maven password encryption to avoid need to type passphrase
> ---
>
> Key: MGPG-31
> URL: http://jira.codehaus.org/browse/MGPG-31
> Project: Maven 2.x GPG Plugin
> Issue Type: Improvement
>Affects Versions: 1.1
> Environment: JDK 6u21, Ubuntu, Maven 3.0 RC1
>Reporter: Jesse Glick
>Priority: Minor
> Fix For: 1.4
>
>
> It is cumbersome to be prompted for a passphrase during both release:prepare
> and release:perform:
> {noformat}
> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ nbm-maven-plugin
> ---
> GPG Passphrase: *
> {noformat}
> I already use http://maven.apache.org/guides/mini/guide-encryption.html (with
> a master password on an Ubuntu encrypted filesystem) so why do I need to type
> this pass phrase each time too?
> Not clear to me whether MGPG-30 already permits this. In any event, the
> plugin documentation does not seem to mention this as a use case.
--
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: (DOXIA-426) Markdown module
[ http://jira.codehaus.org/browse/DOXIA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Nicoulaud updated DOXIA-426: --- Attachment: doxia-module-markdown-3.patch > Markdown module > --- > > Key: DOXIA-426 > URL: http://jira.codehaus.org/browse/DOXIA-426 > Project: Maven Doxia > Issue Type: New Feature > Components: Modules >Affects Versions: 1.3 >Reporter: Julien Nicoulaud > Attachments: doxia-module-markdown-2.patch, > doxia-module-markdown-3.patch, doxia-module-markdown.patch > > > [Markdown|http://en.wikipedia.org/wiki/Markdown] is a widespread Markup > language. It would be nice if there was a Doxia module for Markdown. > Here is a proposed simple implementation that defers all the parsing and > rendering to [PegDown|http://pegdown.org] (Apache License V2), which is the > most reliable Java library for Markdown. -- 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-426) Markdown module
[ http://jira.codehaus.org/browse/DOXIA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268942#action_268942 ] Julien Nicoulaud commented on DOXIA-426: Sorry for the empty files, this is due to the way IntelliJ IDEA exports Subversion patches. Here is a new one: * test.md is now exhaustive. * Added a unit test I had forgotten. * Added rudimentary site index page. > Markdown module > --- > > Key: DOXIA-426 > URL: http://jira.codehaus.org/browse/DOXIA-426 > Project: Maven Doxia > Issue Type: New Feature > Components: Modules >Affects Versions: 1.3 >Reporter: Julien Nicoulaud > Attachments: doxia-module-markdown-2.patch, > doxia-module-markdown-3.patch, doxia-module-markdown.patch > > > [Markdown|http://en.wikipedia.org/wiki/Markdown] is a widespread Markup > language. It would be nice if there was a Doxia module for Markdown. > Here is a proposed simple implementation that defers all the parsing and > rendering to [PegDown|http://pegdown.org] (Apache License V2), which is the > most reliable Java library for Markdown. -- 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-2816) bson library
bson library Key: MAVENUPLOAD-2816 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2816 Project: Maven Upload Requests Issue Type: Wish Reporter: Scott Hernandez "org.bson","rsync://buildbot.mongodb.org/maven/","rsync","Eliot Horowitz","el...@mongodb.org",, -- 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: (WAGON-330) Move to ASF httpclient 4.x
[ http://jira.codehaus.org/browse/WAGON-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268952#action_268952 ] Mark Struberg commented on WAGON-330: - we also need to upgrade jackrabbit since the old client relies on httpclient-3.1 > Move to ASF httpclient 4.x > -- > > Key: WAGON-330 > URL: http://jira.codehaus.org/browse/WAGON-330 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-webdav >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.0 > > -- 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: (MRELEASE-639) Anthill Pro build server expects to be logged into Perforce. Using the release plugin, a perforce login is invoked continuously.
[ http://jira.codehaus.org/browse/MRELEASE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gary fry closed MRELEASE-639. - Resolution: Not A Bug Used the existing "feature" of not specifying a P4PASSWD to work-around. This issue is no longer relevant. > Anthill Pro build server expects to be logged into Perforce. Using the > release plugin, a perforce login is invoked continuously. > - > > Key: MRELEASE-639 > URL: http://jira.codehaus.org/browse/MRELEASE-639 > Project: Maven 2.x Release Plugin > Issue Type: New Feature >Affects Versions: 2.1 > Environment: Anthill Pro/Perforce, maven-scm-provider-perforce >Reporter: gary fry > Attachments: PerforceLoginCommand.java, PerforceLoginCommandTest.java > > > Currently we have a build system that relies on a Perforce client to be > continuously logged in. We have taken a fork of the release plugin to make > it work this way. ie we've commented out the login code. A better solution > is to make this available for others with similar problems. > If a property was provided, it would enable bypassing the Perforce login > command. Attached suggested fix. > if -Dmaven.scm.perforce.perform.login is not coded, default behaviour occurs > (ie p4 login) > if -Dmaven.scm.perforce.perform.login=true is coded, default behaviour occurs > (ie p4 login) > if -Dmaven.scm.perforce.perform.login=false is coded, no Perforce login > occurs and a warning is logged. -- 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: (WAGON-330) Move to ASF httpclient 4.x
[ http://jira.codehaus.org/browse/WAGON-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268963#action_268963 ] Mark Struberg commented on WAGON-330: - humm, too bad that jackrabbit-2.2.5 is _still_ relying on httpclient-3.0 :( So we have 2 options here: a) clone the old wagon-http-shared to a wagon-http-shared3 with the old stuff b) let the dependency from wagon-webdav-jackrabbit point to the latest 1.0-beta.* version any other idea? > Move to ASF httpclient 4.x > -- > > Key: WAGON-330 > URL: http://jira.codehaus.org/browse/WAGON-330 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-webdav >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.0 > > -- 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: (WAGON-330) Move to ASF httpclient 4.x
[ http://jira.codehaus.org/browse/WAGON-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated WAGON-330: Attachment: WAGON-330.patch here is my work so far. All other projects than webdav are able to compile and pass tests (which I'd say indicate that we don't have enough tests!) > Move to ASF httpclient 4.x > -- > > Key: WAGON-330 > URL: http://jira.codehaus.org/browse/WAGON-330 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http, wagon-webdav >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.0 > > Attachments: WAGON-330.patch > > -- 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-426) Markdown module
[ http://jira.codehaus.org/browse/DOXIA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268970#action_268970 ] Lukas Theussl commented on DOXIA-426: - Patch applied in [r1128829|http://svn.apache.org/viewvc?rev=1128829&view=rev]. Thanks! > Markdown module > --- > > Key: DOXIA-426 > URL: http://jira.codehaus.org/browse/DOXIA-426 > Project: Maven Doxia > Issue Type: New Feature > Components: Modules >Affects Versions: 1.3 >Reporter: Julien Nicoulaud > Attachments: doxia-module-markdown-2.patch, > doxia-module-markdown-3.patch, doxia-module-markdown.patch > > > [Markdown|http://en.wikipedia.org/wiki/Markdown] is a widespread Markup > language. It would be nice if there was a Doxia module for Markdown. > Here is a proposed simple implementation that defers all the parsing and > rendering to [PegDown|http://pegdown.org] (Apache License V2), which is the > most reliable Java library for Markdown. -- 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
