[jira] (MJAVADOC-402) Wrong API link with JDK 1.8
[
https://jira.codehaus.org/browse/MJAVADOC-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351835#comment-351835
]
Mark Rekveld commented on MJAVADOC-402:
---
I have this same issue and the fix is in MJAVADOC-397
As a workaround you can override the {{api_1.7}} in the {{javaApiLinks}}
properties
{code:language=xml}
api_1.7
http://docs.oracle.com/javase/8/docs/api/
{code}
> Wrong API link with JDK 1.8
> ---
>
> Key: MJAVADOC-402
> URL: https://jira.codehaus.org/browse/MJAVADOC-402
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mathieu Boretti
>
> When using JDK 1.8, the link to the java API is wrong (goes to the JDK 1.7).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAR-139) New option to avoid empty jar creation
[ https://jira.codehaus.org/browse/MJAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291978#comment-291978 ] Mark Rekveld commented on MJAR-139: --- Great, I'll update my poms to. Cheers, Mark > New option to avoid empty jar creation > -- > > Key: MJAR-139 > URL: https://jira.codehaus.org/browse/MJAR-139 > Project: Maven 2.x JAR Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Roman Ivanov >Assignee: Kristian Rosenvold > Fix For: 2.4 > > Attachments: MJAR-139.patch > > > Usage of "test-jar" is beneficial for all project, as all of them have tests. > > org.apache.maven.plugins > maven-jar-plugin > 2.3.1 > > > > test-jar > > > > > Pom artifacts and some jar artifacts does not have test and will never have > them. > In logs we have: "[WARNING] JAR will be empty - no content was marked for > inclusion!" > and empty and useless artifacts are created, deployed , ... > It will be convenient to have an plugin option to define whether skip empty > jar creation and warning or generate jar with warning in log. Does it make > sense ? > By default option will be FALSE, to comply with previous behavior. -- 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] Updated: (MJAR-139) New option to avoid empty jar creation
[
https://jira.codehaus.org/browse/MJAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Rekveld updated MJAR-139:
--
Attachment: MJAR-139.patch
I took a look at the code and found a simple way to get this fixed.
In the {{AbstractJarMojo}} class, I added a parameter called {{skipIfEmpty}}
with a default value of false, this so not the change the behavior if the
parameter is not set.
If this flag is set to {{true}} and the {{getClassesDirectory()}} method
returns a directory that doesn't exist, then the archive creation will be
skipped.
But if it is set to {{false}} (or default) then the archive will be created
even if it is empty.
(i) This also applies to the jar goal.
Please take a look at the attached patch, no tests included.
I have deployed this patch in the 2.3.1-marvelution-1 version of the plugin
that is available here:
http://repository.marvelution.com/content/repositories/releases/
Cheers,
Mark
> New option to avoid empty jar creation
> --
>
> Key: MJAR-139
> URL: https://jira.codehaus.org/browse/MJAR-139
> Project: Maven 2.x JAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.3.1
>Reporter: Roman Ivanov
> Attachments: MJAR-139.patch
>
>
> Usage of "test-jar" is beneficial for all project, as all of them have tests.
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.3.1
>
>
>
> test-jar
>
>
>
>
> Pom artifacts and some jar artifacts does not have test and will never have
> them.
> In logs we have: "[WARNING] JAR will be empty - no content was marked for
> inclusion!"
> and empty and useless artifacts are created, deployed , ...
> It will be convenient to have an plugin option to define whether skip empty
> jar creation and warning or generate jar with warning in log. Does it make
> sense ?
> By default option will be FALSE, to comply with previous behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
