[
https://issues.apache.org/jira/browse/JAMES-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juhan Aasaru updated JAMES-3395:
--------------------------------
Description:
Currently examples define james-project as its parent:
[https://github.com/apache/james-project/blob/master/examples/pom.xml#L23]
This is why some of the dependencies currently get loaded from the parent. For
example custom-mailets require dependency apache-mailet-api which is not
explicitly defined in its pom but resolved from the parent.
I suggest removing reference to parent from pom.xml of examples and adding the
required dependencies directly to individual example pom-s.
Example scenario: someone wants create its own custom mailets then this person
can take custom-mailets as the foundation without the need to depend on whole
james-server.
Secondly - examples should not be under the package "org.apache.james". This
can introduce errors where example code uses something from James that has
package level access. I propose moving examples to "org.apache.examples.james"
package
I would like to work on this.
was:
Currently examples define james-project as its parent:
[https://github.com/apache/james-project/blob/master/examples/pom.xml#L23]
This is why some of the dependencies currently get loaded from the parent. For
example custom-mailets require dependency apache-mailet-api which is not
explicitly defined in its pom but resolved from the parent.
I suggest removing reference to parent from pom.xml of examples and adding the
required dependencies directly to individual example pom-s.
Example scenario: someone wants create its own custom mailets then this person
can take custom-mailets as the foundation without the need to depend on whole
james-server.
I would like to work on this.
> examples should not extend from james-project
> ---------------------------------------------
>
> Key: JAMES-3395
> URL: https://issues.apache.org/jira/browse/JAMES-3395
> Project: James Server
> Issue Type: Bug
> Reporter: Juhan Aasaru
> Priority: Major
>
> Currently examples define james-project as its parent:
> [https://github.com/apache/james-project/blob/master/examples/pom.xml#L23]
> This is why some of the dependencies currently get loaded from the parent.
> For example custom-mailets require dependency apache-mailet-api which is not
> explicitly defined in its pom but resolved from the parent.
> I suggest removing reference to parent from pom.xml of examples and adding
> the required dependencies directly to individual example pom-s.
> Example scenario: someone wants create its own custom mailets then this
> person can take custom-mailets as the foundation without the need to depend
> on whole james-server.
>
> Secondly - examples should not be under the package "org.apache.james". This
> can introduce errors where example code uses something from James that has
> package level access. I propose moving examples to
> "org.apache.examples.james" package
>
> I would like to work on this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
