[jira] Created: (MCHANGES-231) Changes plugin doesn't use maven proxy settings
Changes plugin doesn't use maven proxy settings
---
Key: MCHANGES-231
URL: http://jira.codehaus.org/browse/MCHANGES-231
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.4
Reporter: Bernd Vogt
Donwloading JIRA reports doesn't work inside a local network with http proxy,
even if the JIRA-host is configured as {{}} in the
{{settings.xml}}.
[INFO] Generating "JIRA Report" report.
[INFO] Downloading from JIRA at:
http:///jira/secure/IssueNavigator.jspa?view=rss&pid=10062&statusIds=6&resolutionIds=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none
[WARNING] Downloading from JIRA failed. Received: [502]
[WARNING] JIRA file
/home/vr/vr4build/build-env/data/jenkins/data/jobs/Generator Maven Plug-ins
Nightly/workspace/target/jira-results.xml doesn't exist.
--
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: (MCHANGES-231) Changes plugin doesn't use maven proxy settings
[
http://jira.codehaus.org/browse/MCHANGES-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262943#action_262943
]
Bernd Vogt commented on MCHANGES-231:
-
Found the problem.
{{JiraHelper#validateNonProxyHosts}} gets called with
{{http:///jira}} as value for the {{targetHost}} argument. Expected
just {{}}.
> Changes plugin doesn't use maven proxy settings
> ---
>
> Key: MCHANGES-231
> URL: http://jira.codehaus.org/browse/MCHANGES-231
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.4
>Reporter: Bernd Vogt
>
> Donwloading JIRA reports doesn't work inside a local network with http proxy,
> even if the JIRA-host is configured as {{}} in the
> {{settings.xml}}.
> [INFO] Generating "JIRA Report" report.
> [INFO] Downloading from JIRA at:
> http:///jira/secure/IssueNavigator.jspa?view=rss&pid=10062&statusIds=6&resolutionIds=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none
> [WARNING] Downloading from JIRA failed. Received: [502]
> [WARNING] JIRA file
> /home/vr/vr4build/build-env/data/jenkins/data/jobs/Generator Maven Plug-ins
> Nightly/workspace/target/jira-results.xml doesn't exist.
--
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: (MRELEASE-674) release plugin converts explicit version to snapshot
release plugin converts explicit version to snapshot - Key: MRELEASE-674 URL: http://jira.codehaus.org/browse/MRELEASE-674 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.1 Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100) Java version: 1.6.0_23, vendor: Sun Microsystems Inc. Java home: i:\tools\jdk\1.6.0_23\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" Reporter: Bernd Mau Attachments: MapVersionPhase.patch I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion(). I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line: mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false I made a patch and attached it to the issue. -- 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: (MPIR-224) Continuous Integration support for Jenkins
Continuous Integration support for Jenkins -- Key: MPIR-224 URL: http://jira.codehaus.org/browse/MPIR-224 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: cim Affects Versions: 2.3.1 Reporter: Bernd Bohmann -- 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: (MPIR-224) Continuous Integration support for Jenkins
[ http://jira.codehaus.org/browse/MPIR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann updated MPIR-224: --- Attachment: MPIR-224.patch > Continuous Integration support for Jenkins > -- > > Key: MPIR-224 > URL: http://jira.codehaus.org/browse/MPIR-224 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: cim >Affects Versions: 2.3.1 >Reporter: Bernd Bohmann > Attachments: MPIR-224.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] Created: (MANTTASKS-218) cacheDependencyRefs is ignored when pulling dependencies from a defined in the build.xml
cacheDependencyRefs is ignored when pulling dependencies from a defined in the build.xml -- Key: MANTTASKS-218 URL: http://jira.codehaus.org/browse/MANTTASKS-218 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.2 Reporter: Stephen Connolly When a is defined in the ant build.xml and then the task uses that then cacheDependencyRefs is ignored unless the is loaded from a file on disk. This is causing a regression in build time for the Apache Cassandra project (https://issues.apache.org/jira/browse/CASSANDRA-1851?focusedCommentId=13017152&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13017152) -- 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-218) cacheDependencyRefs is ignored when pulling dependencies from a defined in the build.xml
[ http://jira.codehaus.org/browse/MANTTASKS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MANTTASKS-218: --- Attachment: MANTTASKS-218.patch Attaching the patch for the Apache Cassandra guys to be able to build local copy > cacheDependencyRefs is ignored when pulling dependencies from a defined > in the build.xml > -- > > Key: MANTTASKS-218 > URL: http://jira.codehaus.org/browse/MANTTASKS-218 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.1.2 >Reporter: Stephen Connolly > Attachments: MANTTASKS-218.patch > > > When a is defined in the ant build.xml and then the task > uses that then cacheDependencyRefs is ignored unless the is > loaded from a file on disk. > This is causing a regression in build time for the Apache Cassandra project > (https://issues.apache.org/jira/browse/CASSANDRA-1851?focusedCommentId=13017152&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13017152) -- 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-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId
SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId - Key: MSITE-579 URL: http://jira.codehaus.org/browse/MSITE-579 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: multi module, relative links Affects Versions: 3.0-beta-3 Reporter: James Carman I have a multi-module project: https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/ In the main pom.xml file, I have: ... example In my generated site, here: http://wicketopia.sourceforge.net/wicketopia-example/source-repository.html The SCM urls are all messed up. They have "wicketopia-example" rather than just "example" in them. I do not set up SCM URLs in the submodules. I just let it inherit stuff from the parent POM. Since we specify example in the parent pom rather than wicketopia-example, shouldn't it know that the SCM URLs shouldn't have "wicketopia-example" in them? -- 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-4760) Way to activate profile based on Maven version
[ http://jira.codehaus.org/browse/MNG-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Gyongyi updated MNG-4760: --- Attachment: MNG-4760-maven-model-builder.patch MNG-4760-maven-model.patch maven-model.patch: This patch adds the "mavenVersion" field to the src/main/mdo/maven.mdo file. maven-model-builder.patch: This patch adds a class and its test to the project so that maven version can be checked when activating a profile. I added the maven-artifact dependency to the maven-model-builder pom because I used the VersionRange class to handle version numbers. After applying the patches, the mavenVersion tag can be used with version ranges and exact versions to activate a profile by maven version. Regards, Gabor Gyongyi > Way to activate profile based on Maven version > -- > > Key: MNG-4760 > URL: http://jira.codehaus.org/browse/MNG-4760 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Profiles >Affects Versions: 3.0-beta-2 > Environment: n/a >Reporter: Anders Hammar > Fix For: Issues to be reviewed for 3.x > > Attachments: MNG-4760-maven-model-builder.patch, > MNG-4760-maven-model.patch > > > A profile activation that checks the version of Maven being used would be > good. For example, the site plugin requires a different version when Maven 3 > is used. Currently, this is done through a profile that activates based on > teh fact that the basedir expression is only recognized by Maven 3.x, which > is IMO a not-so-pretty solution. (See > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin#Maven3.xandsiteplugin-Usingmavensiteplugin2.xwithMaven2.xandmavensiteplugin3.xwithMaven3.x) -- 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: (MCOMPILER-142) classes complied by plexus-compiler-eclipse get 'source not found' problem in eclipse class file editor
[ http://jira.codehaus.org/browse/MCOMPILER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262971#action_262971 ] Anthony O. commented on MCOMPILER-142: -- I've got the exact same problem ! > classes complied by plexus-compiler-eclipse get 'source not found' problem in > eclipse class file editor > --- > > Key: MCOMPILER-142 > URL: http://jira.codehaus.org/browse/MCOMPILER-142 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Rice Yeh >Priority: Critical > > All classes complied by plexus-compiler-eclipse will get 'source not found' > problem in eclipse class file editor which is opened when you access the jar > file containing the compiled classes even though you have source jar > associated with the jar file. A guy met the same problem as mine, see > http://www.mail-archive.com/users@maven.apache.org/msg80120.html. The > following is his observation on this problem: > After having a look into the generated classes, I found that the debug > information is different from the one I compiled with eclipse > jdt. For example, > Debug information from eclipse jdt compiler > Source File Name: MyClass.java > Debug information from plexus-compiler-eclipse maven plugin > Source File Name: com.mydomain.myproject.MyClass > This probable causes the problem. > Rice -- 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: (MPIR-224) Continuous Integration support for Jenkins
[ http://jira.codehaus.org/browse/MPIR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MPIR-224: -- Fix Version/s: 2.3.2 > Continuous Integration support for Jenkins > -- > > Key: MPIR-224 > URL: http://jira.codehaus.org/browse/MPIR-224 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: cim >Affects Versions: 2.3.1 >Reporter: Bernd Bohmann >Assignee: Olivier Lamy > Fix For: 2.3.2 > > Attachments: MPIR-224.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
