how to compile icescrum from source code, any blog shows the details?

[PipC]

If I want to debug icescrum, any blog have the details showing us the steps by steps to setup the development environment?

[SantoshNII]

I am also looking for the same, can anyone please help us out with this?

@noullet: Could you please help us out.

[ceagan]

Since there doesn't appear to be much interest in providing this documentation, I tried to write some. I was able to generate a war file (untested) and wrote up the steps here: https://gist.github.com/ceagan/cd478be3d800b6755214f3d845c3035a

[noullet]

Hello Chris,

Thanks for your contribution! Actually, we are very interested in providing such documentation explaining how to build iceScrum.

The problem is that it is only a very small part of the effort needed to help the community contribute to iceScrum. We don't want to provide false expectations by only doing the easy part ("here is how to build iceScrum, do your thing!") while we could not provide the rest. As an open-source developer myself, I have already been fooled into thinking that I could contribute to a codebase: I worked on providing detailed and thoughtful pull-request / contributions, only to find out that they were irrelevant to the roadmap or that the organization did not have the resources to review and accept my contribution. We clearly wanted to avoid wasting the efforts of contributors, hence the absence of public incitation to contribute until now.

Of course iceScrum is open source and public so everyone can fork it and change it at their will. However, the result will not be iceScrum anymore. We rather want to improve iceScrum. For that to be possible, we needed a solid basis.

Most of the last years have been dedicated to building this stable modern version of iceScrum: a good architecture, clean code, essential features needed to make it competitive in the agile tooling landscape, ressources to learn how to install it and how to use it...

As of only a few weeks ago, most of this work is done apart from learning ressources that still deserve improvements. We are also thinking of lots of new features, but they are less essential. Thus, it is only recently that it is even possible for us to consider enabling contributions.

Here are some of the activities that are required to do so:

• Write the documentation that explains how to build iceScrum from the sources (easy)
• Write the code style guide (easy)
• Write the documentation that explains how iceScrum works (hard)
• Write the documentation that explains how to contribute to the core of iceScrum (hard)
• Make our roadmap public to avoid competing or useless efforts (easy)

This is only the part needed to contribute to the core of iceScrum.

Additional / non-essential features should not go in the core. They should rather be provided by plugins that can add new views, new business items, integrations etc. to iceScrum. The plugin architecture is already there and fully functional. However, additional efforts are needed:

• Write the documentation that explains how to write a plugin (hard)
• Invent a process for plugin submission / publication / integration in official builds (hard)

Writing / building all of the above represents a lot of work and investment. However, this would still be only a small part of it. Indeed, this also entails maintaining all the resources above, helping contributors, reviewing contributions...

Needless to say, we are not there yet. We welcome all community effort such as yours! But many of the resources that will allow for more external contributions require in-house efforts first, that is why we also need financial support from companies that use iceScrum for free and make good money from it. What they give back to us, we can give back to the whole community.