Hi Peter,
As I have just mentioned to Jure, it would be great if you would
consider registering at https://issues.apache.org/bloodhound/register if
you haven't already. In addition to being able to assign #187 to you, I
can also then make sure that you can edit the wiki pages if you think
you have found other problems.
Cheers,
Gary
On 09/18/2012 06:18 AM, Peter Koželj wrote:
The layout I got was achieved by requirements-dev.txt (that is actually the
one mentioned in the contributing doc).
Peter
On Tue, Sep 18, 2012 at 2:49 AM, Olemis Lang <[email protected]> wrote:
What about when using requirements-dev.txt file ? ... even if probably
undocumented
On 9/17/12, Gary Martin <[email protected]> wrote:
Hi,
Updated in an attempt to better describe code locations in response to
the problem pointed out by Peter Koželj. There might be a case for also
listing the locations of the code for the different major parts of the
code to help with initial navigation.
Cheers,
Gary
On 09/17/2012 12:21 PM, Apache Bloodhound wrote:
Page "BloodhoundContributing" was changed by gjm
Diff URL:
<
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing?action=diff&version=9
Revision 9
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundContributing
=========================================================================
--- BloodhoundContributing (version: 8)
+++ BloodhoundContributing (version: 9)
@@ -29,7 +29,7 @@
tracd -r --port=8000 bloodhound/environments/main
}}}
-With this method of installation, the source code for Trac,
!TracAccountManager and !BloodhoundMultiProduct packages (along with
future modules that are installed by default) will be found in
{{{bloodhound/src/}}}.
+With this method of installation, the Bloodhound and Trac code is run
direct from the checked out code. Any source code for external
dependencies and plugins meanwhile will be found in
{{{../installer/bloodhound/src/}}}.
You should find that when you make changes to the associated source
code, when using the {{{-r}}} option on {{{tracd}}}, the server will
reload and the edited code will be run instead of the original. In order
to get templates to reload after modifications are made, you can edit
{{{bloodhound/environments/main/conf/trac.ini}}} and add the following
line to the {{{[trac]}}} section:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
--
Page URL:
<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundContributing' page.
If it was not you, please report to .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
