[jira] [Issue Comment Deleted] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1575:
--
Comment: was deleted

(was: This patch update the james-mailbox mime4j and james-project version used.

Contributed by Matthieu Beachler.)

> James should use latest version of other James subprojects
> --
>
> Key: JAMES-1575
> URL: https://issues.apache.org/jira/browse/JAMES-1575
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: 3.0.0-beta5
>Reporter: Tellier Benoit
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch, 
> 0001-JAMES-1575-update-shade-plugin-to-prevent-a-bug-in-a.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In James, this means :
> Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
> Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
> Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2
> To build this project with modern JDK, we also need the directory 
> /app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (MAILBOX-230) Mailbox should use latest version of other James subprojects

[Antoine Duprat (JIRA)]

Antoine Duprat created MAILBOX-230:
--

 Summary: Mailbox should use latest version of other James 
subprojects
 Key: MAILBOX-230
 URL: https://issues.apache.org/jira/browse/MAILBOX-230
 Project: James Mailbox
  Issue Type: Improvement
Reporter: Antoine Duprat
 Fix For: 0.6


We want an integration tool that builds the entire James project in its latest 
version.

To do that, each james project needs to use the latest version of all other 
James subprojects.

In JDKIM, this means :

- Update mailet version
- Update james-project version
- Update mime4j version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JDKIM-34) JDKIM should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JDKIM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JDKIM-34:

Attachment: 0001-JDKIM-34-update-james-related-projects-to-SNAPSHOT-v.patch

Contributed by Matthieu Baechlor 

Solves the issue

> JDKIM should use latest version of other James subprojects
> --
>
> Key: JDKIM-34
> URL: https://issues.apache.org/jira/browse/JDKIM-34
> Project: James jDKIM
>  Issue Type: Improvement
>Reporter: Tellier Benoit
> Attachments: 
> 0001-JDKIM-34-update-james-related-projects-to-SNAPSHOT-v.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In JDKIM, this means :
>  - Update mailet version
>  - Update mime4j version ( update Mime config creation )
>  - Update james project version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

Tellier Benoit created JAMES-1575:
-

 Summary: James should use latest version of other James subprojects
 Key: JAMES-1575
 URL: https://issues.apache.org/jira/browse/JAMES-1575
 Project: James Server
  Issue Type: Improvement
  Components: Build System
Affects Versions: 3.0.0-beta5
Reporter: Tellier Benoit
 Fix For: 3.0.0-beta5


We want an integration tool that builds the entire James project in its latest 
version.

To do that, each james project needs to use the latest version of all other 
James subprojects.

In James, this means :

Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2

To build this project with modern JDK, we also need the directory 
/app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (JSIEVE-97) James JSieve should use latest version of other James subprojects

[Matthieu Baechler (JIRA)]

Matthieu Baechler created JSIEVE-97:
---

 Summary: James JSieve should use latest version of other James 
subprojects
 Key: JSIEVE-97
 URL: https://issues.apache.org/jira/browse/JSIEVE-97
 Project: James jSieve
  Issue Type: Task
  Components: MultiModule
Reporter: Matthieu Baechler
 Fix For: 0.6


It should depend on james-project 1.8.3-SNAPSHOT and mime4j 0.8 to use only 
up-to-date component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (PROTOCOLS-110) James protocols should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTOCOLS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated PROTOCOLS-110:
-
Attachment: 0001-PROTOCOLS-110-Update-ACL-MAILBOX-API-for-ACL-related.patch

This patch update the james-mailbox mime4j and james-project version used.

Contributed by Matthieu Beachler.


> James protocols should use latest version of other James subprojects
> 
>
> Key: PROTOCOLS-110
> URL: https://issues.apache.org/jira/browse/PROTOCOLS-110
> Project: James Protocols
>  Issue Type: Improvement
>Reporter: Tellier Benoit
>Assignee: Eric Charles
> Attachments: 
> 0001-PROTOCOLS-110-Update-ACL-MAILBOX-API-for-ACL-related.patch
>
>
> We need to update Mailbox subproject : we have to match the new ACL API
> We need to update Mime4j to 0.8.0 : we need to remove LenientAddressBuilder
> We need to use james-project 1.8.3-SNAPSHOT .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1575:
--
Attachment: (was: 
0001-PROTOCOLS-110-Update-ACL-MAILBOX-API-for-ACL-related.patch)

> James should use latest version of other James subprojects
> --
>
> Key: JAMES-1575
> URL: https://issues.apache.org/jira/browse/JAMES-1575
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: 3.0.0-beta5
>Reporter: Tellier Benoit
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch, 
> 0001-JAMES-1575-update-shade-plugin-to-prevent-a-bug-in-a.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In James, this means :
> Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
> Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
> Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2
> To build this project with modern JDK, we also need the directory 
> /app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (JSPF-98) JSPF should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

Tellier Benoit created JSPF-98:
--

 Summary: JSPF should use latest version of other James subprojects
 Key: JSPF-98
 URL: https://issues.apache.org/jira/browse/JSPF-98
 Project: James jSPF
  Issue Type: Improvement
Reporter: Tellier Benoit




We want an integration tool that builds the entire James project in its latest 
version.

To do that, each james project needs to use the latest version of all other 
James subprojects.

In JDKIM, this means :

Correct javadoc to not have issue at compile time with doclint
Update to james-project 1.8.3-SNAPSHOT





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (MAILBOX-230) Mailbox should use latest version of other James subprojects

[Antoine Duprat (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MAILBOX-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Duprat updated MAILBOX-230:
---
Attachment: 0002-JWC-111-update-mime4j-to-0.8.0-SNAPSHOT.patch
0001-JWC-111-update-james-related-projects-to-SNAPSHOT-ve.patch

Contributed by Matthieu Baechler.

Solves the issue

> Mailbox should use latest version of other James subprojects
> 
>
> Key: MAILBOX-230
> URL: https://issues.apache.org/jira/browse/MAILBOX-230
> Project: James Mailbox
>  Issue Type: Improvement
>Reporter: Antoine Duprat
> Fix For: 0.6
>
> Attachments: 
> 0001-JWC-111-update-james-related-projects-to-SNAPSHOT-ve.patch, 
> 0002-JWC-111-update-mime4j-to-0.8.0-SNAPSHOT.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In JDKIM, this means :
> - Update mailet version
> - Update james-project version
> - Update mime4j version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (PROTOCOLS-110) James protocols should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

Tellier Benoit created PROTOCOLS-110:


 Summary: James protocols should use latest version of other James 
subprojects
 Key: PROTOCOLS-110
 URL: https://issues.apache.org/jira/browse/PROTOCOLS-110
 Project: James Protocols
  Issue Type: Improvement
Reporter: Tellier Benoit
Assignee: Eric Charles


We need to update Mailbox subproject : we have to match the new ACL API

We need to update Mime4j to 0.8.0 : we need to remove LenientAddressBuilder

We need to use james-project 1.8.3-SNAPSHOT .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1575:
--
Attachment: 0001-PROTOCOLS-110-Update-ACL-MAILBOX-API-for-ACL-related.patch

This patch update the james-mailbox mime4j and james-project version used.

Contributed by Matthieu Beachler.

> James should use latest version of other James subprojects
> --
>
> Key: JAMES-1575
> URL: https://issues.apache.org/jira/browse/JAMES-1575
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: 3.0.0-beta5
>Reporter: Tellier Benoit
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch, 
> 0001-JAMES-1575-update-shade-plugin-to-prevent-a-bug-in-a.patch, 
> 0001-PROTOCOLS-110-Update-ACL-MAILBOX-API-for-ACL-related.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In James, this means :
> Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
> Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
> Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2
> To build this project with modern JDK, we also need the directory 
> /app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (JDKIM-34) JDKIM should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

Tellier Benoit created JDKIM-34:
---

 Summary: JDKIM should use latest version of other James subprojects
 Key: JDKIM-34
 URL: https://issues.apache.org/jira/browse/JDKIM-34
 Project: James jDKIM
  Issue Type: Improvement
Reporter: Tellier Benoit


We want an integration tool that builds the entire James project in its latest 
version.

To do that, each james project needs to use the latest version of all other 
James subprojects.

In JDKIM, this means :

 - Update mailet version
 - Update mime4j version ( update Mime config creation )
 - Update james project version




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1575:
--
Attachment: 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch

Contributed by Matthieu Baechler.

This patch solves the issue by upgrading the components,
and by creating an empty folder.

> James should use latest version of other James subprojects
> --
>
> Key: JAMES-1575
> URL: https://issues.apache.org/jira/browse/JAMES-1575
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: 3.0.0-beta5
>Reporter: Tellier Benoit
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In James, this means :
> Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
> Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
> Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2
> To build this project with modern JDK, we also need the directory 
> /app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JSPF-98) JSPF should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JSPF-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JSPF-98:
---
Attachment: 0001-JSPF-98-update-james-related-projects-to-SNAPSHOT-ve.patch

Solves the issue.

> JSPF should use latest version of other James subprojects
> -
>
> Key: JSPF-98
> URL: https://issues.apache.org/jira/browse/JSPF-98
> Project: James jSPF
>  Issue Type: Improvement
>Reporter: Tellier Benoit
> Attachments: 
> 0001-JSPF-98-update-james-related-projects-to-SNAPSHOT-ve.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In JDKIM, this means :
> Correct javadoc to not have issue at compile time with doclint
> Update to james-project 1.8.3-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1575) James should use latest version of other James subprojects

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1575:
--
Attachment: 0001-JAMES-1575-update-shade-plugin-to-prevent-a-bug-in-a.patch

