[jira] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://jira.codehaus.org/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328984#comment-328984
]
SebbASF commented on MCOMPILER-205:
---
Note that version 2.5.1 does not suffer from this problem; it only recompiles
the package_info.java files - they do not cause the entire project to be
recompiled.
3.0 and 3.1 are broken.
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://jira.codehaus.org/browse/MCOMPILER-205
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
> Attachments: hello.tgz, no-class-in-java-file.zip
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
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] (DOXIA-492) Add support for doxia macros in markdown documents.
Juergen Kellerer created DOXIA-492:
--
Summary: Add support for doxia macros in markdown documents.
Key: DOXIA-492
URL: https://jira.codehaus.org/browse/DOXIA-492
Project: Maven Doxia
Issue Type: Improvement
Components: Module - Markdown
Affects Versions: 1.4
Reporter: Juergen Kellerer
Attachments: screen.png
It would be nice if doxia macros could be supported also inside markdown
documents (similar to APT).
Existing macros (especially snippet) is very useful, however with the power of
maven there's the ability to register own macros for a build process which
enables reuse of resources and improves dryness in general.
A syntax which may work could be the following:
* Block Level
{noformat}
#`??MACRO_NAME MACRO_ARGS`
{noformat}
* Inline
{noformat}
`??MACRO_NAME MACRO_ARGS`
{noformat}
Reference:
http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
E.g. using "Texts" it works just from the Editor:
!screen.png!
When macros are not interpreted, they fallback to a code block, thus it's easy
to edit these sort of documents with one of the existing nice markdown editors.
--
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] (DOXIA-491) Where are the binary downloads for Doxia Tools?
[ https://jira.codehaus.org/browse/DOXIA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329031#comment-329031 ] Dennis Lundberg commented on DOXIA-491: --- Which Doxia Tool are you looking for, and which version? There have been some restructuring done to Doxia Tools, but that is only on the SCM side of things. You'll find Doxia Converter here: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-converter/ Doxia Linkcheck is here: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-linkcheck/ > Where are the binary downloads for Doxia Tools? > --- > > Key: DOXIA-491 > URL: https://jira.codehaus.org/browse/DOXIA-491 > Project: Maven Doxia > Issue Type: Bug >Reporter: SebbASF > > The page > http://maven.apache.org/doxia/downloads.html > says that source and binary are available through > http://repo.maven.apache.org/maven2/org/apache/maven/doxia/ > However, I could not find any binaries for Doxia Tools -- 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] (MSITE-693) site:stage(-deploy) creates incorrect structure
[ https://jira.codehaus.org/browse/MSITE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329032#comment-329032 ] Dennis Lundberg commented on MSITE-693: --- Please attach a complete runnable project that we can use to test this issue. > site:stage(-deploy) creates incorrect structure > --- > > Key: MSITE-693 > URL: https://jira.codehaus.org/browse/MSITE-693 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: multi module, site:stage(-deploy) >Affects Versions: 3.3 > Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 10:44:56+0200) > Java version: 1.6.0_26, vendor: Sun Microsystems Inc. > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-41-generic-pae", arch: "i386", family: > "unix" >Reporter: Malcolm Wong Ho > > Similar to issue : http://jira.codehaus.org/browse/MSITE-669 > By follow the Maven conventions for multi-module tree, the site plugin does > not produce a multi-module site tree. > Module Tree > simple-parent/pom.xml > simple-parent/simple-model/pom.xml > simple-parent/simple-weather/pom.xml > simple-parent/simple-webapp/pom.xml > Site tree > parent/index.html > simple-model/simple-model/pom.xml > simple-weather/simple-weather/pom.xml > simple-webapp/simple-webapp/pom.xml -- 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] (MJAVADOC-372) Index page should refer to Apache Maven for at least the first mention
[ https://jira.codehaus.org/browse/MJAVADOC-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329033#comment-329033 ] Dennis Lundberg commented on MJAVADOC-372: -- Why? > Index page should refer to Apache Maven for at least the first mention > -- > > Key: MJAVADOC-372 > URL: https://jira.codehaus.org/browse/MJAVADOC-372 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: SebbASF >Priority: Minor > > Index page should refer to Apache Maven for at least the first mention, i.e. > it should start: > Apache Maven Javadoc Plugin > The Apache Maven Javadoc Plugin uses the Javadoc ... -- 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] [Updated] (MPOM-44) Compiler version settings cannot be overridden by defining maven.compiler.source/target
[
https://issues.apache.org/jira/browse/MPOM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPOM-44:
Component/s: (was: maven-plugins)
asf
> Compiler version settings cannot be overridden by defining
> maven.compiler.source/target
> ---
>
> Key: MPOM-44
> URL: https://issues.apache.org/jira/browse/MPOM-44
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-13
>Reporter: Sebb
> Attachments: MPOM-44-extended.patch, MPOM-44.patch
>
>
> The compiler plugin by default picks up the source and target from the
> properties
> maven.compiler.source and maven.compiler.target.
> Unfortunately, the Apache POM uses the following fixed values to specify the
> version:
> {code}
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.5.1
>
> 1.4
> 1.4
>
> {code}
> This means that child poms which use the properties expecting them to be
> honoured have to override the configuration as follows:
> {code}
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> ${maven.compile.source}
> ${maven.compile.target}
>
>
> {code}
> This is unnecessary and wrong.
> For compatibility, the Apache Pom does need to still specify the default
> source/target as 1.4 (the plugin default is 1.5), but it should do so by
> using the standard properties which can then be overridden.
> In fact, if the properties are defined, the compiler plugin config could be
> dropped, as it is the default behaviour.
--
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] (MCHANGES-312) Empty jira report when REST API fails
[ https://jira.codehaus.org/browse/MCHANGES-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329034#comment-329034 ] Dennis Lundberg commented on MCHANGES-312: -- HI, Why would a call to /rest/api/2/status time out? What would you like to happen if it does time out? > Empty jira report when REST API fails > - > > Key: MCHANGES-312 > URL: https://jira.codehaus.org/browse/MCHANGES-312 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.9 >Reporter: Corey Schooler > > When a call to "/rest/api/2/status" times out, the jira report ends up empty. > Even when attempting to forceRss, the code attempts to make REST calls as > long as a call to "/rest/api/2/serverInfo" returns an "OK" status. If any > rest call fails after a successful serverInfo call on line 120 in > RestJiraDownloader, the jira report ends up empty. > Stack trace: > org.apache.cxf.jaxrs.client.ClientWebApplicationException: > org.apache.cxf.jaxrs.client.ClientWebApplicationException: > org.apache.cxf.interceptor.Fault: Could not send Message. > at > org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:807) > at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:743) > at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:717) > at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:262) > at org.apache.cxf.jaxrs.client.WebClient.get(WebClient.java:288) > at > org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:230) > at > org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:206) > at > org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:128) > at > org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367) > 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:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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.apache.cxf.jaxrs.client.ClientWebApplicationException: > org.apache.cxf.interceptor.Fault: Could not send Message. > at > org.apache.cxf.jaxrs.client.AbstractClient.checkClientException(AbstractClient.java:497) > at > org.apache.cxf.jaxrs.client.AbstractClient.preProcessResult(AbstractClie
[jira] (MNGSITE-181) http://repo.maven.apache.org/maven2/ is not browsable any more
[ https://jira.codehaus.org/browse/MNGSITE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNGSITE-181. --- Resolution: Fixed Assignee: Dennis Lundberg Fixed in [r1505043|http://svn.apache.org/viewvc?view=revision&revision=1505043]. > http://repo.maven.apache.org/maven2/ is not browsable any more > -- > > Key: MNGSITE-181 > URL: https://jira.codehaus.org/browse/MNGSITE-181 > Project: Maven Project Web Site > Issue Type: Bug > Environment: > http://maven.apache.org/plugins/#Supported_By_The_Maven_Project >Reporter: SebbASF >Assignee: Dennis Lundberg >Priority: Minor > > The link http://maven.apache.org/plugins/#Supported_By_The_Maven_Project > says: > "To see the most up-to-date list browse the Maven repository at > http://repo.maven.apache.org/maven2/"; > However that is not browsable. > The text should drop that link, e.g. becoming: > To see the most up-to-date list browse the Maven repository starting at the > org/apache/maven/plugins subfolder. -- 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] (MCHECKSTYLE-193) Resource files get included regardless of explicit sourceDirectory / includes / excludes configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329036#comment-329036 ] Dennis Lundberg commented on MCHECKSTYLE-193: - Hi, This is because of MCHECKSTYLE-184, which is a new feature in maven-checkstyle-plugin. > Resource files get included regardless of explicit sourceDirectory / includes > / excludes configuration > -- > > Key: MCHECKSTYLE-193 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-193 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Oleg Kalnichevski > > Resource files get included into checkstyle audit regardless of explicit > sourceDirectory / includes / excludes configuration, which seems wrong to me. > I found no way of forcing version 2.10 to revert to the behavior of version > 2.9.1 with regards to project resources. -- 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] (MPIR-282) Allow customisation via a parent POM
[
https://jira.codehaus.org/browse/MPIR-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329037#comment-329037
]
Dennis Lundberg commented on MPIR-282:
--
Until this is supported out of the box here's a way to do it:
# Create a small utility project that produces a zip file containing your
properties-files.
# Add an execution to the build of your real project that does
"dependency:unpack" to unpack the zip file into the /src/site/custom directory
> Allow customisation via a parent POM
>
>
> Key: MPIR-282
> URL: https://jira.codehaus.org/browse/MPIR-282
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
>Reporter: SebbASF
>
> Individual projects can easily customise the PIR report text by providing
> replacement properties in a custom bundle at
> ${project.basedir}/src/site/custom/project-info-report.properties
> It would be useful for projects which share a common parent pom (e.g. Apache
> Commons) to be able to share a custom bundle.
--
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] (MECLIPSE-743) Add support for generation of attributes
Mitko Kolev created MECLIPSE-743:
Summary: Add support for generation of
attributes
Key: MECLIPSE-743
URL: https://jira.codehaus.org/browse/MECLIPSE-743
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: WTP support
Affects Versions: 2.9
Reporter: Mitko Kolev
Currently it is not possible to configure attributes for the
{{}} element. The goal is to be able to generate classpath
entries wth attributes:
--
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] (MECLIPSE-743) Add support for generation of attributes
[
https://jira.codehaus.org/browse/MECLIPSE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitko Kolev updated MECLIPSE-743:
-
Component/s: (was: WTP support)
Core : Dependencies resolution and build path (.classpath)
> Add support for generation of attributes
> -
>
> Key: MECLIPSE-743
> URL: https://jira.codehaus.org/browse/MECLIPSE-743
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Affects Versions: 2.9
>Reporter: Mitko Kolev
>
> Currently it is not possible to configure attributes for the
> {{}} element. The goal is to be able to generate
> classpath entries wth attributes:
>
>
>
>value="/WEB-INF/lib"/>
>
>
--
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
