[jira] Commented: (MNG-4602) Allow pluggable authentication (using JAAS ?) so that the username and password to connect to a deployment repository can be generated by a Single Sign On-enabled client
[ http://jira.codehaus.org/browse/MNG-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249018#action_249018 ] David Boden commented on MNG-4602: -- It's all changed in Maven 3 with the introduction of Aether for repository management. The fix that I mentioned above isn't strategic for Maven 3 and, because we've already upgraded to Maven 3, I propose to fix it in a different way. In Maven 3 the server authentication details are read from settings.xml in: Project: maven-core Method: org.apache.maven.DefaultMaven.newRepositorySession( MavenExecutionRequest request ) To get the LoginContext or CallbackHandler configuration into settings.xml under the tag, I'd need to create a new version of: http://maven.apache.org/xsd/settings-1.0.0.xsd As a quick-fix, I could just add the configuration to the tag under . It would be a better change to add the CallbackHandler configuration to the Authentication class. That way, the CallbackHandler could be used only when authentication is required. If I make a call to the CallbackHandler within newRepositorySession then I'll have to call every configured callback handler and generate a username and password. More efficient to leave the call until later so that only the server definitions that are being used result in a CallbackHandler call. That would require changing the org.sonatype.aether.repository.Authentication class in the aether-api module. I'll then have to work out (probably by using a debugger) where the Authentication.getUsername() is called and see how many places need to be upgraded to support a call out to a CallbackHandler. > Allow pluggable authentication (using JAAS ?) so that the username and > password to connect to a deployment repository can be generated by a Single > Sign On-enabled client > - > > Key: MNG-4602 > URL: http://jira.codehaus.org/browse/MNG-4602 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Artifacts and Repositories, Settings >Reporter: David Boden >Priority: Minor > > The username and password used to authenticate with the remote repository > during deployment are stored in the user's settings.xml under the > structure. This structure allows a username and password to be specified, or > for a .ssh private key to be specified. > It does not allow for pluggable single sign on, where a Java module (perhaps > a JAAS LoginModule) is available on the client to generate a token in place > of a password. Many corporates use this technique for other web applications, > generating an LDAP token from the user's PC and verifying it against an LDAP > server on the server side. It adds security by removing the need to pass the > user's password over the wire. > This Jira is a request for a pluggable entry point for this single sign on > module, perhaps by specifying a class name in the structure or by > setting a system property. The solution could either define a new interface > which Authentication Providers must implement or can use existing interfaces > from JAAS, (Http) Authenticator or other frameworks. > Please feel free to move this item to the "Maven Wagon" component if you feel > that's the best place to implement the feature. Alternatively, please also > feel free to move to the generic "Maven 2&3" component if you think that the > feature has wider scope than just deployment; perhaps to also authenticate > using Single Sign On with an internal company's repository when *downloading* > artifacts (as well as uploading). -- 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-423) item hrefs not relativised properly when inherited by child modules
[ http://jira.codehaus.org/browse/MSITE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249027#action_249027 ] Lukas Theussl commented on MSITE-423: - I could fix your test project by appending a "/" to the pom s and by fixing some links that are obviously wrong (eg in module1's site.xml, the link to submodule1 should be href="./link-problem-submodule1/index.html" instead of href="./link-problem-module1/link-problem-submodule1/index.html"). After that, a local site deploy gave correct links, so the problem is only for site:stage. > item hrefs not relativised properly when inherited by child modules > --- > > Key: MSITE-423 > URL: http://jira.codehaus.org/browse/MSITE-423 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 2.1 > Environment: Linux, JDK 1.6.0_07, Maven 2.1.0 >Reporter: Robert Davey > Attachments: doxia-sitetools.patch, site-plugin_link-problem.tar.gz > > > See attachment for reproducible minimal case. > I have a multi-module project, for the sake of argument laid out thus: > * parent > ** pom.xml > * module1 > ** pom.xml > ** src/site/site.xml > ** apt/index.apt > > ** submodule1 >*** pom.xml >*** src/site/site.xml >*** apt/index.apt > I specify some links in our parent POM that I want to be inherited by all > child multi-modules. I would hope these links would always point to the > relevant html files in the super parent project for all children, no matter > the nesting level. > > > > > > These links work fine for the super parent menu. The same problem, outlined > below, is apparent whether the links are prefixed by "/" or "./" > When navigating down to module1, all the href links become: > ../module1 > Navigating again down to submodule1 of module1, the links become (or > something equally wacky): > ../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../submodule1 > All the pom.xml files in each module refer to the staged url correctly, and > these don't seem to make any difference to the eventual href whatsoever... > e.g. > parent: http://server/ > module1: http://server/module1 > submodule1: http://server/module1/submodule1 -- 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-534) site:stage gives different links than site:deploy
site:stage gives different links than site:deploy - Key: MSITE-534 URL: http://jira.codehaus.org/browse/MSITE-534 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Lukas Theussl See MSITE-423 for a test project. -- 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: (MSITE-534) site:stage gives different links than site:deploy
[
http://jira.codehaus.org/browse/MSITE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-534:
Attachment: MSITE-534.zip
Test project adapted from MSITE-423. Run site:stage and site:deploy and compare
the links ("Home", "Getting started" etc) in the sub-modules.
> site:stage gives different links than site:deploy
> -
>
> Key: MSITE-534
> URL: http://jira.codehaus.org/browse/MSITE-534
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Lukas Theussl
> Attachments: MSITE-534.zip
>
>
> See MSITE-423 for a test project.
--
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: (MSITE-422) Links being "relativized" incorrectly.
[
http://jira.codehaus.org/browse/MSITE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-422.
---
Resolution: Incomplete
Assignee: Lukas Theussl
> Links being "relativized" incorrectly.
> --
>
> Key: MSITE-422
> URL: http://jira.codehaus.org/browse/MSITE-422
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: relative links
>Affects Versions: 2.0.1
>Reporter: Jason Smith
>Assignee: Lukas Theussl
>
> This also appears to be broken in 2.1-SNAPSHOT as the original entry date of
> this JIRA. It was first discovered in 2.0, and also affects 2.0.1.
> I have the following links in my site.xml. This is a multi-module project,
> but this affects the top-level (parent) project documentation.
>
> http://groovy.codehaus.org/COM+Scripting/..";
> />
>href="http://groovy.codehaus.org/COM+Scripting"; />
>
> Here is the HTML produced:
> Groovy |
> http://groovy.codehaus.org/COM+Scripting";
> class="externalLink">Scriptom Wiki
> The first link is relativized. Incorrectly. My site-distribution is:
>
> codehaus.org.snapshots
> Groovy Website
> dav:https://dav.codehaus.org/groovy/modules/scriptom/SNAPSHOT/${project.version}
>
> Technically, the relative path should be "../../../../..". It would have
> worked just fine if the HREF were "http://groovy.codehaus.org/";.
> Is it actually necessary to complicate the by relativizing the paths
> whenever possible, or would it be simpler just to pass the original HREF
> through unmodified?
--
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: (MSHARED-175) wrong relative path resolution for links
wrong relative path resolution for links Key: MSHARED-175 URL: http://jira.codehaus.org/browse/MSHARED-175 Project: Maven Shared Components Issue Type: Bug Components: maven-doxia-tools Affects Versions: maven-doxia-tools 1.4 Reporter: Lukas Theussl See patch attached at MSITE-423 and test project at MSITE-534 -- 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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MEAR-131:
-
Fix Version/s: 2.5
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
> Fix For: 2.5
>
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MEAR-128) Support for Java EE 6 application.xml
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-128: - Fix Version/s: (was: 2.6) 2.5 > Support for Java EE 6 application.xml > - > > Key: MEAR-128 > URL: http://jira.codehaus.org/browse/MEAR-128 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Peter Major >Assignee: Stephane Nicoll > Fix For: 2.5 > > > Currently the Java EE 6 is not supported, and the generated XML's are using > Java EE 5 namespaces and elements. For example the EE 6 has a new element: > application-name, which could be useful for Global JNDI naming. -- 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: (MEAR-126) Add includeInApplicationXml property in ejbModule
[ http://jira.codehaus.org/browse/MEAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-126. Resolution: Won't Fix I agree with Jeroen's analysis. > Add includeInApplicationXml property in ejbModule > - > > Key: MEAR-126 > URL: http://jira.codehaus.org/browse/MEAR-126 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Anthony Donnefort >Priority: Minor > Attachments: includeInApplicationXml.patch > > > The ear plugin currently add all dependencies of type 'ejb' in the generated > application.xml. > Adding the property includeInApplicationXml (already present in jarModule) to > the ejbModule would allow to include the jar but not deploy it, for example > when it is used as a client. > In case of the ejbModule, the default value is set to true. > The implementation is pretty straightforward and included in this 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] Updated: (MEAR-132) State default value for generateApplicationXml
[ http://jira.codehaus.org/browse/MEAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-132: - Fix Version/s: 2.5 > State default value for generateApplicationXml > -- > > Key: MEAR-132 > URL: http://jira.codehaus.org/browse/MEAR-132 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.4.2 > Environment: n/a >Reporter: Anders Hammar >Assignee: Stephane Nicoll > Fix For: 2.5 > > > The default value for the generateApplicationXml param is 'true'. But this is > not stated in the docs or when using the help goal. I believe what's missing > is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: > /** > * Whether the application.xml should be generated or not. > * > * @parameter default-value="true" > */ > private Boolean generateApplicationXml = Boolean.TRUE; -- 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: (MEAR-65) Support MAR archives
[ http://jira.codehaus.org/browse/MEAR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-65: Fix Version/s: 2.6 > Support MAR archives > > > Key: MEAR-65 > URL: http://jira.codehaus.org/browse/MEAR-65 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: N/A >Reporter: David J. M. Karlsen >Assignee: Stephane Nicoll >Priority: Trivial > Fix For: 2.6 > > > Add support for adding MARs to the archive (mar), like the axis2 > addressing module @: > http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.2/ -- 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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MEAR-131 started by Stephane Nicoll.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
> Fix For: 2.5
>
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MEAR-132) State default value for generateApplicationXml
[ http://jira.codehaus.org/browse/MEAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-132 started by Stephane Nicoll. > State default value for generateApplicationXml > -- > > Key: MEAR-132 > URL: http://jira.codehaus.org/browse/MEAR-132 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.4.2 > Environment: n/a >Reporter: Anders Hammar >Assignee: Stephane Nicoll > Fix For: 2.5 > > > The default value for the generateApplicationXml param is 'true'. But this is > not stated in the docs or when using the help goal. I believe what's missing > is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: > /** > * Whether the application.xml should be generated or not. > * > * @parameter default-value="true" > */ > private Boolean generateApplicationXml = Boolean.TRUE; -- 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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll closed MEAR-131.
Resolution: Fixed
Fixed.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
> Fix For: 2.5
>
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MEAR-128) Support for Java EE 6 application.xml
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249040#action_249040 ] Stephane Nicoll commented on MEAR-128: -- okay let's add support for application-name and initialize-in-order > Support for Java EE 6 application.xml > - > > Key: MEAR-128 > URL: http://jira.codehaus.org/browse/MEAR-128 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Peter Major >Assignee: Stephane Nicoll > Fix For: 2.5 > > > Currently the Java EE 6 is not supported, and the generated XML's are using > Java EE 5 namespaces and elements. For example the EE 6 has a new element: > application-name, which could be useful for Global JNDI naming. -- 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: (MEAR-128) Support for Java EE 6 application.xml
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-128 started by Stephane Nicoll. > Support for Java EE 6 application.xml > - > > Key: MEAR-128 > URL: http://jira.codehaus.org/browse/MEAR-128 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Peter Major >Assignee: Stephane Nicoll > Fix For: 2.5 > > > Currently the Java EE 6 is not supported, and the generated XML's are using > Java EE 5 namespaces and elements. For example the EE 6 has a new element: > application-name, which could be useful for Global JNDI naming. -- 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: (MEAR-132) State default value for generateApplicationXml
[ http://jira.codehaus.org/browse/MEAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-132. Resolution: Fixed > State default value for generateApplicationXml > -- > > Key: MEAR-132 > URL: http://jira.codehaus.org/browse/MEAR-132 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.4.2 > Environment: n/a >Reporter: Anders Hammar >Assignee: Stephane Nicoll > Fix For: 2.5 > > > The default value for the generateApplicationXml param is 'true'. But this is > not stated in the docs or when using the help goal. I believe what's missing > is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: > /** > * Whether the application.xml should be generated or not. > * > * @parameter default-value="true" > */ > private Boolean generateApplicationXml = Boolean.TRUE; -- 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: (MEAR-128) Support for application-name and initialize-in-order (Java EE 6)
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-128: - Summary: Support for application-name and initialize-in-order (Java EE 6) (was: Support for Java EE 6 application.xml) > Support for application-name and initialize-in-order (Java EE 6) > > > Key: MEAR-128 > URL: http://jira.codehaus.org/browse/MEAR-128 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Peter Major >Assignee: Stephane Nicoll > Fix For: 2.5 > > > Currently the Java EE 6 is not supported, and the generated XML's are using > Java EE 5 namespaces and elements. For example the EE 6 has a new element: > application-name, which could be useful for Global JNDI naming. -- 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: (MCHANGES-168) Jira Report (jira-report.html) scrambles encoding of Jira Issues when their summary is written in Non Latin Characters
[ http://jira.codehaus.org/browse/MCHANGES-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-168: - Summary: Jira Report (jira-report.html) scrambles encoding of Jira Issues when their summary is written in Non Latin Characters (was: Jira Report (jira-report.html) scrambles encoding of Jira Issues that their summary is written in Non Latin Characters) > Jira Report (jira-report.html) scrambles encoding of Jira Issues when their > summary is written in Non Latin Characters > -- > > Key: MCHANGES-168 > URL: http://jira.codehaus.org/browse/MCHANGES-168 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.1 > Environment: mvn on Mac OS X 10.5.7 > Atlassian JIRA Enterprise Edition, Version: 3.13.2 on Ubuntu 8.04.2 >Reporter: Vangelis Ghiossis > Attachments: Jira-Report-ScreenShot.jpg, jira-report.html, > jira-results.xml, pom.xml > > > My Jira Issues have Summaries in Jira in non-Lating characters (in Greek in > our case). > The plugin works great up to the point that it creates the jira-report.html > (attached). > The jira-results.xml seems to be in UTF-8 (also attached). > If an XSL Stylesheet is used it does not seem to observe the rss data > encoding of Jira Issues which works, by the way, fine win Non-Latin > Characters with other rss clients. -- 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: (MEAR-128) Support for application-name and initialize-in-order (Java EE 6)
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-128. Resolution: Fixed Implemented. > Support for application-name and initialize-in-order (Java EE 6) > > > Key: MEAR-128 > URL: http://jira.codehaus.org/browse/MEAR-128 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Peter Major >Assignee: Stephane Nicoll > Fix For: 2.5 > > > Currently the Java EE 6 is not supported, and the generated XML's are using > Java EE 5 namespaces and elements. For example the EE 6 has a new element: > application-name, which could be useful for Global JNDI naming. -- 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: (MSITE-420) Parent project site descriptor menu options always a link back to parent site
[ http://jira.codehaus.org/browse/MSITE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-420. --- Resolution: Not A Bug Assignee: Lukas Theussl Please open a new issue with a specific test project if anything is unclear. > Parent project site descriptor menu options always a link back to parent site > - > > Key: MSITE-420 > URL: http://jira.codehaus.org/browse/MSITE-420 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: doxia integration, inheritance >Affects Versions: 2.0-beta-5, 2.0-beta-6, 2.0-beta-7, 2.0, 2.0.1 > Environment: Using maven 2.0.9 - and all versions of the site plugin > all the way back to 2.0-beta-5. >Reporter: EJ Ciramella >Assignee: Lukas Theussl > Attachments: MSITE-420.zip, MSITE-420.zip > > > I'd like to have a parent project define what items are in a given menu for > all child projects and let the child projects define the contents of those > links (this doesn't work). > In the documentation for the site plugin here: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > There is a bit in there about how to get a parent project site descriptor to > be inherited by a child project by using the following: > > This is great if you want the child project to always link back to the parent > project's links/pages for each menu option. > Doxia however shows this is configurable: > http://maven.apache.org/doxia/doxia-sitetools-1.0.x/doxia-decoration-model/decoration.html#class_menu > inheritAsRef - If this is a reference, setting true means that it will be > populated in the project, whereas if it is false, it is populated in the > parent and then inherited. The default value is false. > This property currently doesn't work. -- 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-420) Parent project site descriptor menu options always a link back to parent site
[ http://jira.codehaus.org/browse/MSITE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249043#action_249043 ] Lukas Theussl commented on MSITE-420: - If you add a url to the child you also have to add one to the parent. You didn't specify any distributionManagement url, in this case the site plugin will automatically add the child artifactId to the effective deploy location, so the child will be one directory below the parent. However, relative links are calculated from the project url, so if your parent has http://parent/ then your child needs http://parent/child/. > Parent project site descriptor menu options always a link back to parent site > - > > Key: MSITE-420 > URL: http://jira.codehaus.org/browse/MSITE-420 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: doxia integration, inheritance >Affects Versions: 2.0-beta-5, 2.0-beta-6, 2.0-beta-7, 2.0, 2.0.1 > Environment: Using maven 2.0.9 - and all versions of the site plugin > all the way back to 2.0-beta-5. >Reporter: EJ Ciramella > Attachments: MSITE-420.zip, MSITE-420.zip > > > I'd like to have a parent project define what items are in a given menu for > all child projects and let the child projects define the contents of those > links (this doesn't work). > In the documentation for the site plugin here: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > There is a bit in there about how to get a parent project site descriptor to > be inherited by a child project by using the following: > > This is great if you want the child project to always link back to the parent > project's links/pages for each menu option. > Doxia however shows this is configurable: > http://maven.apache.org/doxia/doxia-sitetools-1.0.x/doxia-decoration-model/decoration.html#class_menu > inheritAsRef - If this is a reference, setting true means that it will be > populated in the project, whereas if it is false, it is populated in the > parent and then inherited. The default value is false. > This property currently doesn't work. -- 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-535) Do not use project.url for relativ link resolution
Do not use project.url for relativ link resolution -- Key: MSITE-535 URL: http://jira.codehaus.org/browse/MSITE-535 Project: Maven 2.x and 3.x Site Plugin Issue Type: Improvement Components: doxia integration, inheritance, relative links Affects Versions: 2.2 Reporter: Lukas Theussl IMO distributionManagement.site.url should be used instead. Imagine a multi-module site with a distributionManagement url that points to the local file system. A local deploy will move any child sites to sub-directories of the parent (by default), but if you forget to adjust the project urls for all children, the relative links are all wrong because they are calculated from the project urls. There are numerous examples and JIRAs where people are confused about this. Having to specify a url for each single child project is a duplicate information and is also logically not necessary. Note that the distributionManagement url always exists (otherwise the deploy will fail), while the project url is optional. IMO the project url should not be used for the local site generation at all, it is just a piece of user information. -- 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: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources
Setting up maven resources when testing in addition to testResources
Key: SUREFIRE-667
URL: http://jira.codehaus.org/browse/SUREFIRE-667
Project: Maven Surefire
Issue Type: New Feature
Affects Versions: 2.6
Reporter: vychtrle
Hey,
I think that developers would need resource goal of resource plugin to be set
up differently for
test phase, than for build phase. When testing one needs to exclude stuff
from src/main/resources. It seems it can't be done, testResources goal
is irrelevant for this because it can't operate on src/main/* and resource goal
can have only one
setting in pom definition, that takes effect in both test and build
phase...
For example, I'd need following settings to look differently (some
excludes) in testing phase :
${project.basedir}/src/main/java
**/*.java
service.properties
${project.basedir}/src/main/resources
**/*.xml
**/*.properties
The ideal behavior would be if one could define "src/main/*" in
but it unfortunately can't be done right now
--
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: (MEAR-135) Rationalize the management of the JavaEE version in a dedicated class
Rationalize the management of the JavaEE version in a dedicated class - Key: MEAR-135 URL: http://jira.codehaus.org/browse/MEAR-135 Project: Maven 2.x Ear Plugin Issue Type: Task Affects Versions: 2.4.2 Reporter: Stephane Nicoll Priority: Minor right now the JavaEE/J2EE version used by the plugin is a simple string. Replace that by a dedicated class offering added-values. An enum would be great but we can't yet. -- 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: (MEAR-135) Rationalize the management of the JavaEE version in a dedicated class
[ http://jira.codehaus.org/browse/MEAR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-135: - Fix Version/s: 2.5 Assignee: Stephane Nicoll > Rationalize the management of the JavaEE version in a dedicated class > - > > Key: MEAR-135 > URL: http://jira.codehaus.org/browse/MEAR-135 > Project: Maven 2.x Ear Plugin > Issue Type: Task >Affects Versions: 2.4.2 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll >Priority: Minor > Fix For: 2.5 > > > right now the JavaEE/J2EE version used by the plugin is a simple string. > Replace that by a dedicated class offering added-values. An enum would be > great but we can't yet. -- 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-200) Problem with login to jira over https and proxy
[
http://jira.codehaus.org/browse/MCHANGES-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249050#action_249050
]
Dennis Lundberg commented on MCHANGES-200:
--
nonProxyHosts is tracked in MCHANGES-60.
> Problem with login to jira over https and proxy
> ---
>
> Key: MCHANGES-200
> URL: http://jira.codehaus.org/browse/MCHANGES-200
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
> Environment: Jdk 1.6_18
> Jira Enterprise Edition, Version: 3.13.3-#344)
>Reporter: Krashan Brahmanjara
> Attachments: AbstractJiraDownloader.java
>
>
> I cannot get changes log from JIRA but url used by maven is correct.
> I mean url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> get correct xml in browsers like FF or IE however untrusted certificate info
> are displayed..
> BTW
> Login phase is very long.
> Deatils
> {noformat}
> [DEBUG] Using proxy: 10.4.1.1 at port 3118
> [DEBUG] JIRA lives at: https://jira.prv.pl
> [DEBUG] Login URL:
> https://jira.prv.pl/login.jsp?os_destination=/secure/&os_username=TR$%^&os_password=*
> [DEBUG] Successfully logged in into JIRA.
> [DEBUG] download jira issues from url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [INFO] Downloading from JIRA at:
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [WARNING] Downloading from JIRA failed. Received: [503]
> {noformat}
> Pom configuration
> {code:xml}
>
> jira
> https://jira.prv.pl/browse?id=INSCS
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.3
>
>
>
>
>
>
>
> true
>
> resolution=1&sorter/field=issuetype&sorter/order=ASC
> Closed
> x
> TR
> true
>
>
> {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] Work started: (MEAR-135) Rationalize the management of the JavaEE version in a dedicated class
[ http://jira.codehaus.org/browse/MEAR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-135 started by Stephane Nicoll. > Rationalize the management of the JavaEE version in a dedicated class > - > > Key: MEAR-135 > URL: http://jira.codehaus.org/browse/MEAR-135 > Project: Maven 2.x Ear Plugin > Issue Type: Task >Affects Versions: 2.4.2 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll >Priority: Minor > Fix For: 2.5 > > > right now the JavaEE/J2EE version used by the plugin is a simple string. > Replace that by a dedicated class offering added-values. An enum would be > great but we can't yet. -- 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-200) Problem with login to jira over https and proxy
[
http://jira.codehaus.org/browse/MCHANGES-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249051#action_249051
]
Dennis Lundberg commented on MCHANGES-200:
--
Untrusted certificates are tracked in MCHANGES-175.
> Problem with login to jira over https and proxy
> ---
>
> Key: MCHANGES-200
> URL: http://jira.codehaus.org/browse/MCHANGES-200
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
> Environment: Jdk 1.6_18
> Jira Enterprise Edition, Version: 3.13.3-#344)
>Reporter: Krashan Brahmanjara
> Attachments: AbstractJiraDownloader.java
>
>
> I cannot get changes log from JIRA but url used by maven is correct.
> I mean url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> get correct xml in browsers like FF or IE however untrusted certificate info
> are displayed..
> BTW
> Login phase is very long.
> Deatils
> {noformat}
> [DEBUG] Using proxy: 10.4.1.1 at port 3118
> [DEBUG] JIRA lives at: https://jira.prv.pl
> [DEBUG] Login URL:
> https://jira.prv.pl/login.jsp?os_destination=/secure/&os_username=TR$%^&os_password=*
> [DEBUG] Successfully logged in into JIRA.
> [DEBUG] download jira issues from url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [INFO] Downloading from JIRA at:
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [WARNING] Downloading from JIRA failed. Received: [503]
> {noformat}
> Pom configuration
> {code:xml}
>
> jira
> https://jira.prv.pl/browse?id=INSCS
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.3
>
>
>
>
>
>
>
> true
>
> resolution=1&sorter/field=issuetype&sorter/order=ASC
> Closed
> x
> TR
> true
>
>
> {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] Closed: (MCHANGES-200) Problem with login to jira over https and proxy
[
http://jira.codehaus.org/browse/MCHANGES-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-200.
Resolution: Duplicate
> Problem with login to jira over https and proxy
> ---
>
> Key: MCHANGES-200
> URL: http://jira.codehaus.org/browse/MCHANGES-200
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
> Environment: Jdk 1.6_18
> Jira Enterprise Edition, Version: 3.13.3-#344)
>Reporter: Krashan Brahmanjara
> Attachments: AbstractJiraDownloader.java
>
>
> I cannot get changes log from JIRA but url used by maven is correct.
> I mean url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> get correct xml in browsers like FF or IE however untrusted certificate info
> are displayed..
> BTW
> Login phase is very long.
> Deatils
> {noformat}
> [DEBUG] Using proxy: 10.4.1.1 at port 3118
> [DEBUG] JIRA lives at: https://jira.prv.pl
> [DEBUG] Login URL:
> https://jira.prv.pl/login.jsp?os_destination=/secure/&os_username=TR$%^&os_password=*
> [DEBUG] Successfully logged in into JIRA.
> [DEBUG] download jira issues from url
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [INFO] Downloading from JIRA at:
> https://jira.prv.pl/secure/IssueNavigator.jspa?view=rss&pid=INSCS&resolution=1&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> [WARNING] Downloading from JIRA failed. Received: [503]
> {noformat}
> Pom configuration
> {code:xml}
>
> jira
> https://jira.prv.pl/browse?id=INSCS
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.3
>
>
>
>
>
>
>
> true
>
> resolution=1&sorter/field=issuetype&sorter/order=ASC
> Closed
> x
> TR
> true
>
>
> {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] Closed: (MEAR-135) Rationalize the management of the JavaEE version in a dedicated class
[ http://jira.codehaus.org/browse/MEAR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-135. Resolution: Fixed > Rationalize the management of the JavaEE version in a dedicated class > - > > Key: MEAR-135 > URL: http://jira.codehaus.org/browse/MEAR-135 > Project: Maven 2.x Ear Plugin > Issue Type: Task >Affects Versions: 2.4.2 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll >Priority: Minor > Fix For: 2.5 > > > right now the JavaEE/J2EE version used by the plugin is a simple string. > Replace that by a dedicated class offering added-values. An enum would be > great but we can't yet. -- 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: (MCHANGES-67) The changes plugin should not hard code the "team-list.html" file
[ http://jira.codehaus.org/browse/MCHANGES-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-67. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Dennis Lundberg Patch applied with modifications in [r1050310|http://svn.apache.org/viewvc?view=revision&revision=1050310]. New 2.4-SNAPSHOT deployed. Thanks! > The changes plugin should not hard code the "team-list.html" file > -- > > Key: MCHANGES-67 > URL: http://jira.codehaus.org/browse/MCHANGES-67 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: changes.xml >Affects Versions: 2.0-beta-2, 2.0-beta-3 >Reporter: Henning Schmiedehausen >Assignee: Dennis Lundberg > Fix For: 2.4 > > Attachments: changes5.patch, MCHANGES-67.patch > > > Projects that do not have a team-list file or use a different file will have > a number of broken links on the changes-plugin report page. > The attached patch makes the URL of the team-list file configurable with the > default being the "team-list.html" file. This can be changed by setting the > > foo.html > > parameter. When this parameter is set to empty (e.g. > > > > then no link is generated and just the names are reported. -- 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-190) HTML in changes.xml stopped working
[ http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249056#action_249056 ] Lukas Theussl commented on MCHANGES-190: I don't agree with 2. I think the most transparent way *is* to change the XSD. However, I would like to see your proposed implementation first, if you can come up with an solution that doesn't need a new xsd and that satisfies everyone, I will happily accept it. :) > HTML in changes.xml stopped working > --- > > Key: MCHANGES-190 > URL: http://jira.codehaus.org/browse/MCHANGES-190 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: changes.xml >Affects Versions: 2.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_17 > OS name: "linux" version: "2.6.32-686" arch: "i386" Family: "unix" >Reporter: Christian Schulte >Priority: Critical > Attachments: changes.xml, changes.xml, MCHANGES-190.zip > > > The fix for MCHANGES-189 does not seem to be correct. A changes.xml file > containing HTML-Tags got rendered correctly using version 2.2. Starting with > version 2.3, HTML-Tags will be encoded using HTML entities for the '<' and > '>' characters leading to the actual tags getting shown in the report. See > the attached example changes.xml file containing HTML no longer working with > version 2.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] Closed: (MCHANGES-60) The jira report should handle the nonProxyHosts specified in settings.xml
[ http://jira.codehaus.org/browse/MCHANGES-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-60. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Dennis Lundberg Patch applied in [r1050910|http://svn.apache.org/viewvc?view=revision&revision=1050910]. Thanks! New 2.4-SNAPSHOT deployed - please help us test it if you have a proxy available. > The jira report should handle the nonProxyHosts specified in settings.xml > - > > Key: MCHANGES-60 > URL: http://jira.codehaus.org/browse/MCHANGES-60 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira >Affects Versions: 2.0-beta-2 > Environment: A network with a proxy to access the outside, and a JIRA > inside the network. >Reporter: Pierre-Antoine Grégoire >Assignee: Dennis Lundberg > Fix For: 2.4 > > Attachments: MNG-MCHANGES-60-MCHANGES-123-maven-changes-plugin.patch > > > These nonProxyHosts can be retrieved with the > settings.getActiveProxy().getNonProxyHosts(); > This returns a String containing a (usually?)comma-separated list of > nonProxyHosts. > If the jira URL matches one of these hosts, it should not use any proxy of > course ;). > I haven't found a nonProxyHosts concept in commons-httpclient, so it should > be checked in the determineProxy Method of AbstractJiraDownloader. > This is quickly fixed and would be very useful ;) > Thanks in advance -- 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: (MCHANGES-123) Login to remote JIRA with username and password is broken with JIRA version 3.12.3
[ http://jira.codehaus.org/browse/MCHANGES-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-123. Resolution: Cannot Reproduce I tried this on a JIRA 3.13.5 installation and it works as it is now. > Login to remote JIRA with username and password is broken with JIRA version > 3.12.3 > -- > > Key: MCHANGES-123 > URL: http://jira.codehaus.org/browse/MCHANGES-123 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.0 >Reporter: Andy Geach >Priority: Minor > Attachments: jira3.12.3_logout.html, > MNG-MCHANGES-60-MCHANGES-123-maven-changes-plugin.patch > > > The current test is for the response to be parsed for the String "your > username and password are incorrect". > In version 3.12.3 that phrase no longer appears -- 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: (MCHANGES-121) Incorrect Component value in report for multi-component JIRA issue
[ http://jira.codehaus.org/browse/MCHANGES-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-121. Resolution: Fixed Fix Version/s: 2.4 Assignee: Dennis Lundberg Fixed in [r1050925|http://svn.apache.org/viewvc?view=revision&revision=1050925]. New 2.4-SNAPSHOT deployed - please test. > Incorrect Component value in report for multi-component JIRA issue > -- > > Key: MCHANGES-121 > URL: http://jira.codehaus.org/browse/MCHANGES-121 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Reporter: David Rauschenbach >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.4 > > > I have a JIRA issue that has a multi-valued component value (eg "Component-A, > Component-B, Component-C"). I run a jira-report from my pom file with a > filter on Component-C only. The report displays the first component of a > multi-component JIRA issue, even when the displayed component does not match > one of the components in the component filter. -- 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: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources
[
http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249064#action_249064
]
Kristian Rosenvold commented on SUREFIRE-667:
-
Your issue describes only a solution without describing the actual use-case or
the problem you are trying to solve, and provides little explanation as to why
this issue should be solved; especially since most people seem to get along
fine without it.
Please add far more information about the use-case and possibly maybe also a
suggestion of why this is the appropriate way to fix this issue.
> Setting up maven resources when testing in addition to testResources
>
>
> Key: SUREFIRE-667
> URL: http://jira.codehaus.org/browse/SUREFIRE-667
> Project: Maven Surefire
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: vychtrle
>
> Hey,
> I think that developers would need resource goal of resource plugin to be set
> up differently for
> test phase, than for build phase. When testing one needs to exclude stuff
> from src/main/resources. It seems it can't be done, testResources goal
> is irrelevant for this because it can't operate on src/main/* and resource
> goal can have only one
> setting in pom definition, that takes effect in both test and build
> phase...
> For example, I'd need following settings to look differently (some
> excludes) in testing phase :
>
>
>${project.basedir}/src/main/java
>
>**/*.java
>service.properties
>
>
>
>
> ${project.basedir}/src/main/resources
>
>**/*.xml
>**/*.properties
>
>
>
> The ideal behavior would be if one could define "src/main/*" in
> but it unfortunately can't be done right now
--
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: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources
[
http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249077#action_249077
]
vychtrle commented on SUREFIRE-667:
---
Hi Kristian,
When testing, I want to exclude some src/main/resources because :
I need to use resources from project dependencies (different ones, but
same directory structure and names as some src/main/resources ), which happens
quite often to me especially when testing.
... And since the target/classes resources are loaded before dependencies ->
...they are loaded first
Sometimes the fact that target/test-classes are loaded before target/classes
isn't enough. Let say that I have 20
spring-context files in META-INF (but only 10 is used for testing) loaded from
the application.
I can't say grab all *.xml in META-INF and load spring beans when testing,
because it
would load beans from all those 20 files instead of 10. As a result I have to
hardcode
their names and everytime I make a change I have to change the code.
There are tons of such scenarios... No, it is not critical feature, but it
means a lot of
setting and workarounds...
If it is a huge project, more than 700 spring beans in various contexts, tons
of configuration etc., absence of such a feature can hurt a lot
> Setting up maven resources when testing in addition to testResources
>
>
> Key: SUREFIRE-667
> URL: http://jira.codehaus.org/browse/SUREFIRE-667
> Project: Maven Surefire
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: vychtrle
>
> Hey,
> I think that developers would need resource goal of resource plugin to be set
> up differently for
> test phase, than for build phase. When testing one needs to exclude stuff
> from src/main/resources. It seems it can't be done, testResources goal
> is irrelevant for this because it can't operate on src/main/* and resource
> goal can have only one
> setting in pom definition, that takes effect in both test and build
> phase...
> For example, I'd need following settings to look differently (some
> excludes) in testing phase :
>
>
>${project.basedir}/src/main/java
>
>**/*.java
>service.properties
>
>
>
>
> ${project.basedir}/src/main/resources
>
>**/*.xml
>**/*.properties
>
>
>
> The ideal behavior would be if one could define "src/main/*" in
> but it unfortunately can't be done right now
--
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-72) Build Failure using IBM JDK 1.4.2 SR7
[ http://jira.codehaus.org/browse/MCHANGES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249078#action_249078 ] Dennis Lundberg commented on MCHANGES-72: - In [r1050951|http://svn.apache.org/viewvc?view=revision&revision=1050951] I upgraded the plexus-mail-sender components to version 1.0-alpha-7, hoping that it will help this issue. A new 2.4-SNAPSHOT has been deployed. Please test it if you the possibility. > Build Failure using IBM JDK 1.4.2 SR7 > - > > Key: MCHANGES-72 > URL: http://jira.codehaus.org/browse/MCHANGES-72 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: announcement >Affects Versions: 2.0-beta-2 > Environment: Windows XP Pro > Maven 2.0.5 > IBM JDK 1.4.2 SR7 >Reporter: Patrick Schneider >Priority: Minor > Attachments: changes-ibmjdk.txt, MCHANGES-72.patch > > > Attached is the -e output from running 'mvn site:site'. -- 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: (MCHANGES-198) How to use
[
http://jira.codehaus.org/browse/MCHANGES-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHANGES-198:
-
Attachment: MCHANGES-198.zip
Here is a test project based on the configuration of this issue. It is working
fine for me.
> How to use
> ---
>
> Key: MCHANGES-198
> URL: http://jira.codehaus.org/browse/MCHANGES-198
> Project: Maven 2.x Changes Plugin
> Issue Type: Test
> Components: changes.xml
> Environment: Maven-2.0.9
>Reporter: Jean Pierre Urkens
>Priority: Minor
> Attachments: changes.xml, MCHANGES-198.zip
>
>
> I'm trying to configure an alternative issueManagement system.
> In the parent POM the maven-changes-plugin is configured in the reporting
> section as:
> {code:xml}
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.3
>
> true
>
>
> %URL%?func=ll&objId=%ISSUE%&objAction=BrowseTask
>
>
>
> changes-report
>
> {code}
> In the project POM I've my issueManagement system defined as:
> {code:xml}
>
> livelink
> http://safe.expandedmedia.com/livelink/livelink.exe/
>
> {code}
> Now i would expect that for all issues listed in the attached changes.xml
> that a link to my issue management system would be created but it doesn't. It
> generates the changes-report but without taking into consideration the
> parameters (not even the addActionDate) I've defined in my parent POM.
--
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: (MCHANGES-198) How to use
[
http://jira.codehaus.org/browse/MCHANGES-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-198.
Resolution: Cannot Reproduce
> How to use
> ---
>
> Key: MCHANGES-198
> URL: http://jira.codehaus.org/browse/MCHANGES-198
> Project: Maven 2.x Changes Plugin
> Issue Type: Test
> Components: changes.xml
> Environment: Maven-2.0.9
>Reporter: Jean Pierre Urkens
>Priority: Minor
> Attachments: changes.xml, MCHANGES-198.zip
>
>
> I'm trying to configure an alternative issueManagement system.
> In the parent POM the maven-changes-plugin is configured in the reporting
> section as:
> {code:xml}
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.3
>
> true
>
>
> %URL%?func=ll&objId=%ISSUE%&objAction=BrowseTask
>
>
>
> changes-report
>
> {code}
> In the project POM I've my issueManagement system defined as:
> {code:xml}
>
> livelink
> http://safe.expandedmedia.com/livelink/livelink.exe/
>
> {code}
> Now i would expect that for all issues listed in the attached changes.xml
> that a link to my issue management system would be created but it doesn't. It
> generates the changes-report but without taking into consideration the
> parameters (not even the addActionDate) I've defined in my parent POM.
--
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-4602) Allow pluggable authentication (using JAAS ?) so that the username and password to connect to a deployment repository can be generated by a Single Sign On-enabled client
[ http://jira.codehaus.org/browse/MNG-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249085#action_249085 ] David Boden commented on MNG-4602: -- I've raised https://issues.sonatype.org/browse/AETHER-54 as the enhancement will be almost entirely in Sonatype Aether. Please feel free to close this issue as "won't fix" in favour of the Aether Jira report. > Allow pluggable authentication (using JAAS ?) so that the username and > password to connect to a deployment repository can be generated by a Single > Sign On-enabled client > - > > Key: MNG-4602 > URL: http://jira.codehaus.org/browse/MNG-4602 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Artifacts and Repositories, Settings >Reporter: David Boden >Priority: Minor > > The username and password used to authenticate with the remote repository > during deployment are stored in the user's settings.xml under the > structure. This structure allows a username and password to be specified, or > for a .ssh private key to be specified. > It does not allow for pluggable single sign on, where a Java module (perhaps > a JAAS LoginModule) is available on the client to generate a token in place > of a password. Many corporates use this technique for other web applications, > generating an LDAP token from the user's PC and verifying it against an LDAP > server on the server side. It adds security by removing the need to pass the > user's password over the wire. > This Jira is a request for a pluggable entry point for this single sign on > module, perhaps by specifying a class name in the structure or by > setting a system property. The solution could either define a new interface > which Authentication Providers must implement or can use existing interfaces > from JAAS, (Http) Authenticator or other frameworks. > Please feel free to move this item to the "Maven Wagon" component if you feel > that's the best place to implement the feature. Alternatively, please also > feel free to move to the generic "Maven 2&3" component if you think that the > feature has wider scope than just deployment; perhaps to also authenticate > using Single Sign On with an internal company's repository when *downloading* > artifacts (as well as uploading). -- 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-4938) pom missing [WARNING] displayed even if it's available
[ http://jira.codehaus.org/browse/MNG-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Moser updated MNG-4938: - Attachment: settings.xml a stripped down version of my global settings.xml file. > pom missing [WARNING] displayed even if it's available > -- > > Key: MNG-4938 > URL: http://jira.codehaus.org/browse/MNG-4938 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.1 > Environment: Win 7 x32 >Reporter: Christian Moser >Assignee: Benjamin Bentmann > Attachments: reproduce.zip, settings.xml > > > The error message is displayed everytime after a SUCCESSFUL build (phase > install) of every delivered sample project despite deps-libs. > Steps for reproducing: > deploy selenium-java-client-driver by hand (webinterface) into artifactory > repository 2.3.1 (didn't test it with nexus) > install projects in the following order: deps-libs, libs-parent, libs-child, > libs-comp > The message should be displayed at the end of the build > [WARNING] The POM for re.produce:selenium-java-client-driver:jar:1.0.1 is > missing, no dependency information available. > This only happens with artifacts which were deployed by hand, i'm curious if > this will also happen with nexus. -- 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-4938) pom missing [WARNING] displayed even if it's available
[ http://jira.codehaus.org/browse/MNG-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Moser updated MNG-4938: - Attachment: log-download.txt log.txt Full debug log files of libs-comp project: log.txt shows install with selenium artifact located in the local repository log-download.txt shows install with resolution of selenium artifact from remote repository pcsoft.internal > pom missing [WARNING] displayed even if it's available > -- > > Key: MNG-4938 > URL: http://jira.codehaus.org/browse/MNG-4938 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.1 > Environment: Win 7 x32 >Reporter: Christian Moser >Assignee: Benjamin Bentmann > Attachments: log-download.txt, log.txt, reproduce.zip, settings.xml > > > The error message is displayed everytime after a SUCCESSFUL build (phase > install) of every delivered sample project despite deps-libs. > Steps for reproducing: > deploy selenium-java-client-driver by hand (webinterface) into artifactory > repository 2.3.1 (didn't test it with nexus) > install projects in the following order: deps-libs, libs-parent, libs-child, > libs-comp > The message should be displayed at the end of the build > [WARNING] The POM for re.produce:selenium-java-client-driver:jar:1.0.1 is > missing, no dependency information available. > This only happens with artifacts which were deployed by hand, i'm curious if > this will also happen with nexus. -- 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
