[jira] Commented: (MWAR-253) Inherit dependencies from a WAR type dependency when it is overlayed.
[ http://jira.codehaus.org/browse/MWAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269532#action_269532 ] Maarten Billemont commented on MWAR-253: The plugin provides the ability to overlay one WAR with another. Such an overlay implies that the latter WAR's classes function, at runtime, in the same classpath. The WAR plugin however fails to reflect this at compile-time. It does not set the compile-time classpath for the artifact according to what is needed to properly compile its classes, which would otherwise work fine at runtime thanks to the overlaying. In that sense, this is a bug with regards to the overlay functionality in the WAR plugin neglecting to reflect its effects at compile-time, as it does at run-time. > Inherit dependencies from a WAR type dependency when it is overlayed. > - > > Key: MWAR-253 > URL: http://jira.codehaus.org/browse/MWAR-253 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Maarten Billemont > > When WAR artifact B depends on WAR artifact A, and also defines an overlay of > A, B should inherit all A's dependencies. > This issue is related to MNG-1991, but can be resolved without much > discussion as it's unrelated to skinny WARs and such. > Classes in B are guaranteed to have runtime access to all A's declared > dependencies when A is an overlay of B. -- 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-5112) Issue MNG-4147 re-current in maven 3.0.3
Issue MNG-4147 re-current in maven 3.0.3 Key: MNG-5112 URL: http://jira.codehaus.org/browse/MNG-5112 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0.3 Reporter: Brett Sutton The reported issue MNG-4147 'very long passwords cause LightweightHTTP wagon to line-wrap the Base64-encoded Authorization header' which is apparently fixed in Maven 2.2.0 appears to have re-occurred in maven 3.0.3. My understanding that the original issue was never actually fixed but rather a work-around was provided which allowed users to switch wagon providers. Maven 3.0.3 doesn't appear to allow the switching of providers which means that the default lightweighthttp provider is used. Given that the bug still exists in the lightweight provider we appear to be back to square one. Is there still a way to switch providers? After several hours of searching I was unable to find a way to switch in 3.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] Closed: (MSITE-586) maven-site-plugin > 2.0 breaks Doxia sink elements
[ http://jira.codehaus.org/browse/MSITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-586. --- Resolution: Not A Bug Assignee: Lukas Theussl > maven-site-plugin > 2.0 breaks Doxia sink elements > - > > Key: MSITE-586 > URL: http://jira.codehaus.org/browse/MSITE-586 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Joshua Hyde >Assignee: Lukas Theussl > Attachments: doxia-bug-test.zip > > > For reasons that I've been unable to yet discern, my reporting plugin fails > to work properly if anything in the 2.x stream (beyond 2.0) is present in the > POM. > I'm attaching a project that demonstrates this. Run "mvn clean test site" and > view the "JETM Timing Report" under Project Reports. Then, run "mvn clean > test site -Pbreak" and view the same report - the generated HTML has the /> elements outside of the definition. -- 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-586) maven-site-plugin > 2.0 breaks Doxia sink elements
[
http://jira.codehaus.org/browse/MSITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269533#action_269533
]
Lukas Theussl commented on MSITE-586:
-
This is not a bug in the site plugin, rather an incorrect use of the doxia-sink
API by the jetm-maven-plugin, and doxia-1.1 (used since site-plugin-2.1) is
just much more strict about that. The relevant sequence of events in
[TimingReportMojo|http://code.google.com/p/jetm-maven-plugin/source/browse/trunk/jetm-maven-plugin/src/main/java/com/google/code/jetm/maven/TimingReportMojo.java]
is
{noformat}
sink.table();
tableHeaderCell(sink, "Name");
...
for (Aggregate aggregate : aggregates) {
sink.tableRow();
tableCell(sink, aggregate.getName());
...
sink.tableRow_();
}
sink.table_();
{noformat}
It should be correctly:
{noformat}
sink.table();
sink.tableRows( justify, grid );
sink.tableRow();
tableHeaderCell(sink, "Name");
...
sink.tableRow_();
for (Aggregate aggregate : aggregates) {
sink.tableRow();
tableCell(sink, aggregate.getName());
...
sink.tableRow_();
}
sink.tableRows_();
sink.table_();
{noformat}
> maven-site-plugin > 2.0 breaks Doxia sink elements
> -
>
> Key: MSITE-586
> URL: http://jira.codehaus.org/browse/MSITE-586
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0.1
>Reporter: Joshua Hyde
> Attachments: doxia-bug-test.zip
>
>
> For reasons that I've been unable to yet discern, my reporting plugin fails
> to work properly if anything in the 2.x stream (beyond 2.0) is present in the
> POM.
> I'm attaching a project that demonstrates this. Run "mvn clean test site" and
> view the "JETM Timing Report" under Project Reports. Then, run "mvn clean
> test site -Pbreak" and view the same report - the generated HTML has the /> elements outside of the definition.
--
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: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
Documentation bug - "Closed" is not a resolutionID
---
Key: MCHANGES-253
URL: http://jira.codehaus.org/browse/MCHANGES-253
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.5
Environment:
http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
Reporter: SebbASF
The page
http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
says:
{quote}
Using Maven syntax
In the following example we are only including issues that have Closed as their
resolution.
{quote}
However, as far as I can tell, Closed is not a valid Resolution type.
It should probably be "Fixed".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-681) maven throws a java.lang.NullPointerException at the end of a release:perform
[ http://jira.codehaus.org/browse/MRELEASE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khai Do closed MRELEASE-681. Resolution: Cannot Reproduce Fix Version/s: 2.1 I think i understand what happened. I ran into this problem because, by default, maven-2.2.1 uses the maven-release-plugin-2.0-beta-8 vesion of the plugin. The fix to this problem occurred in beta-9 so it makes sense. Isn't maven supposed to use the latest version of the plugin if it's not specified in the pom file? Anyways, I could not reproduce after specifically adding the release plugin to my pom and telling it to use the the maven-release-plugin-2.1 version. Sorry for the inconvenience. > maven throws a java.lang.NullPointerException at the end of a release:perform > - > > Key: MRELEASE-681 > URL: http://jira.codehaus.org/browse/MRELEASE-681 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.2 > Environment: maven 2.2.1, java 1.6_23 on windows 7 64 bit >Reporter: Khai Do >Priority: Minor > Fix For: 2.1 > > Attachments: maven-log.txt > > > I'm getting java.lang.NullPointerException when building when i reference > maven-release-plugin in my pom.xml, It doesn't seem to matter which version > of the plugin i reference. i'm using maven 2.2.1, java 1.6_23 on windows 7 64 > bit. I can also repro on linux. > The only way it works without error is if I specify 2.0-beta-9 from the > command line: > mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform > -DconnectionUrl=.. > It fails if I do this: > mvn org.apache.maven.plugins:maven-release-plugin:2.1:perform > -DconnectionUrl=.. > It also fails when I reference 2.0-beta-9 in my pom.xml then run: > mvn relase:perform -DconnectionUrl=.. -- 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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269537#action_269537
]
SebbASF commented on MCHANGES-253:
--
http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html says:
Valid resolutions are: Unresolved, Fixed, Won't Fix, Duplicate, Incomplete and
Cannot Reproduce.
which does not include "Closed".
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MDEPLOY-132) Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters
[ http://jira.codehaus.org/browse/MDEPLOY-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MDEPLOY-132. Resolution: Fixed Fix Version/s: 2.7 1131407. Improved documentation. > Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters > -- > > Key: MDEPLOY-132 > URL: http://jira.codehaus.org/browse/MDEPLOY-132 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug > Components: deploy:deploy-file >Affects Versions: 2.6 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.7 > > > It is confusing, at least to me, that the pom says, 'foo' but > the deploy-file parameter is -Dpackaging=. I'll post up a patch to add > -Dtype= if I get the slightest encouragement here. -- 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: (MCHANGES-254) Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma
Example doesn't work - spaces not allowed in statusIds and resolutionIds after
a comma
--
Key: MCHANGES-254
URL: http://jira.codehaus.org/browse/MCHANGES-254
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.5
Environment:
http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
Reporter: SebbASF
http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax
gives the following examples:
{quote}
Closed
Resolved, Closed
Bug, New Feature, Improvement, Wish
{quote}
However, spaces are not always allowed, they can cause the field to be ignored.
Resolved,Closed - OK
Resolved,Closed - OK
Resolved,Closed - OK
Resolved,Closed - OK
Resolved, Closed - Closed is ignored
Resolved, Closed - Closed is ignored
Resolved, Closed - Closed is ignored
In particular, the example from the web page does not work.
Note that the typeIds field does appear to allow leading space after a comma.
The resolutionIds field does not.
Since spaces are sometimes allowed, may I suggest the code is fixed rather than
the documentation?
--
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-586) maven-site-plugin > 2.0 breaks Doxia sink elements
[ http://jira.codehaus.org/browse/MSITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269540#action_269540 ] Joshua Hyde commented on MSITE-586: --- Ah, thank you very much. > maven-site-plugin > 2.0 breaks Doxia sink elements > - > > Key: MSITE-586 > URL: http://jira.codehaus.org/browse/MSITE-586 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Joshua Hyde >Assignee: Lukas Theussl > Attachments: doxia-bug-test.zip > > > For reasons that I've been unable to yet discern, my reporting plugin fails > to work properly if anything in the 2.x stream (beyond 2.0) is present in the > POM. > I'm attaching a project that demonstrates this. Run "mvn clean test site" and > view the "JETM Timing Report" under Project Reports. Then, run "mvn clean > test site -Pbreak" and view the same report - the generated HTML has the /> elements outside of the definition. -- 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-254) Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma
[
http://jira.codehaus.org/browse/MCHANGES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MCHANGES-254:
--
Fix Version/s: 2.6
> Example doesn't work - spaces not allowed in statusIds and resolutionIds
> after a comma
> --
>
> Key: MCHANGES-254
> URL: http://jira.codehaus.org/browse/MCHANGES-254
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax
> gives the following examples:
> {quote}
>
> Closed
> Resolved, Closed
> Bug, New Feature, Improvement, Wish
>
> {quote}
> However, spaces are not always allowed, they can cause the field to be
> ignored.
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> In particular, the example from the web page does not work.
> Note that the typeIds field does appear to allow leading space after a comma.
> The resolutionIds field does not.
> Since spaces are sometimes allowed, may I suggest the code is fixed rather
> than the documentation?
--
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: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4
fixVersionIds supports human readable display versions in JIRA 4 Key: MCHANGES-255 URL: http://jira.codehaus.org/browse/MCHANGES-255 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.5 Reporter: SebbASF http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds says bq. Sets the fix version id(s) that you want to limit your report to include. These are JIRA's internal version ids, NOT the human readable display ones. This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human readable versions. It would be helpful to document how to obtain the internal version ids, if these are still supported or needed. -- 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-255) fixVersionIds supports human readable display versions in JIRA 4
[ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269541#action_269541 ] Benson Margulies commented on MCHANGES-255: --- Once could, but there's no JIRA API to obtain them, and it would be a big job to add jira-4-specific querying. Obtaining them is a matter of waving your mouse over an obscure location in jira. > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: http://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- 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-254) Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma
[
http://jira.codehaus.org/browse/MCHANGES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-254.
-
Resolution: Fixed
1131414
> Example doesn't work - spaces not allowed in statusIds and resolutionIds
> after a comma
> --
>
> Key: MCHANGES-254
> URL: http://jira.codehaus.org/browse/MCHANGES-254
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax
> gives the following examples:
> {quote}
>
> Closed
> Resolved, Closed
> Bug, New Feature, Improvement, Wish
>
> {quote}
> However, spaces are not always allowed, they can cause the field to be
> ignored.
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved,Closed - OK
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> Resolved, Closed - Closed is ignored
> In particular, the example from the web page does not work.
> Note that the typeIds field does appear to allow leading space after a comma.
> The resolutionIds field does not.
> Since spaces are sometimes allowed, may I suggest the code is fixed rather
> than the documentation?
--
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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
1131414
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MCHANGES-253:
--
Fix Version/s: 2.6
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-255) fixVersionIds supports human readable display versions in JIRA 4
[ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269544#action_269544 ] SebbASF commented on MCHANGES-255: -- I meant the last sentence as an additional fix item. The main issue is that the doc says that one has to use the internal ID, but AFAICT that's not necessary - or even true anymore. The documentation needs to be updated to make this clear. > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: http://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- 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] Reopened: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebbASF reopened MCHANGES-253:
--
AFAICT the following text has not been fixed:
bq. In the following example we are only including issues that have Closed as
their resolution.
Closed should be Fixed here as well
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
Once more with feeling.
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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] Reopened: (MCHANGES-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebbASF reopened MCHANGES-253:
--
Sorry, but there is still an incorrect mention of closed - I've just checked in
the current source, i.e.
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-changes-plugin/src/site/apt/examples/customizing-jira-report.apt.vm?revision=1131414
{quote}
** Using Maven syntax
In the following example we are only including issues that have as
their resolution. The status must be either or . Only
...
Fixed
Resolved, Closed
...
{quote}
Closed is not valid as a resolution.
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-245) Custom mapping of IMS issue types to action types for announcements
[ http://jira.codehaus.org/browse/MCHANGES-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-245. - Resolution: Fixed Fix Version/s: 2.6 Patch applied rev 1131456. Thanks. > Custom mapping of IMS issue types to action types for announcements > --- > > Key: MCHANGES-245 > URL: http://jira.codehaus.org/browse/MCHANGES-245 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.4 >Reporter: Alan Parkinson > Fix For: 2.6 > > Attachments: MCHANGES-245-maven-changes-plugin.patch > > > The current version only maps "Bug", "New Feature" and "Improvement" issues > types to "fix", "add" and "update" actions. If the issue type from the IMS > isn't recognized the default action type is blank and this leads to the issue > not being included within the announcement when using the default template. > This set of supported issue types can be limiting with a modern JIRA > installation as is it has a greater range of issue types and can be extended > with additional types. The most flexible solution for JIRA and other IMSes > would be to allow the the mapping of issue types to action types. -- 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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHANGES-253.
-
Resolution: Fixed
Really, I did fix it.
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269552#action_269552
]
Benson Margulies commented on MCHANGES-253:
---
Sebb, I fixed it in 1131454 after your last reopen.
** Using Maven syntax
In the following example we are only including issues that have as
their resolution. The status must be either or . Only
issues with one of the types , , or are
included in the report.
+-+
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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-248) Support custom jira status ids, please
[ http://jira.codehaus.org/browse/MCHANGES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-248. - Resolution: Fixed Fix Version/s: 2.6 rev 1131459. > Support custom jira status ids, please > -- > > Key: MCHANGES-248 > URL: http://jira.codehaus.org/browse/MCHANGES-248 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira >Affects Versions: 2.5 >Reporter: Benson Margulies > Fix For: 2.6 > > Attachments: MCHANGES-248.patch > > > It is possible to add status IDs to JIRA. e.g., Verified. There is currently > no way to make these work with the changes plugin. -- 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-253) Documentation bug - "Closed" is not a resolutionID
[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269555#action_269555
]
SebbASF commented on MCHANGES-253:
--
Sorry, that was not clear to me from your comment - it did not mention a
further SVN update
(and then I messed up by not looking at the HEAD version which would have shown
what had happened).
> Documentation bug - "Closed" is not a resolutionID
> ---
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>Reporter: SebbASF
>Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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: (MCHANGES-256) Test case for UTF-8 -- 海龟一路下跌。
Test case for UTF-8 -- 海龟一路下跌。 --- Key: MCHANGES-256 URL: http://jira.codehaus.org/browse/MCHANGES-256 Project: Maven 2.x Changes Plugin Issue Type: Wish Affects Versions: 2.5 Reporter: Benson Margulies This jira is here to allow testing of the plugin with some UTF-8. 海龟一路下跌。 -- 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-251) Tolerate novel issue types
[ http://jira.codehaus.org/browse/MCHANGES-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-251. Resolution: Duplicate > Tolerate novel issue types > --- > > Key: MCHANGES-251 > URL: http://jira.codehaus.org/browse/MCHANGES-251 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.5 >Reporter: Benson Margulies > Attachments: types.patch > > > If the plugin encounters an issue with a type it's never met, the issue gets > dropped on the ground. > Calling such issues 'fix' results in something useful in the announcement, > even if it's not ideal. -- 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-245) Custom mapping of IMS issue types to action types for announcements
[ http://jira.codehaus.org/browse/MCHANGES-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269557#action_269557 ] Dennis Lundberg commented on MCHANGES-245: -- Alan and Benson, I'm not feeling comfortable with the patch that was applied for a couple of reasons. * The new parameter in AnnouncementMojo.java needs an example of how one would configure the plugin to add mappings. * The changes to IssueAdapter is not the right way to go. We need to figure out a way to extract the mapping (default values and such) to a class for a specific IMS. This patch exposes the current (not so good) implementation, by adding new public methods. Instead we should create a JIRAAdapter or something similar that can create a mapping Map, which can be used as an input parameter for the IssueAdapter class. For the last two releases of the plugin I've been working to try to abstract away the IMS implementation details as much as possible into helper classes and adapters. The goal is to eventually create an IMS API. Therefor I review every change with that in mind. > Custom mapping of IMS issue types to action types for announcements > --- > > Key: MCHANGES-245 > URL: http://jira.codehaus.org/browse/MCHANGES-245 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.4 >Reporter: Alan Parkinson > Fix For: 2.6 > > Attachments: MCHANGES-245-maven-changes-plugin.patch > > > The current version only maps "Bug", "New Feature" and "Improvement" issues > types to "fix", "add" and "update" actions. If the issue type from the IMS > isn't recognized the default action type is blank and this leads to the issue > not being included within the announcement when using the default template. > This set of supported issue types can be limiting with a modern JIRA > installation as is it has a greater range of issue types and can be extended > with additional types. The most flexible solution for JIRA and other IMSes > would be to allow the the mapping of issue types to action types. -- 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-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 ] Benson Margulies closed MCHANGES-168. - Resolution: Fixed Fix Version/s: 2.6 fixed in 1131489. > 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 >Assignee: Benson Margulies > Fix For: 2.6 > > 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] Commented: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4
[ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269559#action_269559 ] Benson Margulies commented on MCHANGES-255: --- I added doc on how to obtain the numbers from JIRA. I'm leaving this open for the broader question of exploiting JIRA 4 query language. > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: http://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- 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-175) Allow accessing JIRA instances that use untrusted certificates
[ http://jira.codehaus.org/browse/MCHANGES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269560#action_269560 ] Benson Margulies commented on MCHANGES-175: --- Unfortunately, this patch has gone stale due to intervening changes. Could you possibly update it? > Allow accessing JIRA instances that use untrusted certificates > -- > > Key: MCHANGES-175 > URL: http://jira.codehaus.org/browse/MCHANGES-175 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: jira >Affects Versions: 2.1 >Reporter: Krishna Pothula >Priority: Critical > Attachments: patch_MCHANGES-175.diff > > > We have an intranet Jira setup with https to have integration with LDAP. The > certificate used is an internal one not issued by any CA. > While accessing this repository jira-report throws below Exception: > --- > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) > at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) > at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) > at > org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) > -- 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] [Resolved] (MPOM-11) Update to compile with/for java1.5
[ https://issues.apache.org/jira/browse/MPOM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved MPOM-11. -- Resolution: Fixed set up in rev 1131491 > Update to compile with/for java1.5 > -- > > Key: MPOM-11 > URL: https://issues.apache.org/jira/browse/MPOM-11 > Project: Maven POM > Issue Type: Improvement >Affects Versions: MAVEN-19 >Reporter: Benson Margulies > Fix For: MAVEN-20 > > > Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-11) Update to compile with/for java1.5
Update to compile with/for java1.5 -- Key: MPOM-11 URL: https://issues.apache.org/jira/browse/MPOM-11 Project: Maven POM Issue Type: Improvement Affects Versions: MAVEN-19 Reporter: Benson Margulies Fix For: MAVEN-20 Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-4) source jars are not signed when releasing maven-indexer
[ https://issues.apache.org/jira/browse/MPOM-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-4: Component/s: asf > source jars are not signed when releasing maven-indexer > --- > > Key: MPOM-4 > URL: https://issues.apache.org/jira/browse/MPOM-4 > Project: Maven POM > Issue Type: Bug > Components: asf >Reporter: Olivier Lamy > > The sources plugin runs after the gpg plugin. > They both run in the verify phase. > Brian Demers added a comment - 19/Nov/10 2:00 PM > This is not actually a bug, I was just trying to track the changes needed to > the parent poms > Brian Demers added a comment - 19/Nov/10 2:40 PM > Benjamin pointed out that the indexer pom was redefining the sources plugin > config. ( I didn't notice this ) So the parent changes are fine, it changes > the gpg version to 1.1. > I will remove the extra sources plugin config from the indexer pom -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-3) Support additional boilerplate in NOTICE file
[ https://issues.apache.org/jira/browse/MPOM-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-3: Component/s: asf > Support additional boilerplate in NOTICE file > - > > Key: MPOM-3 > URL: https://issues.apache.org/jira/browse/MPOM-3 > Project: Maven POM > Issue Type: Improvement > Components: asf >Reporter: Olivier Lamy > > The pom includes using the maven-remote-resources-plugin to get the > resourceBundle org.apache:apache-jar-resource-bundle:1.4 which has the > "Standard" LICENSE, NOTICE, and DEPENDENCIES .vm files. > The DEPENDENCIES.vm file has already the function at the end to add > user-defined boilerplate: > #if($postDepListText) > $postDepListText > #end > It would be very useful to us to have similar code at the end of the > NOTICE.vm file: > #if($project.properties.postNoticeText) > $project.properties.postNoticeText > #end > The use case is we have many files which have the same copyright notice moved > to the NOTICES file, and would like to automatically have this included. By > doing this, we can define a common parent-pom for these files, which defines > the postNoticeText property, and have it included. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-8) Add snapshot repository as plugin repository
[ https://issues.apache.org/jira/browse/MPOM-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-8: Component/s: asf > Add snapshot repository as plugin repository > > > Key: MPOM-8 > URL: https://issues.apache.org/jira/browse/MPOM-8 > Project: Maven POM > Issue Type: Improvement > Components: asf >Affects Versions: ASF-9 >Reporter: Carsten Ziegeler > > The parent pom only adds the Apache snapshot repo as a repo for artifacts but > not for plugins. Adding this block, allows to use snapshots of plugins: > > > apache.snapshots > Apache Snapshot Repository > http://repository.apache.org/snapshots > > false > > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-1: Component/s: asf > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug > Components: asf >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-10) Apache Parent POM 9 apache-release profile issues
[ https://issues.apache.org/jira/browse/MPOM-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-10: - Component/s: asf > Apache Parent POM 9 apache-release profile issues > - > > Key: MPOM-10 > URL: https://issues.apache.org/jira/browse/MPOM-10 > Project: Maven POM > Issue Type: Bug > Components: asf >Reporter: Sebb > > The apache-release profile creates a zip archive of all the contents of the > current directory tree (excluding SVN and target). > This includes some files that should not be present in the zip, e.g. .pmd, > .fbprefs, and DOAP files. > These should be excluded from the archive. > Also, the profile does not create a tar.gz version of source archive. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-9) Apache Parent POM 9 does not allow override of in apache-release profile
[
https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MPOM-9:
Component/s: asf
> Apache Parent POM 9 does not allow override of in apache-release
> profile
> ---
>
> Key: MPOM-9
> URL: https://issues.apache.org/jira/browse/MPOM-9
> Project: Maven POM
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-9
>Reporter: Sebb
>Assignee: Olivier Lamy
>Priority: Critical
>
> The apache-release profile contains the following settings:
> org.apache.maven.plugins
> maven-gpg-plugin
>
> ${gpg.passphrase}
> true
>
> This is bad, because it unconditionally forces the use of an agent which may
> not be appropriate for all use cases.
> The code should use the relevant property, i.e.
>
> true
> ...
>
> ...
> org.apache.maven.plugins
> maven-gpg-plugin
>
> ${gpg.passphrase}
> ${gpg.useagent}
>
> This would still default to true, but would allow command-line override.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-11) Update to compile with/for java1.5
[ https://issues.apache.org/jira/browse/MPOM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-11: - Component/s: maven > Update to compile with/for java1.5 > -- > > Key: MPOM-11 > URL: https://issues.apache.org/jira/browse/MPOM-11 > Project: Maven POM > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-19 >Reporter: Benson Margulies > Fix For: MAVEN-20 > > > Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-7) Apache Parent Pom should be properly documented
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MPOM-7: Component/s: asf > Apache Parent Pom should be properly documented > --- > > Key: MPOM-7 > URL: https://issues.apache.org/jira/browse/MPOM-7 > Project: Maven POM > Issue Type: Improvement > Components: asf >Reporter: Sebb >Assignee: Olivier Lamy > Fix For: ASF-9 > > Attachments: asf-pom.patch > > > There does not appear to be any documentation on the Apache Parent Pom. > Please can the following be added to the next release: > * how to report issues > * where to find the source > Ideally there should be a page on the Maven web-site that documents it as > well. > In which case please link to that from the POM as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-11) Update to compile with/for java1.5
[ https://issues.apache.org/jira/browse/MPOM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044399#comment-13044399 ] Hudson commented on MPOM-11: Integrated in maven-parent #32 (See [https://builds.apache.org/hudson/job/maven-parent/32/]) [MPOM-11] update to java 1.5, and remove tabs bimargulies : Files : * /maven/pom/trunk/maven/pom.xml > Update to compile with/for java1.5 > -- > > Key: MPOM-11 > URL: https://issues.apache.org/jira/browse/MPOM-11 > Project: Maven POM > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-19 >Reporter: Benson Margulies > Fix For: MAVEN-20 > > > Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-11) Update to compile with/for java1.5
[ https://issues.apache.org/jira/browse/MPOM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044410#comment-13044410 ] Hudson commented on MPOM-11: Integrated in maven-parent #33 (See [https://builds.apache.org/hudson/job/maven-parent/33/]) [MPOM-11] add some site doc to note the change to 1.5 bimargulies : Files : * /maven/pom/trunk/maven/pom.xml * /maven/pom/trunk/maven/src/site/apt/index.apt * /maven/pom/trunk/maven/src/site/apt > Update to compile with/for java1.5 > -- > > Key: MPOM-11 > URL: https://issues.apache.org/jira/browse/MPOM-11 > Project: Maven POM > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-19 >Reporter: Benson Margulies > Fix For: MAVEN-20 > > > Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-7) Apache Parent Pom should be properly documented
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044411#comment-13044411 ] Hudson commented on MPOM-7: --- Integrated in ASF Parent Pom #19 (See [https://builds.apache.org/hudson/job/ASF%20Parent%20Pom/19/]) [MPOM-7]: first whack at documentation in here bimargulies : Files : * /maven/pom/trunk/asf/src/site/apt * /maven/pom/trunk/asf/src/site/site.xml * /maven/pom/trunk/asf/src * /maven/pom/trunk/asf/src/site/apt/index.apt * /maven/pom/trunk/asf/src/site * /maven/pom/trunk/asf/pom.xml > Apache Parent Pom should be properly documented > --- > > Key: MPOM-7 > URL: https://issues.apache.org/jira/browse/MPOM-7 > Project: Maven POM > Issue Type: Improvement > Components: asf >Reporter: Sebb >Assignee: Olivier Lamy > Fix For: ASF-9 > > Attachments: asf-pom.patch > > > There does not appear to be any documentation on the Apache Parent Pom. > Please can the following be added to the next release: > * how to report issues > * where to find the source > Ideally there should be a page on the Maven web-site that documents it as > well. > In which case please link to that from the POM as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4
[ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269562#action_269562 ] SebbASF commented on MCHANGES-255: -- It would be helpful to have the SVN references for the updates. > fixVersionIds supports human readable display versions in JIRA 4 > > > Key: MCHANGES-255 > URL: http://jira.codehaus.org/browse/MCHANGES-255 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: SebbASF > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds > says > bq. Sets the fix version id(s) that you want to limit your report to include. > These are JIRA's internal version ids, NOT the human readable display ones. > This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human > readable versions. > It would be helpful to document how to obtain the internal version ids, if > these are still supported or needed. -- 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: (MCHANGES-257) Improve filter documentation
Improve filter documentation Key: MCHANGES-257 URL: http://jira.codehaus.org/browse/MCHANGES-257 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: jira Affects Versions: 2.5 Environment: http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#filter Reporter: SebbASF [1] http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#filter and [2] http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_JIRA_syntax [1] says: bq. The filter parameter uses the same format of url parameters that is used in a JIRA search. However, it fails to mention that the first & needs to be omitted. And does not document what happens if used in conjunction with other forms of filter. [2] compares the Jira filter with the Maven-style filter. However, the Jira filter includes more than the Maven filter, as it can also be used to define sorting. Indeed it appears that the Jira filter overrids all the Maven filters and the sort column names -- 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: (MCHANGES-258) Allow fixVersionIds to specify 'non-EMPTY'
Allow fixVersionIds to specify 'non-EMPTY' -- Key: MCHANGES-258 URL: http://jira.codehaus.org/browse/MCHANGES-258 Project: Maven 2.x Changes Plugin Issue Type: New Feature Components: jira Affects Versions: 2.5 Reporter: SebbASF It would be useful if the fixVersionIds parameter had a way of specifying non-empty fix versions. -- 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] (MPOM-11) Update to compile with/for java1.5
[ https://issues.apache.org/jira/browse/MPOM-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044421#comment-13044421 ] Hudson commented on MPOM-11: Integrated in maven-parent #34 (See [https://builds.apache.org/hudson/job/maven-parent/34/]) [MPOM-11]: reapply the trivial change the the issueManagement URL [MPOM-11] Undo accidental reformatting. bimargulies : Files : * /maven/pom/trunk/maven/pom.xml bimargulies : Files : * /maven/pom/trunk/maven/pom.xml > Update to compile with/for java1.5 > -- > > Key: MPOM-11 > URL: https://issues.apache.org/jira/browse/MPOM-11 > Project: Maven POM > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-19 >Reporter: Benson Margulies > Fix For: MAVEN-20 > > > Let's make the default compile environment for all of maven be Java 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4792) Preemptive authentication doesn't work
[ http://jira.codehaus.org/browse/MNG-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269567#action_269567 ] Chris Tanger commented on MNG-4792: --- I'm also experiencing this issue with maven 2.2.1 with a Nexus server on the back. I have sniffed the http communications and the preemptive authentication configuration is indeed being ignored. > Preemptive authentication doesn't work > -- > > Key: MNG-4792 > URL: http://jira.codehaus.org/browse/MNG-4792 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.1 > Environment: Sun Java 1.6.0_21, Windows 7 >Reporter: Marcin Zajaczkowski > > It seems preemptive authentication in Maven using httpclient wagon provider > doesn't work. With configuration taken form [1] Maven knock to repository > (tested with Artifactory 2.2.5) as anonymous user. > > repo-id > user > pass > > httpclient > > > > > http.authentication.preemptive > %b,true > > > > > > > Confirmed by independent party also with Maven 2.2.1. I can sniff http > traffic if needed. > [1] - http://maven.apache.org/guides/mini/guide-http-settings.html -- 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] Issue Comment Edited: (MNG-4792) Preemptive authentication doesn't work
[ http://jira.codehaus.org/browse/MNG-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269567#action_269567 ] Chris Tanger edited comment on MNG-4792 at 6/4/11 10:38 PM: I'm also experiencing this issue with maven 2.2.1 with a Nexus server on the back. I have sniffed the http communications and the preemptive authentication configuration is indeed being ignored. Furthermore it appears that the expect 100-continue functionality isn't working properly either. Protocol inspection reveals that even when 100-continue is sent in the header the payload is still sent. Naturally this leads to a bad checksum computation on the server since the first request is denied with 401 since preemptive authentication doesn't work. was (Author: tangercp): I'm also experiencing this issue with maven 2.2.1 with a Nexus server on the back. I have sniffed the http communications and the preemptive authentication configuration is indeed being ignored. > Preemptive authentication doesn't work > -- > > Key: MNG-4792 > URL: http://jira.codehaus.org/browse/MNG-4792 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.1 > Environment: Sun Java 1.6.0_21, Windows 7 >Reporter: Marcin Zajaczkowski > > It seems preemptive authentication in Maven using httpclient wagon provider > doesn't work. With configuration taken form [1] Maven knock to repository > (tested with Artifactory 2.2.5) as anonymous user. > > repo-id > user > pass > > httpclient > > > > > http.authentication.preemptive > %b,true > > > > > > > Confirmed by independent party also with Maven 2.2.1. I can sniff http > traffic if needed. > [1] - http://maven.apache.org/guides/mini/guide-http-settings.html -- 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] Issue Comment Edited: (MNG-4792) Preemptive authentication doesn't work
[ http://jira.codehaus.org/browse/MNG-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269567#action_269567 ] Chris Tanger edited comment on MNG-4792 at 6/4/11 10:45 PM: I'm also experiencing this issue with maven 2.2.1 with a Nexus server on the back. I have sniffed the http communications and the preemptive authentication configuration is indeed being ignored. Furthermore it appears that the expect 100-continue functionality isn't working properly either. Protocol inspection reveals that even when 100-continue is sent in the header the payload is still sent. Naturally this leads to a bad checksum computation on the server since the first request is denied with 401 since preemptive authentication doesn't work. Note: We are using a username and maven encrypted password in the server section of settings.xml. was (Author: tangercp): I'm also experiencing this issue with maven 2.2.1 with a Nexus server on the back. I have sniffed the http communications and the preemptive authentication configuration is indeed being ignored. Furthermore it appears that the expect 100-continue functionality isn't working properly either. Protocol inspection reveals that even when 100-continue is sent in the header the payload is still sent. Naturally this leads to a bad checksum computation on the server since the first request is denied with 401 since preemptive authentication doesn't work. > Preemptive authentication doesn't work > -- > > Key: MNG-4792 > URL: http://jira.codehaus.org/browse/MNG-4792 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.1 > Environment: Sun Java 1.6.0_21, Windows 7 >Reporter: Marcin Zajaczkowski > > It seems preemptive authentication in Maven using httpclient wagon provider > doesn't work. With configuration taken form [1] Maven knock to repository > (tested with Artifactory 2.2.5) as anonymous user. > > repo-id > user > pass > > httpclient > > > > > http.authentication.preemptive > %b,true > > > > > > > Confirmed by independent party also with Maven 2.2.1. I can sniff http > traffic if needed. > [1] - http://maven.apache.org/guides/mini/guide-http-settings.html -- 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