I also attach here the patch for James-project ( I do not know were to submit 
it ... ) :

In other James subprojects ( eg : protocols ), when upgrading to james-project 
1.8.3-SNAPSHOT we have a conflicting version of maven-shade-plugin.

An upgrade to 2.3 fix the issue.

> James should use latest version of other James subprojects
> --
>
> Key: JAMES-1575
> URL: https://issues.apache.org/jira/browse/JAMES-1575
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: 3.0.0-beta5
>Reporter: Tellier Benoit
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1575-update-james-related-projects-to-SNAPSHOT.patch, 
> 0001-JAMES-1575-update-shade-plugin-to-prevent-a-bug-in-a.patch
>
>
> We want an integration tool that builds the entire James project in its 
> latest version.
> To do that, each james project needs to use the latest version of all other 
> James subprojects.
> In James, this means :
> Using james-protocols 1.6.4-SNAPSHOT instead of 1.6.3
> Using jspf 1.0.1-SNAPSHOT instead of 1.0.0
> Relying on james-project 1.8.3-SNAPSHOT instead of 1.8.2
> To build this project with modern JDK, we also need the directory 
> /app/src/main/config/war/ to be created



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JSIEVE-97) James JSieve should use latest version of other James subprojects

[Matthieu Baechler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JSIEVE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Baechler updated JSIEVE-97:

Attachment: 0001-JWC-111-Updating-parent-project.patch

This patch update dependencies and fix a call to mime4j.

> James JSieve should use latest version of other James subprojects
> -
>
> Key: JSIEVE-97
> URL: https://issues.apache.org/jira/browse/JSIEVE-97
> Project: James jSieve
>  Issue Type: Task
>  Components: MultiModule
>Reporter: Matthieu Baechler
> Fix For: 0.6
>
> Attachments: 0001-JWC-111-Updating-parent-project.patch
>
>
> It should depend on james-project 1.8.3-SNAPSHOT and mime4j 0.8 to use only 
> up-to-date component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1563) Switch to Maven3

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1563:
--
Attachment: 0001-JAMES-1563-solve-javadoc-generation-on-modern-JDK.patch

In this patch ( that should be applied on james-project 1.8.3-SNAPSHOT ) we :

 - Upgrade maven-site-plugin version
 - Turn off doclint on javadoc generation

> Switch to Maven3
> 
>
> Key: JAMES-1563
> URL: https://issues.apache.org/jira/browse/JAMES-1563
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: Trunk, 3.0.0-beta5
> Environment: Eclipse LUNA with integrated Mave 3.2.1 (m2eclipse)
> Together with Maven 3.2.3 
>Reporter: Bernd Waibel
>Priority: Minor
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1563-solve-javadoc-generation-on-modern-JDK.patch, maven3.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Building with old maven in actual eclipse is some kind outdated.
> It is easy possible to switch to maven 3, with the following changes:
> 1. Eclipse Luna with Maven 3.2.1 is ok for: mvn install, package, clean. Not 
> for mvn site.
> 2. Maven 3.2.3 is ok for mvn install, package, clean, site.
> The Maven 3.2.1 could not build the site, because the structure on 
> "http://repo.maven.apache.org/maven2/"; is wrong. The structure is from 2012 
> and for Maven2, so maybe the structure need to get updated. Nothing I can do.
> For switching to Maven3, which I did, you need to change the pom.xml. Details 
> and patch will follow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-1563) Switch to Maven3

