[jira] (MINDEXER-55) Indexer should gather all the discovered packagings during indexing
[ https://jira.codehaus.org/browse/MINDEXER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308315#comment-308315 ] Tamás Cservenák commented on MINDEXER-55: - Original issue https://issues.sonatype.org/browse/NEXUS-3831 > Indexer should gather all the discovered packagings during indexing > --- > > Key: MINDEXER-55 > URL: https://jira.codehaus.org/browse/MINDEXER-55 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák > > The newly discovered packagings that are NOT in the mapping > (ArtifactPackagingMapper) component should be somehow gathered (and maybe > written out to some file?) giving a chance to user to correct mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-55) Indexer should gather all the discovered packagings during indexing
Tamás Cservenák created MINDEXER-55: --- Summary: Indexer should gather all the discovered packagings during indexing Key: MINDEXER-55 URL: https://jira.codehaus.org/browse/MINDEXER-55 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák The newly discovered packagings that are NOT in the mapping (ArtifactPackagingMapper) component should be somehow gathered (and maybe written out to some file?) giving a chance to user to correct mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-56) Get rid of StringBuffer and replace it with StringBuilder.
Tamás Cservenák created MINDEXER-56: --- Summary: Get rid of StringBuffer and replace it with StringBuilder. Key: MINDEXER-56 URL: https://jira.codehaus.org/browse/MINDEXER-56 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák Get rid of StringBuffer and replace it with StringBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-56) Get rid of StringBuffer and replace it with StringBuilder.
[ https://jira.codehaus.org/browse/MINDEXER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-56: Fix Version/s: 5.0.0 https://svn.apache.org/viewvc?view=revision&revision=1372377 > Get rid of StringBuffer and replace it with StringBuilder. > -- > > Key: MINDEXER-56 > URL: https://jira.codehaus.org/browse/MINDEXER-56 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák > Fix For: 5.0.0 > > > Get rid of StringBuffer and replace it with StringBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-56) Get rid of StringBuffer and replace it with StringBuilder.
[ https://jira.codehaus.org/browse/MINDEXER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák reassigned MINDEXER-56: --- Assignee: Tamás Cservenák > Get rid of StringBuffer and replace it with StringBuilder. > -- > > Key: MINDEXER-56 > URL: https://jira.codehaus.org/browse/MINDEXER-56 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Get rid of StringBuffer and replace it with StringBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-56) Get rid of StringBuffer and replace it with StringBuilder.
[ https://jira.codehaus.org/browse/MINDEXER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINDEXER-56. --- Resolution: Fixed Fix in trunk. > Get rid of StringBuffer and replace it with StringBuilder. > -- > > Key: MINDEXER-56 > URL: https://jira.codehaus.org/browse/MINDEXER-56 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Get rid of StringBuffer and replace it with StringBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
Tamás Cservenák created MINDEXER-57: --- Summary: Make use of new Lucene 3.5+ API Key: MINDEXER-57 URL: https://jira.codehaus.org/browse/MINDEXER-57 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák Make use of new Lucene 3.5+ API. Lucene introduced some nice new APIs (and they got into core in 3.6). Since MI is bumped to Lucene 3.6, it should make use of those. Most of these relates to searcher lifespan management, something that was done by very involved locking and "bottlewarmer" features of MI, something that should be completely removed. See: http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
[ https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-57: Fix Version/s: 5.0.0 Assignee: Tamás Cservenák > Make use of new Lucene 3.5+ API > --- > > Key: MINDEXER-57 > URL: https://jira.codehaus.org/browse/MINDEXER-57 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Make use of new Lucene 3.5+ API. > Lucene introduced some nice new APIs (and they got into core in 3.6). Since > MI is bumped to Lucene 3.6, it should make use of those. Most of these > relates to searcher lifespan management, something that was done by very > involved locking and "bottlewarmer" features of MI, something that should be > completely removed. > See: > http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html > http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
[ https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308320#comment-308320 ] Tamás Cservenák commented on MINDEXER-57: - https://svn.apache.org/viewvc?view=revision&revision=1372380 https://svn.apache.org/viewvc?view=revision&revision=1372383 > Make use of new Lucene 3.5+ API > --- > > Key: MINDEXER-57 > URL: https://jira.codehaus.org/browse/MINDEXER-57 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Make use of new Lucene 3.5+ API. > Lucene introduced some nice new APIs (and they got into core in 3.6). Since > MI is bumped to Lucene 3.6, it should make use of those. Most of these > relates to searcher lifespan management, something that was done by very > involved locking and "bottlewarmer" features of MI, something that should be > completely removed. > See: > http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html > http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
[
https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308321#comment-308321
]
Tamás Cservenák commented on MINDEXER-57:
-
This change introduces a _slight_ API change, noticeable if you tamper with
{{IndexingContext}} at low level. For example, Sonatype Nexus integration
required _no source change_ at all (if you don't count one Unit Test that did
tamper with IndexingContext at low level, to bring index into desired state).
For examples of needed code changes, see here:
https://github.com/cstamas/maven-indexer-examples/commit/eb38e442889d072d380c8fb18e5f35a5dd372076
https://github.com/sonatype/nexus/commit/1b2f83c177428469edd53ce1994574db0f3cc986
> Make use of new Lucene 3.5+ API
> ---
>
> Key: MINDEXER-57
> URL: https://jira.codehaus.org/browse/MINDEXER-57
> Project: Maven Indexer
> Issue Type: Improvement
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
> Fix For: 5.0.0
>
>
> Make use of new Lucene 3.5+ API.
> Lucene introduced some nice new APIs (and they got into core in 3.6). Since
> MI is bumped to Lucene 3.6, it should make use of those. Most of these
> relates to searcher lifespan management, something that was done by very
> involved locking and "bottlewarmer" features of MI, something that should be
> completely removed.
> See:
> http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html
> http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
[ https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINDEXER-57. --- Resolution: Fixed Fixes in trunk. > Make use of new Lucene 3.5+ API > --- > > Key: MINDEXER-57 > URL: https://jira.codehaus.org/browse/MINDEXER-57 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Make use of new Lucene 3.5+ API. > Lucene introduced some nice new APIs (and they got into core in 3.6). Since > MI is bumped to Lucene 3.6, it should make use of those. Most of these > relates to searcher lifespan management, something that was done by very > involved locking and "bottlewarmer" features of MI, something that should be > completely removed. > See: > http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html > http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-57) Make use of new Lucene 3.5+ API
[ https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308322#comment-308322 ] Tamás Cservenák commented on MINDEXER-57: - API change was a reason to bump MI version to 5.0 > Make use of new Lucene 3.5+ API > --- > > Key: MINDEXER-57 > URL: https://jira.codehaus.org/browse/MINDEXER-57 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Make use of new Lucene 3.5+ API. > Lucene introduced some nice new APIs (and they got into core in 3.6). Since > MI is bumped to Lucene 3.6, it should make use of those. Most of these > relates to searcher lifespan management, something that was done by very > involved locking and "bottlewarmer" features of MI, something that should be > completely removed. > See: > http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html > http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remote it
[ https://jira.codehaus.org/browse/MINDEXER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINDEXER-58. --- Resolution: Fixed Fix in trunk. > Cleanup deprecated baggage: remote it > - > > Key: MINDEXER-58 > URL: https://jira.codehaus.org/browse/MINDEXER-58 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remote it
[ https://jira.codehaus.org/browse/MINDEXER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák reassigned MINDEXER-58: --- Assignee: Tamás Cservenák > Cleanup deprecated baggage: remote it > - > > Key: MINDEXER-58 > URL: https://jira.codehaus.org/browse/MINDEXER-58 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remote it
[ https://jira.codehaus.org/browse/MINDEXER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308324#comment-308324 ] Tamás Cservenák commented on MINDEXER-58: - https://svn.apache.org/viewvc?view=revision&revision=1372382 > Cleanup deprecated baggage: remote it > - > > Key: MINDEXER-58 > URL: https://jira.codehaus.org/browse/MINDEXER-58 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remote it
Tamás Cservenák created MINDEXER-58: --- Summary: Cleanup deprecated baggage: remote it Key: MINDEXER-58 URL: https://jira.codehaus.org/browse/MINDEXER-58 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remote it
[ https://jira.codehaus.org/browse/MINDEXER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-58: Fix Version/s: 5.0.0 > Cleanup deprecated baggage: remote it > - > > Key: MINDEXER-58 > URL: https://jira.codehaus.org/browse/MINDEXER-58 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-58) Cleanup deprecated baggage: remove it
[ https://jira.codehaus.org/browse/MINDEXER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-58: Summary: Cleanup deprecated baggage: remove it (was: Cleanup deprecated baggage: remote it) > Cleanup deprecated baggage: remove it > - > > Key: MINDEXER-58 > URL: https://jira.codehaus.org/browse/MINDEXER-58 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > We have some deprecated things dragged since version 3. Remove them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-59) Memory hog in case of proxy repository: detection of deleted items
Tamás Cservenák created MINDEXER-59: --- Summary: Memory hog in case of proxy repository: detection of deleted items Key: MINDEXER-59 URL: https://jira.codehaus.org/browse/MINDEXER-59 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák Memory hog in case of proxy repository: detection of deleted items. Index scanner kept a set of UINFOs in memory, used to detect artifact removals (ie. artifact is on index, hence it's UINFO is in set, but is not found by FS scanning). This is not needed at all in case of proxy repositories (when context has remote index update URL set), as in that case removal of an artifact from local FS actually means "removal from cache" and does not affects the remote source (the place from where index is fetched on updates, and eventually, that is proxied). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-59) Memory hog in case of proxy repository: detection of deleted items
[ https://jira.codehaus.org/browse/MINDEXER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINDEXER-59. --- Resolution: Fixed Fix in trunk. > Memory hog in case of proxy repository: detection of deleted items > -- > > Key: MINDEXER-59 > URL: https://jira.codehaus.org/browse/MINDEXER-59 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Memory hog in case of proxy repository: detection of deleted items. > Index scanner kept a set of UINFOs in memory, used to detect artifact > removals (ie. artifact is on index, hence it's UINFO is in set, but is not > found by FS scanning). > This is not needed at all in case of proxy repositories (when context has > remote index update URL set), as in that case removal of an artifact from > local FS actually means "removal from cache" and does not affects the remote > source (the place from where index is fetched on updates, and eventually, > that is proxied). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-59) Memory hog in case of proxy repository: detection of deleted items
[ https://jira.codehaus.org/browse/MINDEXER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308328#comment-308328 ] Tamás Cservenák commented on MINDEXER-59: - https://svn.apache.org/viewvc?view=revision&revision=1373387 > Memory hog in case of proxy repository: detection of deleted items > -- > > Key: MINDEXER-59 > URL: https://jira.codehaus.org/browse/MINDEXER-59 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Memory hog in case of proxy repository: detection of deleted items. > Index scanner kept a set of UINFOs in memory, used to detect artifact > removals (ie. artifact is on index, hence it's UINFO is in set, but is not > found by FS scanning). > This is not needed at all in case of proxy repositories (when context has > remote index update URL set), as in that case removal of an artifact from > local FS actually means "removal from cache" and does not affects the remote > source (the place from where index is fetched on updates, and eventually, > that is proxied). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-59) Memory hog in case of proxy repository: detection of deleted items
[ https://jira.codehaus.org/browse/MINDEXER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-59: Fix Version/s: 5.0.0 Assignee: Tamás Cservenák > Memory hog in case of proxy repository: detection of deleted items > -- > > Key: MINDEXER-59 > URL: https://jira.codehaus.org/browse/MINDEXER-59 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Memory hog in case of proxy repository: detection of deleted items. > Index scanner kept a set of UINFOs in memory, used to detect artifact > removals (ie. artifact is on index, hence it's UINFO is in set, but is not > found by FS scanning). > This is not needed at all in case of proxy repositories (when context has > remote index update URL set), as in that case removal of an artifact from > local FS actually means "removal from cache" and does not affects the remote > source (the place from where index is fetched on updates, and eventually, > that is proxied). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-60) Bump MI project to to Java6
Tamás Cservenák created MINDEXER-60: --- Summary: Bump MI project to to Java6 Key: MINDEXER-60 URL: https://jira.codehaus.org/browse/MINDEXER-60 Project: Maven Indexer Issue Type: Improvement Reporter: Tamás Cservenák -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-60) Bump MI project to to Java6
[ https://jira.codehaus.org/browse/MINDEXER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-60: Description: Maven Indexer project should be bumped to Java6 source and target levels. As Java6 is about to EOL, and MI is still Java5... Fix Version/s: 5.0.0 > Bump MI project to to Java6 > --- > > Key: MINDEXER-60 > URL: https://jira.codehaus.org/browse/MINDEXER-60 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Maven Indexer project should be bumped to Java6 source and target levels. As > Java6 is about to EOL, and MI is still Java5... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-60) Bump MI project to to Java6
[ https://jira.codehaus.org/browse/MINDEXER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák reassigned MINDEXER-60: --- Assignee: Tamás Cservenák > Bump MI project to to Java6 > --- > > Key: MINDEXER-60 > URL: https://jira.codehaus.org/browse/MINDEXER-60 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-60) Bump MI project to to Java6
[ https://jira.codehaus.org/browse/MINDEXER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MINDEXER-60. --- Resolution: Won't Fix Won't do this: conclusion on the mailing thread was that people prefer spectacles designed before 250 years, and nobody wants to wear new designed, new techie (polarising), etc. Similarly with phones: Apple initially met huge refusal for their new phones, as everyone was sticking to their can phones... It all makes sense ;) > Bump MI project to to Java6 > --- > > Key: MINDEXER-60 > URL: https://jira.codehaus.org/browse/MINDEXER-60 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák > Fix For: 5.0.0 > > > Maven Indexer project should be bumped to Java6 source and target levels. As > Java6 is about to EOL, and MI is still Java5... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308333#comment-308333
]
nkeywal commented on SUREFIRE-800:
--
Hi Kristian,
Any feedback on this patch? I think it fixes SUREFIRE-817 as well BTW.
I can add the class name in the "Tests run" line if you confirm you're ok with
the patch globally...
Thanks!
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
> Attachments: 800.v1.patch
>
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308335#comment-308335
]
Kristian Rosenvold commented on SUREFIRE-800:
-
Not yet, I'll be doing a very minor bugfix release for surefire "soon" and will
look at it then.
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
> Fix For: 2.13
>
> Attachments: 800.v1.patch
>
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-800:
Fix Version/s: 2.13
Assignee: Kristian Rosenvold
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: 800.v1.patch
>
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-227) packaged (war:war) and exploded (war:expanded) webapps have different content
[
https://jira.codehaus.org/browse/MWAR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308341#comment-308341
]
Dieter König commented on MWAR-227:
---
Huh? You are referencing the documentation. Is possibly the documentation of
exploded goal wrong?
"Description:
Create an exploded webapp in a specified directory."
How should this be understood?
By the way there is no need in functionality exploded goal provides ACTUALLY
because the exploded directory in that form is already generated during war:war
processing. That's why i was also assuming exploded would generate the
"unpackaged" war and what indeed should be the truth.
> packaged (war:war) and exploded (war:expanded) webapps have different content
> -
>
> Key: MWAR-227
> URL: https://jira.codehaus.org/browse/MWAR-227
> Project: Maven 2.x WAR Plugin
> Issue Type: New Feature
>Affects Versions: 2.1-beta-1
>Reporter: Kevin Wright
>
> Specifically, when using
> WEB-INF/lib/*.jar, the jars are
> correctly excluded from the packaged form of the war, but still present in
> the exploded form.
> Both forms should have identical content and should be totally
> interchangable. This also means that there is no possible way to exclude
> jars from an exploded webapp.
> As a workaround, I also attempted this:
> {code:xml}
>
>
> WEB-INF/lib/*.jar
>
>
> {code}
> But just got an exception thrown for my efforts...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
Martijn Verburg created MPIR-253: Summary: Team report does support CEST timezone Key: MPIR-253 URL: https://jira.codehaus.org/browse/MPIR-253 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: project-team Affects Versions: 2.5.1 Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34 Reporter: Martijn Verburg Priority: Minor [INFO] Generating "Project Team" report--- maven-project-info-reports-plugin:2.5.1 [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a recognised time zone, use a number in the range -12 and +14 instead of. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-252) Dependency Management report doesn't exclude system scoped dependencies
Martijn Verburg created MPIR-252: Summary: Dependency Management report doesn't exclude system scoped dependencies Key: MPIR-252 URL: https://jira.codehaus.org/browse/MPIR-252 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependency-management Affects Versions: 2.5.1 Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34 Reporter: Martijn Verburg [WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion from repository. org.apache.maven.project.ProjectBuildingException: Error resolving project artifact: Failure to find com.sun:tools:pom:localVersion in http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jclarity-central has elapsed or updates are forced for project com.sun:tools:pom:localVersion at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146) at org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79) at org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused
[jira] (MJAVADOC-350) Allow include/exclude at the class level
Benson Margulies created MJAVADOC-350: - Summary: Allow include/exclude at the class level Key: MJAVADOC-350 URL: https://jira.codehaus.org/browse/MJAVADOC-350 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.8.1 Reporter: Benson Margulies Javadoc itself (and the ant task, for purposes of comparison) allows controlling the source files that are processed, one at a time. I suggest the creation of a standard maven include/exclude setup to give class-at-a-time control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPIR-253:
Description:
{noformat}
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.5.1
[WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
recognised time zone, use a number in the range -12 and +14 instead of.
{noformat}
was:
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.5.1
[WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
recognised time zone, use a number in the range -12 and +14 instead of.
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308363#comment-308363
]
Robert Scholte commented on MPIR-253:
-
How was the developer defined in the pom?
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-252) Dependency Management report doesn't exclude system scoped dependencies
[
https://jira.codehaus.org/browse/MPIR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPIR-252:
Description:
{noformat}
[WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion
from repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find com.sun:tools:pom:localVersion in
http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the
local repository, resolution will not be reattempted until the update interval
of jclarity-central has elapsed or updates are forced for project
com.sun:tools:pom:localVersion
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure
to find com.sun:tools:pom:localVersion in
http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the
local repository, resolution will not be reattempted until the update interval
of jclarity-central has elapsed or updates are for
[jira] (MPIR-252) Dependency Management report doesn't exclude system scoped dependencies
[
https://jira.codehaus.org/browse/MPIR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308364#comment-308364
]
Robert Scholte commented on MPIR-252:
-
Was this a system-scoped dependency? What does it look like? (In other words:
how can we reproduce it?)
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-252
> URL: https://jira.codehaus.org/browse/MPIR-252
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>
> {noformat}
> [WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion
> from repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find com.sun:tools:pom:localVersion in
> http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of jclarity-central has elapsed or updates are forced for project
> com.sun:tools:pom:localVersion
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308365#comment-308365
]
Martijn Verburg commented on MPIR-253:
--
Ben Evans
GMT
Kirk Pepperdine
CEST
Martijn Verburg
GMT
Richard Warburton
GMT
John Oliver
GMT
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-252) Dependency Management report doesn't exclude system scoped dependencies
[
https://jira.codehaus.org/browse/MPIR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308366#comment-308366
]
Martijn Verburg commented on MPIR-252:
--
In the dependency management section:
com.sun
tools
localVersion
system
${toolsjar}
Where ${toolsJar} is set by a property to be ${java.home}/..lib/tools.jar"
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-252
> URL: https://jira.codehaus.org/browse/MPIR-252
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>
> {noformat}
> [WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion
> from repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find com.sun:tools:pom:localVersion in
> http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of jclarity-central has elapsed or updates are forced for project
> com.sun:tools:pom:localVersion
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.N
[jira] (MDEP-376) -Dincludes and -Dexcludes filtering not working anymore
Ryan Gardner created MDEP-376:
-
Summary: -Dincludes and -Dexcludes filtering not working anymore
Key: MDEP-376
URL: https://jira.codehaus.org/browse/MDEP-376
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: tree
Affects Versions: 2.5.1
Reporter: Ryan Gardner
running
{code}
mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
{code}
will restrict the tree that is printed to just show the artifacts that match
the includes pattern (a much smaller tree)
in version 2.5+
{code}
mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
{code}
on a project will show the entire tree with no filtering.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308367#comment-308367
]
Robert Scholte commented on MPIR-253:
-
I think it should be CET (Central European Time) instead of CEST (Central
European Summer Time).
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308368#comment-308368
]
Martijn Verburg commented on MPIR-253:
--
Right you are, thanks! - I can't seem to close this issue with a "Won't Fix"
equivalent, is that something you can do?
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-253) Team report does support CEST timezone
[
https://jira.codehaus.org/browse/MPIR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPIR-253.
---
Resolution: Not A Bug
Assignee: Robert Scholte
Never use the summertime
> Team report does support CEST timezone
> --
>
> Key: MPIR-253
> URL: https://jira.codehaus.org/browse/MPIR-253
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: project-team
>Affects Versions: 2.5.1
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Martijn Verburg
>Assignee: Robert Scholte
>Priority: Minor
>
> {noformat}
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.5.1
> [WARNING] The time zone 'CEST' for the developer 'Kirk Pepperdine' is not a
> recognised time zone, use a number in the range -12 and +14 instead of.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308374#comment-308374 ] Martin Franklin commented on MCOMPILER-157: --- I managed to get this working using the helper plugin in combination with a second invocation of the compiler. Let compiler run normally and generate the annotation processor output. Then invoke the help plugin at the process-classes lifecycle stage, followed by the compiler again. Note that the order is important, so that the build-helper gets invoked before the compiler. org.codehaus.mojo build-helper-maven-plugin 1.7 add-source process-classes add-source target/generated-sources/annotations maven-compiler-plugin add-source process-classes compile > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Fix For: 2.6 > > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > maven-compiler-plugin-addToSourcePathAsWell.patch, TestCase2.zip, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308375#comment-308375 ] Martin Franklin commented on MCOMPILER-157: --- Should also state I upgraded to the compiler version 2.5.1 and am using maven 3.0.4 > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Fix For: 2.6 > > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > maven-compiler-plugin-addToSourcePathAsWell.patch, TestCase2.zip, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-232) maven-ant-tasks port to maven 3.x
gil created MANTTASKS-232: - Summary: maven-ant-tasks port to maven 3.x Key: MANTTASKS-232 URL: https://jira.codehaus.org/browse/MANTTASKS-232 Project: Maven 2.x Ant Tasks Issue Type: Bug Affects Versions: 2.1.3 Environment: fedora all version Reporter: gil Attachments: maven-ant-tasks-2.1.3-build-failure.txt hello, in fedora maven 2.x don't provides some libraries if they are presents in maven 3.x. there are some plans for add to m-a-t maven 3.x compatibilty ? thanks regards shown in the attached file errors trying to run the build with maven 3.x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-257) Improve filter documentation
[ https://jira.codehaus.org/browse/MCHANGES-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308380#comment-308380 ] Jared Fordham commented on MCHANGES-257: A log message, warning / info, might also help users understand a configuration that they are attempting will not being honored. > Improve filter documentation > > > Key: MCHANGES-257 > URL: https://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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5255) Dependency with 'provided' scope has its transitive dependency included in final artifact
[ https://jira.codehaus.org/browse/MNG-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308383#comment-308383 ] Andrey Saksonov commented on MNG-5255: -- Same issue with me, also it affects test scope too. I was very surprised too see servlet-api-2.5 (provided scope) and junit-4.10 (test scope) in my final war in my Spring/GAE/GWT application generated by Spring Roo. If your google about GWT problems with maven you find a lot of messages like this: http://stackoverflow.com/questions/10671855/unit-testing-app-engine-eclipse-maven. I think it is the same problem, it is not understandable why test scoped jars (actually it is some mocks used only for unit testing) pulled into final war artifact. > Dependency with 'provided' scope has its transitive dependency included in > final artifact > - > > Key: MNG-5255 > URL: https://jira.codehaus.org/browse/MNG-5255 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.4 > Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) > Maven home: D:\bin\apache-maven-3.0.4 > Java version: 1.6.0_27, vendor: Sun Microsystems Inc. > Java home: D:\bin\java\jdk1.6.0_27\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Bart Skondin > Attachments: provided-scope-not-working.zip > > > Expected: A dependency declared with a scope of 'provided', along with any > transitive dependencies, should not be included in the final artifact. > Actual: I have a dependency, jsp-api, declared with 'provided' scope. This > dependency has a dependency of its own, servlet-api. The servlet-api.jar is > being included in the web-inf/lib folder of the resultant war file. > Background: We recently upgraded from Maven 2.2.1 to Maven 3.0.4. The problem > was not witnessed until after the upgrade. > Steps to Reproduce: Run mvn install, then have a look at the web-inf/lib > folder. Notice that the servlet-api.jar has been included. > Additional Info: It seems that I can only reproduce this behavior when > declaring a specific dependency in my pom, spring-ldap. Here is the > dependency tree for the given pared-down project (attached): > --- maven-dependency-plugin:2.1:tree (default-cli) @ > provided-scope-not-working --- > com.bug.example:provided-scope-not-working:war:0.0.1-SNAPSHOT > +- javax.servlet:jsp-api:jar:2.0:provided > | \- javax.servlet:servlet-api:jar:2.4:provided > \- org.springframework.ldap:spring-ldap:jar:1.2.1:compile >+- commons-logging:commons-logging:jar:1.0.4:compile >+- commons-lang:commons-lang:jar:2.1:compile >+- org.springframework:spring-beans:jar:2.0.6:compile >| +- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) >| \- (org.springframework:spring-core:jar:2.0.6:compile - omitted for > duplicate) >\- org.springframework:spring-core:jar:2.0.6:compile > \- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-286) Please make test-jar also run for "war" packages
[ https://jira.codehaus.org/browse/MWAR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308387#comment-308387 ] Marco rietveld commented on MWAR-286: - @Robert, thanks, that fixes the problem for us. > Please make test-jar also run for "war" packages > > > Key: MWAR-286 > URL: https://jira.codehaus.org/browse/MWAR-286 > Project: Maven 2.x WAR Plugin > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Marco rietveld >Priority: Minor > > If you configure the jar plugin to also run the test-jar goal, it will only > run that if the package type in the pom of the project is "jar". > However, in the case of wars it's would also be handy to be able to make the > test-jars (by simply changing the configuration in one mother pom). > We realize that this is an edge-case. However, we (drools/jbpm) work with a > project that has _lots_ or submodules including a couple "war" submodules. > Being able to simply have all war submodules generate test-jars without > having to modify each individual war submodule's pom.xml would be nice. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
