[jira] (MSITE-695) java.lang.NullPointerException in org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL
[
https://jira.codehaus.org/browse/MSITE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329900#comment-329900
]
Herve Boutemy commented on MSITE-695:
-
ok, this time, I can reproduce and even understand the failure and propose a
workaround
first, the workaround: don't use -DstagingSiteURL=... but write the value in
pom (either directly or in a profile)
this case, where the value is set on CLI but not in the pom, was omitted in
code: now I understand how the code was returning null but this wasn't expected
(and I couldn't even imagine how to get such a case)
then I'll fix the issue in next plugin version: due to some other changes,
actual trunk won't fail with NPE, but it won't calculate right staging url
> java.lang.NullPointerException in
> org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL
> --
>
> Key: MSITE-695
> URL: https://jira.codehaus.org/browse/MSITE-695
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 3.2, 3.3
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
> Maven home: C:\Java\apache-maven-3.0.5\bin\..
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> and
> C:\vcs\svn\apache\log4j2\trunk>C:\Java\apache-maven-3.1.0\bin\mvn.bat -version
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27
> 22:15:32-0400)
> Maven home: C:\Java\apache-maven-3.1.0\bin\..
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Priority: Blocker
>
> Checkout log4j 2 from:
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
> The HEAD of trunk is currently revision 1504131.
> Run:
> mvn clean site
> Get:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.724s
> [INFO] Finished at: Wed Jul 17 12:43:47 EDT 2013
> [INFO] Final Memory: 22M/213M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on
> project log4j: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy
> (default-cli) on project log4j: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:318)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[jira] (MSITE-695) java.lang.NullPointerException in org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL
[
https://jira.codehaus.org/browse/MSITE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329906#comment-329906
]
Herve Boutemy commented on MSITE-695:
-
notice I don't know what eats so much memory when building site: is it really
expected?
hint: declaring time consuming reporting plugins in a reporting profile permits
quick "mvn site site:stage" tests to check site structure and hand-written
content, then "mvn -Preporting site site:stage" to get a last full check before
stage-deploying. In your case, it could IMHO help you a lot given the amount of
reports
> java.lang.NullPointerException in
> org.apache.maven.plugins.site.SiteStageDeployMojo.getTopMostParentWithSameStagingSiteURL
> --
>
> Key: MSITE-695
> URL: https://jira.codehaus.org/browse/MSITE-695
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 3.2, 3.3
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
> Maven home: C:\Java\apache-maven-3.0.5\bin\..
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> and
> C:\vcs\svn\apache\log4j2\trunk>C:\Java\apache-maven-3.1.0\bin\mvn.bat -version
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27
> 22:15:32-0400)
> Maven home: C:\Java\apache-maven-3.1.0\bin\..
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Priority: Blocker
>
> Checkout log4j 2 from:
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
> The HEAD of trunk is currently revision 1504131.
> Run:
> mvn clean site
> Get:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.724s
> [INFO] Finished at: Wed Jul 17 12:43:47 EDT 2013
> [INFO] Final Memory: 22M/213M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy (default-cli) on
> project log4j: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy
> (default-cli) on project log4j: Execution default-cli of goal
> org.apache.maven.plugins:maven-site-plugin:3.3:stage-deploy failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:318)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:606)
> 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:414)
> at
> org.codehaus.plexus.classworlds.lau
[jira] (DOXIA-493) Images within table are not shown
[
https://jira.codehaus.org/browse/DOXIA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Schenk updated DOXIA-493:
--
Attachment: Patch_DOXIA-493_trunk.patch
Added patch for trunk including unit test
> Images within table are not shown
> -
>
> Key: DOXIA-493
> URL: https://jira.codehaus.org/browse/DOXIA-493
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.4
> Environment: Windows/Linux
>Reporter: Mark Schenk
> Attachments: Patch_DOXIA-493_trunk.patch,
> Patch_for_correcting_images_and_headers_within_table_cell.patch
>
>
> While working on project documentation I encountered a (at least I think) bug
> which is related to including images in tables. The example below doesnât
> result in an image shown in the table cell but instead shows the inclusion as
> text ({{!images/symbol.png!}}).
> {code}
> ||Symbol||Description||
> |!images/symbol.png!|text|
> {code}
> After investigation I found out that the renderer of the table
> ({{TableBlockParser}}) only applies the {{ParagraphBlockParser}} and not
> other parsers like {{SectionBlockParser}}, {{FigureBlockParser}}, and
> {{ListBlockParser}}.
> To fix this I created the included patch. With this patch applied to version
> 1.4 of Doxia the example as shown above was properly parsed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version
[ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated MRELEASE-431: - Attachment: MRELEASE-431.patch I've updated the code to make the VersionPolicyManager a plexus component, and it's now injected by plexus into the MapVersionsPhase. However, I don't know where I can override the implementation using Plexus configuration as you suggested, so any hints are appreciated. Besides the updated [^MRELEASE-431.patch], you can also view the [diff on github|https://github.com/rombert/release/compare/6de575dd76224c690bfd88375eac88f49ba6d319...HEAD] > Configuration of policy for calculating next (release) version > -- > > Key: MRELEASE-431 > URL: https://jira.codehaus.org/browse/MRELEASE-431 > Project: Maven Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.0-beta-8 >Reporter: Carsten Ziegeler >Assignee: Robert Scholte > Fix For: 2.5 > > Attachments: > 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch, > MRELEASE-431.patch > > > Currently, when preparing the release, the version to release is always the > next version which usually is the current version without the snapshot > extension. > There are quiet a lot projects (Apache Felix, Sling and others) following an > even release numbering policy. So while the current development version is > odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4. > It would be nice if this could be made configuration through some > configuration property like > next-even (with possible values being: next > (default, as-is), next-even, next-odd > I briefly scanned through the code and it seems that adding support for this > requires changes in both, the release-manager and the release-plugin. > If this feature gets accepted and if someone could give me some minor hints > how/where to add this I could come up with a patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5467) intermittent "ProtocolException: The server failed to respond with a valid HTTP response"
[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329936#comment-329936 ] Peter Lynch commented on MNG-5467: -- This applies to 3.1.0 as well. This fails every other build for me, so I consider it critical to fix. Can we start the wagon 2.5 release process at least so we can manually override the wagon in Maven? > intermittent "ProtocolException: The server failed to respond with a valid > HTTP response" > - > > Key: MNG-5467 > URL: https://jira.codehaus.org/browse/MNG-5467 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.5 >Reporter: Igor Fedorenko > > Building projects with maven 3.0.5 I regularly get "ProtocolException: The > server failed to respond with a valid HTTP response" when resolving > dependencies from repository.sonatype.org. From what I can tell this is > caused by a bug in httpclient, which I reported as > https://issues.apache.org/jira/browse/HTTPCLIENT-1340 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5467) intermittent "ProtocolException: The server failed to respond with a valid HTTP response"
[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-5467: - Priority: Critical (was: Major) > intermittent "ProtocolException: The server failed to respond with a valid > HTTP response" > - > > Key: MNG-5467 > URL: https://jira.codehaus.org/browse/MNG-5467 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.5 >Reporter: Igor Fedorenko >Priority: Critical > > Building projects with maven 3.0.5 I regularly get "ProtocolException: The > server failed to respond with a valid HTTP response" when resolving > dependencies from repository.sonatype.org. From what I can tell this is > caused by a bug in httpclient, which I reported as > https://issues.apache.org/jira/browse/HTTPCLIENT-1340 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5467) intermittent "ProtocolException: The server failed to respond with a valid HTTP response"
[ https://jira.codehaus.org/browse/MNG-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MNG-5467: - Affects Version/s: 3.1.0 > intermittent "ProtocolException: The server failed to respond with a valid > HTTP response" > - > > Key: MNG-5467 > URL: https://jira.codehaus.org/browse/MNG-5467 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.5, 3.1.0 >Reporter: Igor Fedorenko >Priority: Critical > > Building projects with maven 3.0.5 I regularly get "ProtocolException: The > server failed to respond with a valid HTTP response" when resolving > dependencies from repository.sonatype.org. From what I can tell this is > caused by a bug in httpclient, which I reported as > https://issues.apache.org/jira/browse/HTTPCLIENT-1340 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-96) Skip option for install-file
Tiemo Vorschütz created MINSTALL-96: --- Summary: Skip option for install-file Key: MINSTALL-96 URL: https://jira.codehaus.org/browse/MINSTALL-96 Project: Maven Install Plugin Issue Type: Improvement Components: install:install-file Affects Versions: 2.4 Reporter: Tiemo Vorschütz Attachments: InstallFileMojo.java.patch For my process it would be helpful to also introduce a skip option for install:install-file to be able to disable install-file creation by setting a pom property. This could be necessary if the build chain is designed by a parent pom and should by simply modified inside the child pom. In my case all plugin definitions are outsourced to the parent pom file and should only be set by properties by the developers to take care that modifications to the build chain are inherited. I attached a patch to enable skipping also for install-file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-72) Add copyright notice position option
[
https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSKINS-72.
Resolution: Fixed
> Add copyright notice position option
>
>
> Key: MSKINS-72
> URL: https://jira.codehaus.org/browse/MSKINS-72
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
>Affects Versions: fluido-1.3.0
>Reporter: Michael Osipov
>Assignee: Olivier Lamy
> Fix For: fluido-1.3.1
>
> Attachments: MSKINS-72.patch, mylyn-context.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The default skin has the copyright notice on the right-hand side of the
> screen. This has unfortunately changed in fluido skin.
> Add a {{}} element to site.xml/custom/fluidoSkin with left
> or right as values.
> IMHO default should be as in default skin.
> If current state will be retained, the right position has to be added to
> [this
> line|http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.3.0/src/main/resources/META-INF/maven/site.vm?view=markup#l1055].
> Swap {{class="row span12"}} to {{class="pull-right"}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-72) Add copyright notice position option
[
https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329946#comment-329946
]
Michael Osipov commented on MSKINS-72:
--
Fixed with http://svn.apache.org/r1509378
> Add copyright notice position option
>
>
> Key: MSKINS-72
> URL: https://jira.codehaus.org/browse/MSKINS-72
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
>Affects Versions: fluido-1.3.0
>Reporter: Michael Osipov
>Assignee: Olivier Lamy
> Fix For: fluido-1.3.1
>
> Attachments: MSKINS-72.patch, mylyn-context.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The default skin has the copyright notice on the right-hand side of the
> screen. This has unfortunately changed in fluido skin.
> Add a {{}} element to site.xml/custom/fluidoSkin with left
> or right as values.
> IMHO default should be as in default skin.
> If current state will be retained, the right position has to be added to
> [this
> line|http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.3.0/src/main/resources/META-INF/maven/site.vm?view=markup#l1055].
> Swap {{class="row span12"}} to {{class="pull-right"}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-85) Unify breadcrumb chevron of Fluido with other skins
Michael Osipov created MSKINS-85: Summary: Unify breadcrumb chevron of Fluido with other skins Key: MSKINS-85 URL: https://jira.codehaus.org/browse/MSKINS-85 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.1, fluido-1.3.0 Reporter: Michael Osipov Priority: Minor Fluido uses a slash because Bootstrap's examples do but all other skins use a greater-than sign. This should be unified to the greater-than sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-85) Unify breadcrumb chevron of Fluido with other skins
[ https://jira.codehaus.org/browse/MSKINS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-85: - Fix Version/s: fluido-1.3.1 Assignee: Michael Osipov Remaining Estimate: 0 minutes Original Estimate: 0 minutes > Unify breadcrumb chevron of Fluido with other skins > --- > > Key: MSKINS-85 > URL: https://jira.codehaus.org/browse/MSKINS-85 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0, fluido-1.3.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: fluido-1.3.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Fluido uses a slash because Bootstrap's examples do but all other skins use a > greater-than sign. This should be unified to the greater-than sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-85) Unify breadcrumb chevron of Fluido with other skins
[ https://jira.codehaus.org/browse/MSKINS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329948#comment-329948 ] Michael Osipov commented on MSKINS-85: -- Targetting for 1.3.1. > Unify breadcrumb chevron of Fluido with other skins > --- > > Key: MSKINS-85 > URL: https://jira.codehaus.org/browse/MSKINS-85 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0, fluido-1.3.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: fluido-1.3.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Fluido uses a slash because Bootstrap's examples do but all other skins use a > greater-than sign. This should be unified to the greater-than sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-74) JarFileContentsIndexCreator may stop scanning under some circumstances
Tamás Cservenák created MINDEXER-74: --- Summary: JarFileContentsIndexCreator may stop scanning under some circumstances Key: MINDEXER-74 URL: https://jira.codehaus.org/browse/MINDEXER-74 Project: Maven Indexer Issue Type: Bug Reporter: Tamás Cservenák JarFileContentsIndexCreator, if throws some RuntimeException, will: * abort scanning * not provide enough context information Example: https://issues.sonatype.org/browse/NEXUS-5814 Probably caused by some unicode entry in inspected JAR file: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499 Proposal: JarFileContentsIndexCreator should in these case provide more meaningful log entry (what file, what entry maybe), be more resistant to problems like these and should not stop scanning, but Scanner should continue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-74) JarFileContentsIndexCreator may stop scanning under some circumstances
[ https://jira.codehaus.org/browse/MINDEXER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-74: Description: JarFileContentsIndexCreator, if throws some RuntimeException, will: * abort scanning * not provide enough context information Example: https://issues.sonatype.org/browse/NEXUS-5814 Probably caused by some unicode entry in inspected JAR file: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499 Proposal: JarFileContentsIndexCreator should in these case provide more meaningful log entry (what file, what entry maybe), be more resistant to problems like these and should not stop scanning, but Scanner should continue (and probably skip this JAR file but logging this fact). was: JarFileContentsIndexCreator, if throws some RuntimeException, will: * abort scanning * not provide enough context information Example: https://issues.sonatype.org/browse/NEXUS-5814 Probably caused by some unicode entry in inspected JAR file: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499 Proposal: JarFileContentsIndexCreator should in these case provide more meaningful log entry (what file, what entry maybe), be more resistant to problems like these and should not stop scanning, but Scanner should continue. > JarFileContentsIndexCreator may stop scanning under some circumstances > -- > > Key: MINDEXER-74 > URL: https://jira.codehaus.org/browse/MINDEXER-74 > Project: Maven Indexer > Issue Type: Bug >Reporter: Tamás Cservenák > > JarFileContentsIndexCreator, if throws some RuntimeException, will: > * abort scanning > * not provide enough context information > Example: > https://issues.sonatype.org/browse/NEXUS-5814 > Probably caused by some unicode entry in inspected JAR file: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499 > Proposal: > JarFileContentsIndexCreator should in these case provide more meaningful log > entry (what file, what entry maybe), be more resistant to problems like these > and should not stop scanning, but Scanner should continue (and probably skip > this JAR file but logging this fact). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-75) Squash indexer-artifact and indexer-core
Tamás Cservenák created MINDEXER-75: --- Summary: Squash indexer-artifact and indexer-core Key: MINDEXER-75 URL: https://jira.codehaus.org/browse/MINDEXER-75 Project: Maven Indexer Issue Type: Task Reporter: Tamás Cservenák Priority: Minor This separation is a legacy, while this component was part of Sonatype Nexus. There is no reason to have the 6 file separated now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-75) Squash indexer-artifact and indexer-core
[ https://jira.codehaus.org/browse/MINDEXER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák updated MINDEXER-75: Description: This separation is a legacy, while this component was part of Sonatype Nexus. There is no reason to have the 10 classes separated now. (was: This separation is a legacy, while this component was part of Sonatype Nexus. There is no reason to have the 6 file separated now.) > Squash indexer-artifact and indexer-core > > > Key: MINDEXER-75 > URL: https://jira.codehaus.org/browse/MINDEXER-75 > Project: Maven Indexer > Issue Type: Task >Reporter: Tamás Cservenák >Priority: Minor > > This separation is a legacy, while this component was part of Sonatype Nexus. > There is no reason to have the 10 classes separated now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINDEXER-76) Move IndexCreatorSorter.sort use into DefaultIndexingContext
Tamás Cservenák created MINDEXER-76: --- Summary: Move IndexCreatorSorter.sort use into DefaultIndexingContext Key: MINDEXER-76 URL: https://jira.codehaus.org/browse/MINDEXER-76 Project: Maven Indexer Issue Type: Task Reporter: Tamás Cservenák As currently: * multiple execution paths misses to apply it * current state is inconsistent * not sorting index creators causes MINDEXER-34 Having it happen at one single place is better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-301) webResources filtering not happening properly
Mukarram Baig created MWAR-301: -- Summary: webResources filtering not happening properly Key: MWAR-301 URL: https://jira.codehaus.org/browse/MWAR-301 Project: Maven WAR Plugin Issue Type: Bug Components: filtering Affects Versions: 2.4 Environment: Linux Reporter: Mukarram Baig Attachments: mwar-tester.zip I noticed that webResources were not getting filtered when I upgraded from 2.3 to 2.4 and could not find an open issue related to it, so letting you guys know if I am doing something incorrect that was working till 2.3 and got fixed in 2.4. I am attaching a sample project where a JS file was getting filtered properly when using 2.3 and not when using 2.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-85) Unify breadcrumb chevron of Fluido with other skins
[ https://jira.codehaus.org/browse/MSKINS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329955#comment-329955 ] Michael Osipov commented on MSKINS-85: -- Fixed in r1509551. > Unify breadcrumb chevron of Fluido with other skins > --- > > Key: MSKINS-85 > URL: https://jira.codehaus.org/browse/MSKINS-85 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0, fluido-1.3.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: fluido-1.3.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Fluido uses a slash because Bootstrap's examples do but all other skins use a > greater-than sign. This should be unified to the greater-than sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-85) Unify breadcrumb chevron of Fluido with other skins
[ https://jira.codehaus.org/browse/MSKINS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSKINS-85. Resolution: Fixed > Unify breadcrumb chevron of Fluido with other skins > --- > > Key: MSKINS-85 > URL: https://jira.codehaus.org/browse/MSKINS-85 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.0, fluido-1.3.1 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Minor > Fix For: fluido-1.3.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Fluido uses a slash because Bootstrap's examples do but all other skins use a > greater-than sign. This should be unified to the greater-than sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
