You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (Created) (JIRA)" <ji...@apache.org> on 2012/03/09 07:59:57 UTC
[jira] [Created] (OPENMEETINGS-86) SVN directory structure need to
be optimized
SVN directory structure need to be optimized
--------------------------------------------
Key: OPENMEETINGS-86
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-86
Project: Openmeetings
Issue Type: Improvement
Components: BuildsAndReleases
Affects Versions: 2.0 Apache Incubator Release
Reporter: Maxim Solodovnik
Assignee: Maxim Solodovnik
Right now we have really messy project structure:
bin (ant intermediate folder for classes)
build (eclipse folder for classes)
build.xml + build file
derby.log (derdy DB log)
dist (ant folder fo build artifacts)
docs (HTML documentation generated from xdocs)
filetest.keystore (keystore generated by ant)
ivysettings.xml + ivy configuration file
ivy.xml + ivy configuration file
junitreport (ant generated folder for junit reports)
lib +- folder with initial and downloaded libraries
LICENSE + apache license
log (red5 log from junit tests)
openlaszlo (downloaded openlaszlo sources)
openmeetings (derby DB generated by junit)
red5 (downloaded red5)
screen_compile (classes of screenshare client)
src + java sources
test +- not sure
velocity.log (log generated by velocity)
WebContent + various sources
xdocs + documentation
project root is full of generated data. I propose to reorganize it
move all generated (including docs) into let's say "build" folder and make it better structured
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-86) SVN directory structure need to
be optimized
Posted by "Maxim Solodovnik (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-86.
------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0 Apache Incubator Release
Assignee: SebastianWagner (was: Maxim Solodovnik)
done
Sebastian, could you please review the new structure?
> SVN directory structure need to be optimized
> --------------------------------------------
>
> Key: OPENMEETINGS-86
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-86
> Project: Openmeetings
> Issue Type: Improvement
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Maxim Solodovnik
> Assignee: SebastianWagner
> Fix For: 2.0 Apache Incubator Release
>
>
> Right now we have really messy project structure:
> bin (ant intermediate folder for classes)
> build (eclipse folder for classes)
> build.xml + build file
> derby.log (derdy DB log)
> dist (ant folder fo build artifacts)
> docs (HTML documentation generated from xdocs)
> filetest.keystore (keystore generated by ant)
> ivysettings.xml + ivy configuration file
> ivy.xml + ivy configuration file
> junitreport (ant generated folder for junit reports)
> lib +- folder with initial and downloaded libraries
> LICENSE + apache license
> log (red5 log from junit tests)
> openlaszlo (downloaded openlaszlo sources)
> openmeetings (derby DB generated by junit)
> red5 (downloaded red5)
> screen_compile (classes of screenshare client)
> src + java sources
> test +- not sure
> velocity.log (log generated by velocity)
> WebContent + various sources
> xdocs + documentation
> project root is full of generated data. I propose to reorganize it
> move all generated (including docs) into let's say "build" folder and make it better structured
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-86) SVN directory structure need to
be optimized
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-86.
----------------------------------------
Assignee: Maxim Solodovnik (was: SebastianWagner)
Closing all old 'Resolved' issues
> SVN directory structure need to be optimized
> --------------------------------------------
>
> Key: OPENMEETINGS-86
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-86
> Project: Openmeetings
> Issue Type: Improvement
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> Right now we have really messy project structure:
> bin (ant intermediate folder for classes)
> build (eclipse folder for classes)
> build.xml + build file
> derby.log (derdy DB log)
> dist (ant folder fo build artifacts)
> docs (HTML documentation generated from xdocs)
> filetest.keystore (keystore generated by ant)
> ivysettings.xml + ivy configuration file
> ivy.xml + ivy configuration file
> junitreport (ant generated folder for junit reports)
> lib +- folder with initial and downloaded libraries
> LICENSE + apache license
> log (red5 log from junit tests)
> openlaszlo (downloaded openlaszlo sources)
> openmeetings (derby DB generated by junit)
> red5 (downloaded red5)
> screen_compile (classes of screenshare client)
> src + java sources
> test +- not sure
> velocity.log (log generated by velocity)
> WebContent + various sources
> xdocs + documentation
> project root is full of generated data. I propose to reorganize it
> move all generated (including docs) into let's say "build" folder and make it better structured
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira