[jira] Updated: (MNG-4211) [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+
[ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-4211: --- Fix Version/s: (was: 2.2.1) (was: 3.0-alpha-3) > [regression] proxy access broken between maven version 2.0.10 and 2.1. > Probably due to addition of wagon 1.0-beta-4+ > - > > Key: MNG-4211 > URL: http://jira.codehaus.org/browse/MNG-4211 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1.0, 2.2.0 > Environment: WinXP SP2 >Reporter: Robert Glover Jr >Priority: Blocker > Attachments: jira_files_4_total.zip > > > At a large company, maven become impossible to use via proxy when maven > upgraded from 1.0.10 to 2.1. maven has always worked fine via proxy in 2.0.9 > and continues to work fine. however maven via proxy always fails in version > 2.1.0 and higher. > Attached is a zip file containing 1) log of GMAIL chat between the > creater of this JIRA and a maven developer. 2) two console outputs of > running maven 2.2. RC3 showing the proxy failure messages. 3) setting.xml > (with comments stripped out) -- 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-4221) Push all repository/artifact related code into a legacy module and create a backward compat layer for external consumers
Push all repository/artifact related code into a legacy module and create a backward compat layer for external consumers Key: MNG-4221 URL: http://jira.codehaus.org/browse/MNG-4221 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl -- 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: (MNG-4221) Push all repository/artifact related code into a legacy module and create a backward compat layer for external consumers
[ http://jira.codehaus.org/browse/MNG-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-4221: --- Affects Version/s: 3.0-alpha-2 Fix Version/s: 3.0-alpha-3 > Push all repository/artifact related code into a legacy module and create a > backward compat layer for external consumers > > > Key: MNG-4221 > URL: http://jira.codehaus.org/browse/MNG-4221 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-2 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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] Work started: (MNG-4221) Push all repository/artifact related code into a legacy module and create a backward compat layer for external consumers
[ http://jira.codehaus.org/browse/MNG-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-4221 started by Jason van Zyl. > Push all repository/artifact related code into a legacy module and create a > backward compat layer for external consumers > > > Key: MNG-4221 > URL: http://jira.codehaus.org/browse/MNG-4221 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-2 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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-4222) Use Apache JSecurity (Shiro) to implement a general security system for repository access
Use Apache JSecurity (Shiro) to implement a general security system for repository access - Key: MNG-4222 URL: http://jira.codehaus.org/browse/MNG-4222 Project: Maven 2 Issue Type: New Feature Reporter: Jason van Zyl -- 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] Work started: (MNG-4222) Use Apache JSecurity (Shiro) to implement a general security system for repository access
[ http://jira.codehaus.org/browse/MNG-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-4222 started by Jason van Zyl. > Use Apache JSecurity (Shiro) to implement a general security system for > repository access > - > > Key: MNG-4222 > URL: http://jira.codehaus.org/browse/MNG-4222 > Project: Maven 2 > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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: (MNG-4222) Use Apache JSecurity (Shiro) to implement a general security system for repository access
[ http://jira.codehaus.org/browse/MNG-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-4222: --- Fix Version/s: 3.0-alpha-3 > Use Apache JSecurity (Shiro) to implement a general security system for > repository access > - > > Key: MNG-4222 > URL: http://jira.codehaus.org/browse/MNG-4222 > Project: Maven 2 > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > -- 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: (DOXIA-345) UTF-8 problems with APT and XDOC format
UTF-8 problems with APT and XDOC format --- Key: DOXIA-345 URL: http://jira.codehaus.org/browse/DOXIA-345 Project: Maven Doxia Issue Type: Bug Affects Versions: 2.0 Environment: Ubuntu Linux 9.04 (Kernel 2.6.28-13-generic) ; Java 1.6 u 13 jdk 32 bit ; maven-site-plugin with 2.0-beta-7 Reporter: Bernhard Grünewaldt Attachments: utf8-test.zip At the moment I am using the XDOC format. I want to switch to APT format since it is the "replacement" for XDOC. That's what you write on your website. I read the previous bugs on ISO-8859-1 and UTF-8 issues. For xdoc it now works when using maven-site-plugin with version 2.0-beta-7 and outputEncoding utf8. But for APT there is still the problem that the fileencoding is in "plattformencoding" which is latin1 or ISO-8859-1, but not UTF-8. And asian characters don't come in ISO, they come in utf8 encoding. So how can the APT format be the replacement for XDOC when that is not working. Could you please come up with a solution for it. How about another file-extension for utf8 apt files. Like "filename.uapt" I would really appreciate any solutions on that problem. I attached a test-project to the bug with one apt file and one xdoc file with special utf8 chars. -- 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: (MPIR-160) Dependency report ignores local repository and always re-fetches artifacts from remote repos
[
http://jira.codehaus.org/browse/MPIR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MPIR-160.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1.2
Fixed in [r789085|http://svn.apache.org/viewvc?view=rev&revision=789085].
> Dependency report ignores local repository and always re-fetches artifacts
> from remote repos
>
>
> Key: MPIR-160
> URL: http://jira.codehaus.org/browse/MPIR-160
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.1.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.1.2
>
>
> Due to [r675941|http://svn.apache.org/viewvc?view=rev&revision=675941] the
> dependency report uses {{ArtifactResolver.resolveAlways()}} instead of
> {{ArtifactResolver.resolve()}}. Usage of the former method wipes out the
> caching effect of the local repository, thereby producing massive amount of
> exceptions during offline mode and more severely causing high network traffic
> that slows down the build.
--
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: (MNG-3538) Properties inside are not replaced in resulting POM
[
http://jira.codehaus.org/browse/MNG-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3538:
---
Fix Version/s: (was: 2.2.0)
> Properties inside are not replaced in resulting POM
>
>
> Key: MNG-3538
> URL: http://jira.codehaus.org/browse/MNG-3538
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
>Reporter: Ondrej Par
>Assignee: John Casey
>
> When I use the following dependency definition, the correct classifier is
> used during build; however, when the project POM file is deployed to the
> repository, it still contains the property name, not the replaced value:
>
> someGroup
> someArtifact
> 3.3.0
> ${myproperty.arch}
>
--
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: (MNG-4167) version-expression transformation interferes with plugins like GPG
[ http://jira.codehaus.org/browse/MNG-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4167: --- Affects Version/s: (was: 2.2.0) 2.1.0 > version-expression transformation interferes with plugins like GPG > -- > > Key: MNG-4167 > URL: http://jira.codehaus.org/browse/MNG-4167 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1.0 >Reporter: John Casey >Assignee: John Casey > Fix For: 3.x > > > See MGPG-14. -- 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-4140) Properties incorrectly replaced in pom
[
http://jira.codehaus.org/browse/MNG-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181768#action_181768
]
Benjamin Bentmann commented on MNG-4140:
For the record, POM interpolation upon installation/deployment to repos has
been completely removed from Maven 2.2.
> Properties incorrectly replaced in pom
> --
>
> Key: MNG-4140
> URL: http://jira.codehaus.org/browse/MNG-4140
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Reinhard Nägele
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: pom-transformed.xml, pom.xml
>
>
> The attached sample pom configures the dependency plugin. During an install,
> {{$\{project.version\}}} is replaced by the actual version when in fact no
> replacement at all must happen (see {{pom-transformed.xml}}). This seems to
> be related to the {{version}}, since all other properties remain unchanged.
> In our real world scenario, the dependency plugin is configured in a profile
> in order to copy child module artifacts to Luntbuild's publish directory.
> This, of course, won't work if the version is replaced during install. It
> must be evaluated at runtime.
> This is a regression in Maven 2.1.0. Maven 2.0.10 does not have the problem.
--
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-269) Allow configuration of httpclient to change cookie policy, other options
[ http://jira.codehaus.org/browse/WAGON-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-269: --- Fix Version/s: (was: 1.0) 1.0-beta-6 > Allow configuration of httpclient to change cookie policy, other options > > > Key: WAGON-269 > URL: http://jira.codehaus.org/browse/WAGON-269 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http >Affects Versions: 1.0-beta-5 >Reporter: John Casey >Assignee: John Casey > Fix For: 1.0-beta-6 > > > In some cases, using non-lightweight http wagon can result in WARNING > messages about cookies with an incorrect path. This can be a particular > problem where internal rewrite modules change the location of a servlet that > expects to be at a different path than the one the browser used to access it. > httpclient configuration options need to be exposed for configuration from > the settings.xml in order to allow users to fix this. Simply ignoring cookies > is probably not a great option, since some sites do rely on session cookies > to maintain authentication, etc. Additionally, there is a wealth of > configuration available for httpclient, and exposing a method for configuring > this wagon comprehensively should help us head off future concerns about one > of the other config options. -- 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-2499) Please sync org.infinitest's continuous testing toolkit with central
Please sync org.infinitest's continuous testing toolkit with central Key: MAVENUPLOAD-2499 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2499 Project: Maven Upload Requests Issue Type: Wish Reporter: Paul Holser Hosting this bundle on Sourceforge alongside my jopt-simple project. Contact benr...@gmail.com for more details about Infinitest and the attendant Continuous Testing Toolkit. "org.infinitest","mavens...@shell.sourceforge.net:/home/groups/j/jo/jopt-simple/htdocs/maven","rsync_ssh","Paul Holser","phol...@gmail.com",, or "org.infinitest.continuous-testing-toolkit","mavens...@shell.sourceforge.net:/home/groups/j/jo/jopt-simple/htdocs/maven","rsync_ssh","Paul Holser","phol...@gmail.com",, Whichever makes more sense. -- 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
