incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Pablo Santos Rodríguez (JIRA) <>
Subject [jira] [Commented] (JSPWIKI-738) Dependencies should not be distributed with source archive
Date Sun, 05 Aug 2012 22:46:02 GMT


Juan Pablo Santos Rodríguez commented on JSPWIKI-738:

Hello Florian,

there are several things to note:

The download mechanism: it was introduced because having external jars in the source code
is considered against Apache principles, which was noted in the follow-up of the [July status
Keeping the jars in libs tests/libs will most probably be a blocker for IPMC.

The growing libs directory: I'm thinking we could avoid that problem by directly download
them from Central, except for sandler and freshcookies-security, which are not available there.

maven ant tasks: to introduce cobertura and sonar support we needed some (L)GPL jars, which
we couldn't have in our SVN repository, hence the mechanism to download them. I was thinking
of downloading all dependencies via these tasks, but as sandler and freshcookies-security
are not published on central, so may be we could just download the needed jars from central
and get rid off these tasks. Thoughts?

> Dependencies should not be distributed with source archive
> ----------------------------------------------------------
>                 Key: JSPWIKI-738
>                 URL:
>             Project: JSPWiki
>          Issue Type: Task
>    Affects Versions: Graduating, 2.9
>            Reporter: Juan Pablo Santos Rodríguez
>            Assignee: Juan Pablo Santos Rodríguez
>             Fix For: Graduating, 2.9
> As pointed out in the revision of the July 2012 incubation report, JSPWiki ships binary
dependencies in the source archive, which is contrary to Apache principles.
> As we are downloading some dependencies in current trunk, I would take the path of downloading
all needed jars. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message