[Tellier Benoit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JAMES-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated JAMES-1563:
--
Attachment: 0001-JAMES-1563-Remove-version-from-maven-site-plugin-as-.patch

The version for maven-site-plugin is hard coded in the mailet submodule.

To generate the documentation for all James subproject, we need to use parent 
maven-site-plugin-version.

> Switch to Maven3
> 
>
> Key: JAMES-1563
> URL: https://issues.apache.org/jira/browse/JAMES-1563
> Project: James Server
>  Issue Type: Improvement
>  Components: Build System
>Affects Versions: Trunk, 3.0.0-beta5
> Environment: Eclipse LUNA with integrated Mave 3.2.1 (m2eclipse)
> Together with Maven 3.2.3 
>Reporter: Bernd Waibel
>Priority: Minor
> Fix For: 3.0.0-beta5
>
> Attachments: 
> 0001-JAMES-1563-Remove-version-from-maven-site-plugin-as-.patch, 
> 0001-JAMES-1563-solve-javadoc-generation-on-modern-JDK.patch, maven3.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Building with old maven in actual eclipse is some kind outdated.
> It is easy possible to switch to maven 3, with the following changes:
> 1. Eclipse Luna with Maven 3.2.1 is ok for: mvn install, package, clean. Not 
> for mvn site.
> 2. Maven 3.2.3 is ok for mvn install, package, clean, site.
> The Maven 3.2.1 could not build the site, because the structure on 
> "http://repo.maven.apache.org/maven2/"; is wrong. The structure is from 2012 
> and for Maven2, so maybe the structure need to get updated. Nothing I can do.
> For switching to Maven3, which I did, you need to change the pom.xml. Details 
> and patch will follow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Commented] (MAILBOX-11) MailboxQuery ignore namespace

[Tellier Benoit (JIRA)]

[ 
https://issues.apache.org/jira/browse/MAILBOX-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519100#comment-14519100
 ] 

Tellier Benoit commented on MAILBOX-11:
---

We want to solve this issue.

We identified the problem : it comes from StoreMailboxManager :: search method :

It relies on the MailboxMapper :: findMailboxWithPathLike. The behaviour of 
this metod is not standardized and differ in each and every implementation.

Then the StoreMailboxMapper selects only mailboxes satisfying the provided 
expression. We can add a check for name and namespace there.

It might be clever to standardize the MailboxMapper :: findMailboxWithPathLike 
method. This means provide standard test, test it in each implementation, and 
finally make the tests pass for each implementations.

> MailboxQuery ignore namespace
> -
>
> Key: MAILBOX-11
> URL: https://issues.apache.org/jira/browse/MAILBOX-11
> Project: James Mailbox
>  Issue Type: Bug
> Environment: Linux, JDK 1.6
>Reporter: François-Denis Gonthier
>Assignee: Norman Maurer
> Fix For: 0.6
>
>
> MailboxQuery doesn't pay any attention to namespace of the mailbox it is 
> based on. For example, Mozilla Thunderbird might to mailbox search with 
> expressions like #private.%. That expression is passed directly to the 
> isExpressionMatch method of the MailboxQuery class. This has obviously 
> incorrect results.
> Arguments to the isExpressionMatch method should be parsed to separate the 
> namespace from the mailbox name or isExpressionMatch should do the parsing 
> itself. In that case the argument name should be renamed to something like 
> 'searchExpression' instead of 'name' which doesn't convey the right meaning.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Build failed in Jenkins: jdkim-trunk #2353

[Apache Jenkins Server]

See 

--
Started by timer
Building remotely on solaris1 (Solaris) in workspace 

