[jira] Closed: (MNG-2305) only first active proxy considered/used
[ http://jira.codehaus.org/browse/MNG-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-2305. -- Resolution: Fixed Fix Version/s: (was: 3.0-beta-1) 3.0-alpha-3 Assignee: Benjamin Bentmann > only first active proxy considered/used > --- > > Key: MNG-2305 > URL: http://jira.codehaus.org/browse/MNG-2305 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 2.0.4, 2.1.0-M1 > Environment: WIN2K JDK 1.5.0_06 > proxy:81 for both http and https >Reporter: Franz Fehringer >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > Attachments: settings.xml > > > With the attached settings.xml > all https connects fail (doing mvn -U). > If i reverse the order (https first http second) all http connects fail. > Questions: > Does https tunneling over http proxies work at all with Maven2 (sending HTTP > CONNECT to the proxy is needed)? > Why is the Java system configuration (in Application > Data\Sun\Java\Deployment\deployment.properties) not used to detect proxies? -- 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: (MNG-4123) still can't override properties in pom.xml with -D command line settings. regression?
[
http://jira.codehaus.org/browse/MNG-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4123.
--
Resolution: Cannot Reproduce
> still can't override properties in pom.xml with -D command line settings.
> regression?
> -
>
> Key: MNG-4123
> URL: http://jira.codehaus.org/browse/MNG-4123
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0-alpha-2
> Environment: windows vista
>Reporter: chris bedford
>Assignee: Benjamin Bentmann
> Attachments: MNG-4123.zip
>
>
> Hello...
> The original bug ( http://jira.codehaus.org/browse/MNG-1992
> ) was marked as fixed in 2.1.0, and 3.0-alpha-1
> I used a slightliy modifed version of the test case described in
> http://jira.codehaus.org/browse/MNG-3417
> to understand what I thought i was seeing...
> It still seems not to work as described in the original bug.
> I tried two things...
> 1) tried resource filtering (running>mvn
> -Dtest.property='overridden' clean verify < and catting test.xt as
> described in the original bug report.
> same result.
> Then I tried updating my maven resources plugin to 2.3 -- running with
> maven 3.0-alpha-2(see modified pom.xml, below).Stil no luck.
> 2) next i tried
> mvn -e -Dtest.result=haha help:effective-pom
> the property setting given for test.result was still default.
> So it seems like there are two failure modes (?) . one for resource
> filtering, and one for interpolation process that does not involve filtering..
> or maybe they have they same root cause. In any case it seems not to work
> still (at least on windoze).
> thanks !
> -chris
> modified pom.xml
> {code:xml}
>
>
> 4.0.0
> com.test
> test
> 1.0
> jar
>
> default
> *.txt
>
>
>
> test.profile
>
>profile
>*.txt
>
>
>
>
>
>
>
> maven-resources-plugin
> 2.3
>
>
>
>
>
>${basedir}/src/test/resources
>true
>
>${test.include.pattern}
>
>
>
>
>
> {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] Commented: (MREPOSITORY-11) Javadoc not included in the bundle
[ http://jira.codehaus.org/browse/MREPOSITORY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216485#action_216485 ] Aaron Kaplan commented on MREPOSITORY-11: - Ben's comment about the documentation being out of date has still not been addressed. > Javadoc not included in the bundle > -- > > Key: MREPOSITORY-11 > URL: http://jira.codehaus.org/browse/MREPOSITORY-11 > Project: Maven 2.x Repository Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Maven version: 2.0.7 > Java version: 1.4.2_13 > OS name: "windows xp" version: "5.1" arch: "x86" >Reporter: Julien HENRY >Assignee: Carlos Sanchez > Fix For: 2.1 > > > On a simple project, I run: > mvn clean source:jar javadoc:jar repository:bundle-create > As a result in target I get: > artifact-version.jar > artifact-version-bundle.jar > artifact-version-javadoc.jar > artifact-version-sources.jar > But in artifact-version-bundle.jar there are only: > META-INF > pom.xml > LICENSE.txt > artifact-version.jar > artifact-version-sources.jar -- 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: (MNG-3133) DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths
[
http://jira.codehaus.org/browse/MNG-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3133.
--
Resolution: Fixed
Assignee: Benjamin Bentmann
Fixed in [r930411|http://svn.apache.org/viewvc?view=revision&revision=930411].
> DefaultModelInheritence::appendPath assumes it is operating on
> interpolated/literal paths
> -
>
> Key: MNG-3133
> URL: http://jira.codehaus.org/browse/MNG-3133
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.7
>Reporter: John Allen
>Assignee: Benjamin Bentmann
>Priority: Critical
> Fix For: 3.0-beta-1
>
>
> Used by all the assembleXXXInheritance methods within
> assembleModelInheritance, the appendPath method assumes that its dealing with
> literal paths which is not a documented restriction. Thus having
> ${expressions} in any of the paths being operated on (e.g. project URL,
> distroManagement site, SCM, etc etc), the results will not be valid.
> This whole area of Maven's core requires a specification so it can be coded
> too and maintained.
--
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
