Re: Parent vs BOM
+-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" a écrit : > 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). However, this ended up adding some double entry. > > So I'd like to propose moving this bom up a few directories, and leave > this up as the only place to have the modules listed. Importing this > one into our parent. > > WDYT? > > John >
[jira] [Assigned] (DELTASPIKE-477) New Scheduler module is not included in binary distribution.
[ 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 distribution. > > > Key: DELTASPIKE-477 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-477 > Project: DeltaSpike > Issue Type: Task > Components: Scheduler >Reporter: John D. Ament >Assignee: John D. Ament > Fix For: 0.6 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (DELTASPIKE-477) New Scheduler module is not included in binary distribution.
[ https://issues.apache.org/jira/browse/DELTASPIKE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reopened DELTASPIKE-477: -- Actually it still is not in there. I wanted to hold off on resolving this until we figure out parent vs bom. > New Scheduler module is not included in binary distribution. > > > Key: DELTASPIKE-477 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-477 > Project: DeltaSpike > Issue Type: Task > Components: Scheduler >Reporter: John D. Ament > Fix For: 0.6 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Parent vs BOM
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). However, this ended up adding some double entry. So I'd like to propose moving this bom up a few directories, and leave this up as the only place to have the modules listed. Importing this one into our parent. WDYT? John
[jira] [Closed] (DELTASPIKE-478) Create build profile in jenkins that creates binary distribution.
[ 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. > - > > Key: DELTASPIKE-478 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-478 > Project: DeltaSpike > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: John D. Ament >Assignee: Mark Struberg >Priority: Minor > Fix For: 0.6 > > > Please add a jenkins job to execute with the -Pdistribution profile. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DELTASPIKE-478) Create build profile in jenkins that creates binary distribution.
[ https://issues.apache.org/jira/browse/DELTASPIKE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855322#comment-13855322 ] John D. Ament commented on DELTASPIKE-478: -- Thanks, it worked! The only issue I saw was that browsing only shows tar.gz not zip. The zip is there. I'll start updating getting started docs around this. > Create build profile in jenkins that creates binary distribution. > - > > Key: DELTASPIKE-478 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-478 > Project: DeltaSpike > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: John D. Ament >Assignee: Mark Struberg >Priority: Minor > Fix For: 0.6 > > > Please add a jenkins job to execute with the -Pdistribution profile. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (DELTASPIKE-477) New Scheduler module is not included in binary distribution.
[ https://issues.apache.org/jira/browse/DELTASPIKE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-477. - Resolution: Fixed Fix Version/s: 0.6 > New Scheduler module is not included in binary distribution. > > > Key: DELTASPIKE-477 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-477 > Project: DeltaSpike > Issue Type: Task > Components: Scheduler >Reporter: John D. Ament > Fix For: 0.6 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (DELTASPIKE-477) New Scheduler module is not included in binary distribution.
[ 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 distribution. > > > Key: DELTASPIKE-477 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-477 > Project: DeltaSpike > Issue Type: Task > Components: Scheduler >Reporter: John D. Ament > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (DELTASPIKE-472) Implement portable extensions that install custom beans when not running inside a WAR file.
[ https://issues.apache.org/jira/browse/DELTASPIKE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855147#comment-13855147 ] Gerhard Petracek edited comment on DELTASPIKE-472 at 12/22/13 10:44 AM: @john: no - it is not. we just agreed on adding config-files (optionally) needed by some containers if adding it/them is the only impact. i haven't said that we won't/shouldn't do it. we just need something more concrete + we shouldn't do it manually. was (Author: gpetracek): @john: no - it is not. we just agreed on adding config-files (optionally) needed by some containers if adding it/them is the only impact > Implement portable extensions that install custom beans when not running > inside a WAR file. > --- > > Key: DELTASPIKE-472 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-472 > Project: DeltaSpike > Issue Type: Improvement > Components: Core >Reporter: John D. Ament >Assignee: John D. Ament > Fix For: 0.6 > > > In many cases, when you deploy with CDI you're using a self contained WAR > that has everything in it. However, in certain deployment models you can > reference external classpath entries that could be available to you, but not > scanned based on CDI scanning rules. > To work with these more efficiently, we need to implement some extensions > that do very basic things, mostly installing custom beans at runtime to the > destination applications. > I'll go through the application and identify cases where we need to install a > bean, ignoring things that obviously don't belong, e.g. @Typed classes which > are understood to not be installed. At a minimum we should create extensions > that encompass our primary features, where they don't already exist - for > example, Partial Bean is already an extension and needs no other work, Bean > Validation doesn't need an extension since it can be configured, Servlet > simply needs to be registered. Most of this work seems to be in Core. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DELTASPIKE-472) Implement portable extensions that install custom beans when not running inside a WAR file.
[ https://issues.apache.org/jira/browse/DELTASPIKE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855147#comment-13855147 ] Gerhard Petracek commented on DELTASPIKE-472: - @john: no - it is not. we just agreed on adding config-files (optionally) needed by some containers if adding it/them is the only impact > Implement portable extensions that install custom beans when not running > inside a WAR file. > --- > > Key: DELTASPIKE-472 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-472 > Project: DeltaSpike > Issue Type: Improvement > Components: Core >Reporter: John D. Ament >Assignee: John D. Ament > Fix For: 0.6 > > > In many cases, when you deploy with CDI you're using a self contained WAR > that has everything in it. However, in certain deployment models you can > reference external classpath entries that could be available to you, but not > scanned based on CDI scanning rules. > To work with these more efficiently, we need to implement some extensions > that do very basic things, mostly installing custom beans at runtime to the > destination applications. > I'll go through the application and identify cases where we need to install a > bean, ignoring things that obviously don't belong, e.g. @Typed classes which > are understood to not be installed. At a minimum we should create extensions > that encompass our primary features, where they don't already exist - for > example, Partial Bean is already an extension and needs no other work, Bean > Validation doesn't need an extension since it can be configured, Servlet > simply needs to be registered. Most of this work seems to be in Core. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (DELTASPIKE-475) auto. registration of jobs with cron-expressions
[ https://issues.apache.org/jira/browse/DELTASPIKE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-475. - Resolution: Fixed #1 it's already possible to use other schedulers (a custom integration just needs to provide a custom implementation of Scheduler (QuartzScheduler is Deactivatable see DELTASPIKE-474) + a config-value for "deltaspike.scheduler.job-class" -> users don't even need to provide a special config - just a custom module which provides the config + handles deactivation of the defaults correctly) #2 as mentioned by romain, we can create own modules as soon as we support more than quartz > auto. registration of jobs with cron-expressions > > > Key: DELTASPIKE-475 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-475 > Project: DeltaSpike > Issue Type: New Feature > Components: Scheduler >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 0.6 > > > includes: > - support of any scheduler which allows to register jobs based on > cron-expressions > - default integration with quartz -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DELTASPIKE-478) Create build profile in jenkins that creates binary distribution.
[ https://issues.apache.org/jira/browse/DELTASPIKE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855139#comment-13855139 ] Mark Struberg commented on DELTASPIKE-478: -- Txs John, I now added the profile to our 'DeltaSpike Deploy' build job at builds.apache.org. I also started a fresh build now. Can you please check for the expected results on http://repository.apache.org/ ? > Create build profile in jenkins that creates binary distribution. > - > > Key: DELTASPIKE-478 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-478 > Project: DeltaSpike > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: John D. Ament >Assignee: Mark Struberg >Priority: Minor > Fix For: 0.6 > > > Please add a jenkins job to execute with the -Pdistribution profile. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (DELTASPIKE-478) Create build profile in jenkins that creates binary distribution.
[ https://issues.apache.org/jira/browse/DELTASPIKE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-478. -- Resolution: Fixed Fix Version/s: 0.6 > Create build profile in jenkins that creates binary distribution. > - > > Key: DELTASPIKE-478 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-478 > Project: DeltaSpike > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: John D. Ament >Assignee: Mark Struberg >Priority: Minor > Fix For: 0.6 > > > Please add a jenkins job to execute with the -Pdistribution profile. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (DELTASPIKE-475) auto. registration of jobs with cron-expressions
[ https://issues.apache.org/jira/browse/DELTASPIKE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855131#comment-13855131 ] Thomas Andraschko commented on DELTASPIKE-475: -- +1 Romain > auto. registration of jobs with cron-expressions > > > Key: DELTASPIKE-475 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-475 > Project: DeltaSpike > Issue Type: New Feature > Components: Scheduler >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 0.6 > > > includes: > - support of any scheduler which allows to register jobs based on > cron-expressions > - default integration with quartz -- This message was sent by Atlassian JIRA (v6.1.5#6160)
