[
https://issues.apache.org/jira/browse/DELTASPIKE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855131#comment-13855131
]
Thomas Andraschko commented on DELTASPIKE-475:
--
+1 Romain
auto.
[
https://issues.apache.org/jira/browse/DELTASPIKE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855147#comment-13855147
]
Gerhard Petracek edited comment on DELTASPIKE-472 at 12/22/13 10:44 AM:
[
https://issues.apache.org/jira/browse/DELTASPIKE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-477:
Issue Type: Task (was: Bug)
New Scheduler module is not included in binary
[
https://issues.apache.org/jira/browse/DELTASPIKE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855322#comment-13855322
]
John D. Ament commented on DELTASPIKE-478:
--
Thanks, it worked! The only issue
[
https://issues.apache.org/jira/browse/DELTASPIKE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament closed DELTASPIKE-478.
Create build profile in jenkins that creates binary distribution.
Hi all
Recently for the binary distribution task, I added a bom. I added
this because the parent pom includes our dependencies, as well as our
developer list. For someone importing the project to build against, I
figured this was a bad idea (we would show as developers in that
imported pom).
[
https://issues.apache.org/jira/browse/DELTASPIKE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament reassigned DELTASPIKE-477:
Assignee: John D. Ament
New Scheduler module is not included in binary
+-0 while deltaspike doesnt use itself the bom (they lead too often to dep
issues in practise)
Le 23 déc. 2013 02:09, John D. Ament john.d.am...@gmail.com a écrit :
Hi all
Recently for the binary distribution task, I added a bom. I added
this because the parent pom includes our dependencies,