Hi Hervé,
I tested it on maven-scm-publish-plugin, since it is quite little and
I'll
intend to make a release in a week or so
you can see the result here [1]
of course, the download link doesn't work because it is a non-released
SNAPSHOT
Yeah but the result looks great...
As expected, seing it in a generated site gave me my first improvement idea: do
no link to svn but to http site
Hm...you are talking about the usual linke in source-repository.html ?
Other ideas:
- perhaps we should disable MPIR license report (Project License)
We should think of ...
- there is not use of mirrors, which is asked in [2]: I don't know if it is a
real problem, since I don't think much people will download it, or perhaps
users that don't understand that they are downloading source
But currently the download.cgi is used for the download link...looks ok
to me...
Kind regards
Karl-Heinz Marbaise
Any other thoughts?
Regards,
Hervé
[1] http://maven.apache.org/plugins-archives/maven-scm-publish-plugin-LATEST/
[2] http://www.apache.org/dist/
Le dimanche 27 avril 2014 14:36:30 Karl Heinz Marbaise a écrit :
Hi,
> Hi,
this can even be added in plugin parent pom, to avoid copy/paste in every
plugin
Would be great...
did you try to commit such a change and deploy the site to show the
result?
No i didn't yet....
Kind regards
Karl-Heinz
Regards,
Hervé
Le dimanche 27 avril 2014 11:37:58 Karl Heinz Marbaise a écrit :
Hi,
Currently i've taken a deep look into the above issue..
Currently i can provide a temporarily solution like adding the links to
the site for all plugins like this:
--- maven-shade-plugin/src/site/site.xml (revision 1590367)
+++ maven-shade-plugin/src/site/site.xml (working copy)
@@ -28,6 +28,9 @@
<item name="Goals" href="plugin-info.html"/>
<item name="Usage" href="usage.html"/>
<item name="FAQ" href="faq.html"/>
+ <!-- According to http://jira.codehaus.org/browse/MNGSITE-152 -->
+ <item name="License" href="http://www.apache.org/licenses/"/>
+ <item name="Download"
href="https://dist.apache.org/repos/dist/release/maven/plugins/${project.
art ifactId}-${project.version}-source-release.zip "/>
</menu>
<menu name="Examples">
<item name="Selecting Contents for Uber JAR"
href="examples/includes-excludes.html"/>
Do we have a better solution for this kind of thing? What do you think?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
