You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/10/26 09:55:50 UTC
[jira] Created: (SLING-83) Improve our Maven modules layout to make
Sling easier to understand
Improve our Maven modules layout to make Sling easier to understand
-------------------------------------------------------------------
Key: SLING-83
URL: https://issues.apache.org/jira/browse/SLING-83
Project: Sling
Issue Type: Improvement
Reporter: Bertrand Delacretaz
As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
sling-api (used by both microsling and sling)
microsling
- microsling-webapp (uses sling-api)
- microsling-cargo-testing (I'm planning to write some integration tests)
sling
- sling-osgi (osgi-related modules, console, ...)
- sling-jcr (JCR utility modules, wrappers, ...)
- sling-jsp (jasper compiler, JSP script engine, ...)
- sling-core
- sling-commons (was not on the mailing list proposal, but probably useful)
- ...
sling-maven-plugins
- ... existing plugins
[1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by Carsten Ziegeler <cz...@apache.org>.
Felix Meschberger schrieb:
> Hi all,
>
> Here is my proposal
> http://cwiki.apache.org/confluence/display/SLING/Module
> +Reorganization+Proposal
>
> Please comment. Thanks.
>
Looks good to me - additionally I would drop the cache sub project in
sling as it is currently empty.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [jira] Created: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by Felix Meschberger <fm...@gmail.com>.
Hi all,
Here is my proposal
http://cwiki.apache.org/confluence/display/SLING/Module
+Reorganization+Proposal
Please comment. Thanks.
Am Freitag, den 26.10.2007, 10:58 +0200 schrieb Carsten Ziegeler:
> No one picked up my great suggestion of calling the "big sling" catapult
> (sniff) :(
Yet another name :-)
Regards
Felix
>
> Carsten
>
> Bertrand Delacretaz (JIRA) wrote:
> > Improve our Maven modules layout to make Sling easier to understand
> > -------------------------------------------------------------------
> >
> > Key: SLING-83
> > URL: https://issues.apache.org/jira/browse/SLING-83
> > Project: Sling
> > Issue Type: Improvement
> > Reporter: Bertrand Delacretaz
> >
> >
> > As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> >
> > The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> >
> > sling-api (used by both microsling and sling)
> > microsling
> > - microsling-webapp (uses sling-api)
> > - microsling-cargo-testing (I'm planning to write some integration tests)
> > sling
> > - sling-osgi (osgi-related modules, console, ...)
> > - sling-jcr (JCR utility modules, wrappers, ...)
> > - sling-jsp (jasper compiler, JSP script engine, ...)
> > - sling-core
> > - sling-commons (was not on the mailing list proposal, but probably useful)
> > - ...
> > sling-maven-plugins
> > - ... existing plugins
> >
> > [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
> >
>
>
Re: [jira] Created: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by Carsten Ziegeler <cz...@apache.org>.
No one picked up my great suggestion of calling the "big sling" catapult
(sniff) :(
Carsten
Bertrand Delacretaz (JIRA) wrote:
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
>
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
>
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
>
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
>
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
>
--
Carsten Ziegeler
cziegeler@apache.org
[jira] Commented: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539921 ]
Bertrand Delacretaz commented on SLING-83:
------------------------------------------
The recently added sling-json module is a good example of what might go into sling-commons.
And I'd put the microsling script engines there as well, unless we have a sling-scripting module to contain them (see SLING-97).
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned SLING-83:
--------------------------------------
Assignee: Felix Meschberger
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540362 ]
Felix Meschberger commented on SLING-83:
----------------------------------------
Proposed structure can be found here: http://cwiki.apache.org/confluence/display/SLING/Module+Reorganization+Proposal
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-83) Improve our Maven modules layout to make
Sling easier to understand
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-83.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Closing this issue as module reorganization is done.
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-83) Improve our Maven modules layout to
make Sling easier to understand
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540409 ]
Felix Meschberger commented on SLING-83:
----------------------------------------
Created branch Sling_Component_API with the current module structure. To switch the current checkout use the svn switch command.
See http://markmail.org/message/n3pmmdzjvfpzzgnd
> Improve our Maven modules layout to make Sling easier to understand
> -------------------------------------------------------------------
>
> Key: SLING-83
> URL: https://issues.apache.org/jira/browse/SLING-83
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
>
> As discussed on sling-dev [1], we'd like to restructure our source code, to split Sling in smaller pieces and make it easier to understand what is what.
> The suggested Maven modules are as follows. That's the general idea, details will have to be filled in.
> sling-api (used by both microsling and sling)
> microsling
> - microsling-webapp (uses sling-api)
> - microsling-cargo-testing (I'm planning to write some integration tests)
> sling
> - sling-osgi (osgi-related modules, console, ...)
> - sling-jcr (JCR utility modules, wrappers, ...)
> - sling-jsp (jasper compiler, JSP script engine, ...)
> - sling-core
> - sling-commons (was not on the mailing list proposal, but probably useful)
> - ...
> sling-maven-plugins
> - ... existing plugins
> [1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.