Community
Participate
Working Groups
These are the proposed steps to return Sequoyah to a maintainable state for the sake of addressing Andmore bug reports: 1. Check out archived Sequoyah project at https://eclipse.googlesource.com/sequoyah 2. Convert the trunk to a Maven project using Andmore as an Eclipse project template. 3. Update project to use archives available from current online repositories 4. Update the Java version to 1.8 5. Import the Mavenized Sequoyah project into Andmore as a main module - peers are andmore-core, android-core and android-swt. At stage 4. we have a Maven project ready to be placed in an independent Eclipse project. The essential elements of the original project, including copyright and license information are retained. The project is in a working state, so it is mostly an administrative challenge to proceed. Stage 5. need only be a temporary step to avoid holding up Andmore bug resolution. However, as Andmore seems to be the only consumer of Sequoyah and uses it in a significant way, it may make sense to bring the two together into a single project. The proposed Sequoyah integration into Andmore can be examined by cloning https://github.com/Kys3rK1ng/andmore.
We actually have the Sequoyah Git repository here, Wayne should be able to provide more information on retrieving it. So we can eliminate step 1. Step 2 we will need to convert to a Maven project just to make sure it builds.
> Step 2 we will need to convert to a Maven project just to make sure it builds. If I understand right, all the proposed steps are already performed in the demo repository https://github.com/Kys3rK1ng/andmore and just awaiting approval?
