Hello there,
one other idea:
* see https://maven.apache.org/pom.html#The_Super_POM
* release:perform activates the release-profile
* inside of the release-profile an execution attach-sources is
defined, which maybe does not inherit your configuration?
Regards
Mirko
Regards Mirko
--
On Thu, Mar 15, 2018 at 1:38 AM Thomas Broyer wrote:
> Be careful in your testing: javadoc:javadoc forks a lifecycle at
> 'generate-sources' phase (and javadoc:aggregate at 'compile' phase),
> whereas javadoc:jar does not!
>
An excellent point.
> So running 'mvn
Be careful in your testing: javadoc:javadoc forks a lifecycle at
'generate-sources' phase (and javadoc:aggregate at 'compile' phase),
whereas javadoc:jar does not!
So running 'mvn javadoc:jar' alone indeed won't run your protoc plugin,
which won't add the generated sources as a compile source
strange
can you provide a test project, please?
Regards,
Hervé
Le mardi 13 mars 2018, 18:56:45 CET Laird Nelson a écrit :
> I am finding that the sourcepath for javadoc:jar (when run as part of the
> release profile) is different from the sourcepath for javadoc:javadoc in my
> project that
I can confirm this :(
Spent several hours trying to release
Finaly fixed all javadoc warnings
WBR, Maxim
(from mobile, sorry for the typos)
On Wed, Mar 14, 2018, 00:57 Laird Nelson wrote:
> I am finding that the sourcepath for javadoc:jar (when run as part of the
>
I am finding that the sourcepath for javadoc:jar (when run as part of the
release profile) is different from the sourcepath for javadoc:javadoc in my
project that involves (protoc-) generated sources.
(The net effect is that at release time, everything works fine up until
release:perform, which