[
https://issues.apache.org/jira/browse/ABDERA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590668#action_12590668
]
dandiep edited comment on ABDERA-115 at 4/18/08 7:15 PM:
---------------------------------------------------------------
I am completely against moving toward a *single* source folder/tree and getting
rid of the modules if thats what you're proposing. Its bad from a separation of
concerns point of view and often results in unwanted coupling.
was (Author: dandiep):
I am completely against moving toward a source folder/tree and getting rid
of the modules if thats what you're proposing. Its bad from a separation of
concerns point of view and often results in unwanted coupling.
> Distribution repackaging
> ------------------------
>
> Key: ABDERA-115
> URL: https://issues.apache.org/jira/browse/ABDERA-115
> Project: Abdera
> Issue Type: Wish
> Affects Versions: 0.4.0
> Reporter: Remy Gendron
> Priority: Minor
>
> To simplify project configuration and help when I will give ownership of my
> current project to someone else.
> The distribution packaging should be remodeled so that including abdera.jar
> and abdera-src.jar in the build path is the only action required.
> I would also make a distinction in the folders hierarchy between runtime and
> compile time external dependencies.
> Abdera could become a single project, which would simplify and encourage
> involvement from the community. The build process would be responsible for
> creating a suite of module jars as well as one big, friendly abdera.jar that
> includes everything.
> The Spring framework would be a good example to follow.
> Thanks again for the great work!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