java.io.IOException: Failed to install 
http://archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to 
/home/jenkins/tools/maven/apache-maven-3.0.4
at hudson.FilePath.installIfNecessaryFrom(FilePath.java:772)
at 
hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:70)
at 
hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
at 
hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609)
at 
hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:182)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:866)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Caused by: java.io.IOException: Failed to mkdirs: 
/home/jenkins/tools/maven/apache-maven-3.0.4
at hudson.FilePath.mkdirs(FilePath.java:1075)
at hudson.FilePath.installIfNecessaryFrom(FilePath.java:738)
... 15 more
Retrying after 10 seconds
java.io.IOException: Failed to install 
http://archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to 
/home/jenkins/tools/maven/apache-maven-3.0.4
at hudson.FilePath.installIfNecessaryFrom(FilePath.java:772)
at 
hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:70)
at 
hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
at 
hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609)
at 
hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:182)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:866)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Caused by: java.io.IOException: Failed to mkdirs: 
/home/jenkins/tools/maven/apache-maven-3.0.4
at hudson.FilePath.mkdirs(FilePath.java:1075)
at hudson.FilePath.installIfNecessaryFrom(FilePath.java:738)
... 15 more
Retrying after 10 seconds
java.io.IOException: Failed to install 
http://archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to 
/home/jenkins/tools/maven/apache-maven-3.0.4
at hudson.FilePath.installIfNecessaryFrom(FilePath.java:772)
at 
hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:70)
at 
hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
at 
hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609)
at 
hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:182)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:866)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(Resourc

Build failed in Jenkins: james-server-trunk » Apache James :: Server :: Data :: HBase Persistence #5146

[Apache Jenkins Server]

See 


--
[INFO] 
[INFO] 
[INFO] Building Apache James :: Server :: Data :: HBase Persistence 
3.0.0-beta5-SNAPSHOT
[INFO] 
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/maven-metadata.xml
 (2 KB at 2.7 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/apache-james-mailbox-hbase-0.6-20150430.042041-669.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/apache-james-mailbox-hbase-0.6-20150430.042041-669.pom
 (6 KB at 129.0 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/apache-james-mailbox-hbase-0.6-20150430.042041-669-tests.jar
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-james-mailbox-hbase/0.6-SNAPSHOT/apache-james-mailbox-hbase-0.6-20150430.042041-669-tests.jar
 (42 KB at 701.2 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
james-server-data-hbase ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ 
james-server-data-hbase ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
james-server-data-hbase ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ 
james-server-data-hbase ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
james-server-data-hbase ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ 
james-server-data-hbase ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 4 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ 
james-server-data-hbase ---
[INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---
Running org.apache.james.domainlist.hbase.HBaseDomainListTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-log4j12/1.7.2/slf4j-log4j12-1.7.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-simple/1.7.2/slf4j-simple-1.7.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
2015-04-30 04:31:40,385 [main] WARN  
org.apache.hadoop.hdfs.server.namenode.FSNamesystem - The dfs.support.append 
option is in your configuration, however append is not supported. This 
configuration option is no longer required to enable sync.
2015-04-30 04:31:40,635 [main] WARN  
org.apache.hadoop.metrics2.impl

Build failed in Jenkins: james-server-trunk #5146

[Apache Jenkins Server]

See 

--
[...truncated 7963 lines...]
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailetcontainer-api/3.0.0-beta5-20150430.042354-1324/james-server-mailetcontainer-api-3.0.0-beta5-20150430.042354-1324-test-sources.jar
Sending artifact delta relative to james-server-trunk » Apache James :: Server 
:: Mailetcontainer API #5145
Archived 5 artifacts
Archive block size is 32768
Received 0 blocks and 61415 bytes
Compression is 0.0%
Took 0.2 sec
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailets/3.0.0-beta5-SNAPSHOT/james-server-mailets-3.0.0-beta5-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailets/3.0.0-beta5-20150430.043034-1023/james-server-mailets-3.0.0-beta5-20150430.043034-1023.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailets/3.0.0-beta5-20150430.043034-1023/james-server-mailets-3.0.0-beta5-20150430.043034-1023-tests.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailets/3.0.0-beta5-20150430.043034-1023/james-server-mailets-3.0.0-beta5-20150430.043034-1023-sources.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-mailets/3.0.0-beta5-20150430.043034-1023/james-server-mailets-3.0.0-beta5-20150430.043034-1023-test-sources.jar
Sending artifact delta relative to james-server-trunk » Apache James :: Server 
:: Mailets #5145
Archived 5 artifacts
Archive block size is 32768
Received 0 blocks and 451543 bytes
Compression is 0.0%
Took 0.39 sec
[JENKINS] Archiving 

 to 
org.apache.james/james-server-protocols-lmtp/3.0.0-beta5-SNAPSHOT/james-server-protocols-lmtp-3.0.0-beta5-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.james/james-server-protocols-lmtp/3.0.0-beta5-20150430.042816-1083/james-server-protocols-lmtp-3.0.0-beta5-20150430.042816-1083.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-protocols-lmtp/3.0.0-beta5-20150430.042816-1083/james-server-protocols-lmtp-3.0.0-beta5-20150430.042816-1083-tests.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-protocols-lmtp/3.0.0-beta5-20150430.042816-1083/james-server-protocols-lmtp-3.0.0-beta5-20150430.042816-1083-sources.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-protocols-lmtp/3.0.0-beta5-20150430.042816-1083/james-server-protocols-lmtp-3.0.0-beta5-20150430.042816-1083-test-sources.jar
Sending artifact delta relative to james-server-trunk » Apache James :: Server 
:: LMTP #5145
Archived 5 artifacts
Archive block size is 32768
Received 0 blocks and 70712 bytes
Compression is 0.0%
Took 0.23 sec
[JENKINS] Archiving 

 to 
org.apache.james/james-server-queue-activemq/3.0.0-beta5-SNAPSHOT/james-server-queue-activemq-3.0.0-beta5-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.james/james-server-queue-activemq/3.0.0-beta5-20150430.043015-1025/james-server-queue-activemq-3.0.0-beta5-20150430.043015-1025.jar
[JENKINS] Archiving 

 to 
org.apache.james/james-server-queue-activemq/3.0.0-beta5-20150430.043015-1025/james-server-queue-activemq-3.0.0-beta5-20150430.043015-1025-tests.jar
[JENKINS] Archiving