Re: [VOTE] Release Apache DeltaSpike 1.9.0

2018-09-09 Thread John D. Ament
Just looked, for DS-900 a file was added MockUserTransactionResolver.java which does not have a proper header. Probably not a big deal, but should we fix before this release gets cut? John On Fri, Sep 7, 2018 at 8:04 AM Mark Struberg wrote: > Good afternoon! > > I'd like to call a VOTE on

Re: Build failed in Jenkins: DeltaSpike Deploy #2478

2018-09-09 Thread John D. Ament
Hi Mark Could you add a valid license header to MockUserTransactionResolver.java or replace it if it's not Apache licensed? John On Sat, Sep 8, 2018 at 9:54 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: CI for Weld2 error

2018-06-07 Thread John D. Ament
What versions of weld 2 have you tried? On Thu, Jun 7, 2018, 5:11 PM Mark Struberg wrote: > Hi! > > I've tried to fix the CI for Weld2, but it seems that there is nothing > wrong with DeltaSpike but a bug in Weld2 regarding alternatives in > beans.xml if they get disabled via

[jira] [Resolved] (DELTASPIKE-1326) Clean up Java 8 support in data module

2018-03-08 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1326. --- Resolution: Fixed > Clean up Java 8 support in data mod

[jira] [Created] (DELTASPIKE-1328) Add a Java 8 base repository

2018-03-08 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1328: - Summary: Add a Java 8 base repository Key: DELTASPIKE-1328 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1328 Project: DeltaSpike Issue

[jira] [Commented] (DELTASPIKE-1177) [Deltaspike Data] Regoznize Entity Type by method returned type if @Repository.forEntity is set to default

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389866#comment-16389866 ] John D. Ament commented on DELTASPIKE-1177: --- Hi [~tibor17] basically, the issue

[jira] [Updated] (DELTASPIKE-1177) [Deltaspike Data] Regoznize Entity Type by method returned type if @Repository.forEntity is set to default

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1177: -- Fix Version/s: (was: 1.9.0) > [Deltaspike Data] Regoznize Entity T

[jira] [Updated] (DELTASPIKE-1177) [Deltaspike Data] Regoznize Entity Type by method returned type if @Repository.forEntity is set to default

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1177: -- Fix Version/s: 1.9.0 > [Deltaspike Data] Regoznize Entity Type by method retur

[jira] [Created] (DELTASPIKE-1326) Clean up Java 8 support in data module

2018-03-07 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1326: - Summary: Clean up Java 8 support in data module Key: DELTASPIKE-1326 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1326 Project: DeltaSpike

[jira] [Updated] (DELTASPIKE-1324) @Transactional annotation at method level doesn't override the one at class level any more

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1324: -- Fix Version/s: 1.9.0 > @Transactional annotation at method level doesn't overr

[jira] [Commented] (DELTASPIKE-1324) @Transactional annotation at method level doesn't override the one at class level any more

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389852#comment-16389852 ] John D. Ament commented on DELTASPIKE-1324: --- BTW is 1.9.0 an OK place to fix for you

[jira] [Assigned] (DELTASPIKE-1324) @Transactional annotation at method level doesn't override the one at class level any more

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1324: - Assignee: John D. Ament > @Transactional annotation at method level does

[jira] [Commented] (DELTASPIKE-1324) @Transactional annotation at method level doesn't override the one at class level any more

2018-03-07 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389851#comment-16389851 ] John D. Ament commented on DELTASPIKE-1324: --- Good catch, will fix.  Sorry about

Re: [DISCUSS] require Java8 and move to Deltaspike-1.9.x version?

2018-03-01 Thread John D. Ament
in 1.x is fine for me, we can try to improve our APIs with Java8 > In 2.x we can even improve further and cleanup then > > > 2018-03-01 15:55 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > > > 2018-03-01 15:50 GMT+01:00 John D. Ament <johndam...@apache.org>: &g

Re: [DISCUSS] require Java8 and move to Deltaspike-1.9.x version?

2018-03-01 Thread John D. Ament
IMHO to move to Java 8 we need to drop support for EE6/EE7. So to me that says the next version is 2.0 not 1.9.x. There are some weld 1.1 versions that support this, but no testable AS7 instance that we can check against. John On Thu, Mar 1, 2018 at 9:35 AM Cody Lerum

[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config

2018-02-13 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362184#comment-16362184 ] John D. Ament commented on DELTASPIKE-1316: --- Since this is an external code import, don't

Wrong license on proxy-module impl-asm

2018-01-13 Thread John D. Ament
The license for proxy-module's impl-asm binary JAR is generated incorrectly. Do we need to include a shaded ASM? If we do, we need to include the BSD-3-Clause license in the generated JAR. John

Re: Build failed in Jenkins: DeltaSpike Deploy » Apache DeltaSpike Proxy-Module #2173

2018-01-11 Thread John D. Ament
/target/) > > 2018-01-11 15:23 GMT+01:00 John D. Ament <johndam...@apache.org>: > > > Anyone looking at the build failures? > > > > On Thu, Jan 11, 2018 at 8:51 AM Apache Jenkins Server < > > jenk...@builds.apache.org> wrote: > > &g

Re: Build failed in Jenkins: DeltaSpike Deploy » Apache DeltaSpike Proxy-Module #2173

2018-01-11 Thread John D. Ament
Anyone looking at the build failures? On Thu, Jan 11, 2018 at 8:51 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/DeltaSpike%20Deploy/org.apache.deltaspike.modules$proxy-module-project/2173/display/redirect > > > >

Re: provide a default Scheduler which is not using quartz as default?

2018-01-05 Thread John D. Ament
On Fri, Jan 5, 2018 at 2:00 PM John D. Ament <johndam...@apache.org> wrote: > On Fri, Jan 5, 2018 at 1:21 PM Mark Struberg <strub...@yahoo.de.invalid> > wrote: > >> > Shouldnąt we just disable the update check in our quartz configuration? >> >> Well

Re: provide a default Scheduler which is not using quartz as default?

2018-01-05 Thread John D. Ament
On Fri, Jan 5, 2018 at 1:21 PM Mark Struberg wrote: > > Shouldnąt we just disable the update check in our quartz configuration? > > Well there is a flag to disable this behaviour, but a.) it's hard to set > (requires -D) and it doesn't disable 100%. > The code still

Re: provide a default Scheduler which is not using quartz as default?

2018-01-05 Thread John D. Ament
-0 There's already so many solutions around scheduling. It makes sense to disable it out of the box using configuration, as well as documenting it for users. I'm not sure how well maintained quartz is. John On Fri, Jan 5, 2018 at 11:39 AM Mark Struberg wrote: > Hi

[jira] [Commented] (DELTASPIKE-1311) Allow Excluded Repositories

2018-01-05 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313288#comment-16313288 ] John D. Ament commented on DELTASPIKE-1311: --- [~gpetracek] thanks for the reminder. We

[jira] [Commented] (DELTASPIKE-1311) Allow Excluded Repositories

2018-01-05 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313252#comment-16313252 ] John D. Ament commented on DELTASPIKE-1311: --- [~romain.manni-bucau] no this is a common use

[jira] [Commented] (DELTASPIKE-1311) Allow Excluded Repositories

2018-01-05 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313181#comment-16313181 ] John D. Ament commented on DELTASPIKE-1311: --- It probably works well as a minimal slice. We

[jira] [Created] (DELTASPIKE-1311) Allow Excluded Repositories

2018-01-05 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1311: - Summary: Allow Excluded Repositories Key: DELTASPIKE-1311 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1311 Project: DeltaSpike Issue

[jira] [Commented] (DELTASPIKE-1299) Order by items are applied in alphabetic order

2017-12-30 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306996#comment-16306996 ] John D. Ament commented on DELTASPIKE-1299: --- [~tandraschko] I don't know what this ticket

Re: [VOTE] release Apache DeltaSpike-1.8.1

2017-12-30 Thread John D. Ament
I didn't see an answer on this, but I'm fine with releasing as is considering the contents so here's my +1. On Sat, Dec 30, 2017 at 11:59 AM John D. Ament <johndam...@apache.org> wrote: > Where did it break jenkins? > > > https://builds.apache.org/view/A-D/view/DeltaSpike/jo

Re: [VOTE] release Apache DeltaSpike-1.8.1

2017-12-30 Thread John D. Ament
ed. > But we should really get this release out of the door asap as it contains > important security fixes. > > Happy to run an 1.8.2 release in the next weeks. > > LieGrue, > strub > > > Am 30.12.2017 um 17:43 schrieb John D. Ament <johndam...@apache.org>: &g

Re: [VOTE] release Apache DeltaSpike-1.8.1

2017-12-30 Thread John D. Ament
Hmmm looks like we crossed wires. Can you rerun with current master? I want to ensure that 1299 is included. On Sat, Dec 30, 2017 at 11:39 AM Mark Struberg wrote: > Hi folks! > > I did run the necessary steps for releasing DeltaSpike-1.8.1 > > The following bugs and

[jira] [Resolved] (DELTASPIKE-1299) Order by items are applied in alphabetic order

2017-12-30 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1299. --- Resolution: Fixed Thanks for the patch, applied! > Order by items are appl

[jira] [Updated] (DELTASPIKE-1299) Order by items are applied in alphabetic order

2017-12-30 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1299: -- Fix Version/s: 1.8.1 > Order by items are applied in alphabetic or

[jira] [Reopened] (DELTASPIKE-1262) Remove CdiContainer control

2017-12-30 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reopened DELTASPIKE-1262: --- [~struberg] This is for a planned 2.0 (who knows when it will happen). You can

[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-12-30 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306857#comment-16306857 ] John D. Ament commented on DELTASPIKE-940: -- Yep, simply forgot to upate JIRA

Re: CI for DeltaSpike?

2017-12-01 Thread John D. Ament
I'm not sure if its the cause or not, but I see this when running the failing tests on wildfly 10.1 10:31:46,124 WARN [org.jboss.modules] (Weld Thread Pool -- 6) Failed to define class org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator$1 in Module

Re: CI for DeltaSpike?

2017-12-01 Thread John D. Ament
The main issues are that we're all independent contributors to DS, all with the same level of rights to write to the repo. We typically don't do PRs. We actually do have a PR job in Jenkins for those external parties that do raise PRs ->

[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-12-01 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274449#comment-16274449 ] John D. Ament commented on DELTASPIKE-940: -- got it. The issue looks pretty straight forward

Re: Build failed in Jenkins: DeltaSpike Deploy #2115

2017-11-30 Thread John D. Ament
Looks like this was the one job where that profile was still working right, I tweaked the job config and restarted it :-( If there are any other java 8 jobs that are broken now, just add -Pjava8.tests to the maven config. John On Thu, Nov 30, 2017 at 10:15 AM Apache Jenkins Server <

[jira] [Commented] (DELTASPIKE-1302) ThreadPoolManager: ExecutorService map is always empty

2017-11-25 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265792#comment-16265792 ] John D. Ament commented on DELTASPIKE-1302: --- I like Romain's idea. Makes sense

[jira] [Commented] (DELTASPIKE-1301) java.lang.IllegalStateException,message=Could not find EntityManager with default qualifier.

2017-11-17 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257226#comment-16257226 ] John D. Ament commented on DELTASPIKE-1301: --- You mentioned this in a prior comment: {code

[jira] [Commented] (DELTASPIKE-1301) java.lang.IllegalStateException,message=Could not find EntityManager with default qualifier.

2017-11-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255639#comment-16255639 ] John D. Ament commented on DELTASPIKE-1301: --- Just wondering, did you try adding

[jira] [Updated] (DELTASPIKE-1301) java.lang.IllegalStateException,message=Could not find EntityManager with default qualifier.

2017-11-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1301: -- Description: Hello, I have the following data-module repository: {code

Re: Build failed in Jenkins: DeltaSpike RAT-Check #2806

2017-10-31 Thread John D. Ament
Can you fix this Gerhard? On Tue, Oct 31, 2017 at 2:40 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/DeltaSpike%20RAT-Check/2806/display/redirect?page=changes > > > > Changes: > > [gpetracek] DELTASPIKE-1297 added test with a customized

Re: CDI extension: error with specialization beans

2017-09-24 Thread John D. Ament
The error you're getting is more to do with EJB than it does with CDI. JBoss AS 7 is very old. I doubt specializing an EJB would have ever worked (I'm not even sure it works today, specializing is more to do with how CDI works). Does it need to be an EJB? On Sun, Sep 24, 2017 at 4:59 PM Antonio

[jira] [Resolved] (DELTASPIKE-1292) deltaspike distribution BOM has wrong parent - rendering it useless

2017-09-13 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1292. --- Resolution: Duplicate Marking as a duplicate. > deltaspike distribution BOM

[jira] [Resolved] (DELTASPIKE-1278) PropertyFileConfig does not respect optional on external resources

2017-08-12 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1278. --- Resolution: Fixed Assignee: John D. Ament Fix Version/s: 1.8.1

[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-08-12 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124726#comment-16124726 ] John D. Ament commented on DELTASPIKE-940: -- [~tandraschko] sorry thought I had already

[jira] [Resolved] (DELTASPIKE-1281) Deltaspike does not pass BeanManager to persistenf factory config using "javax.persistence.bean.manager"

2017-08-12 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1281. --- Resolution: Fixed Done. > Deltaspike does not pass BeanManager to persist

[jira] [Assigned] (DELTASPIKE-1281) Deltaspike does not pass BeanManager to persistenf factory config using "javax.persistence.bean.manager"

2017-07-18 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1281: - Assignee: John D. Ament > Deltaspike does not pass BeanMana

[jira] [Updated] (DELTASPIKE-1281) Deltaspike does not pass BeanManager to persistenf factory config using "javax.persistence.bean.manager"

2017-07-18 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1281: -- Fix Version/s: 1.8.1 > Deltaspike does not pass BeanManager to persistenf fact

[jira] [Commented] (DELTASPIKE-1275) Build fails on Linux because Testclass filenames are to long

2017-06-26 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063499#comment-16063499 ] John D. Ament commented on DELTASPIKE-1275: --- what distro? > Build fails on Linux beca

[jira] [Resolved] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-06-24 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1252. --- Resolution: Fixed > data-documentation missing Optional return va

[jira] [Created] (DELTASPIKE-1273) Test against OWB 2

2017-06-18 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1273: - Summary: Test against OWB 2 Key: DELTASPIKE-1273 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1273 Project: DeltaSpike Issue Type: Test

Testing Against OWB 2

2017-06-18 Thread John D. Ament
I'm planning to push up a new profile based on OWB 2, in the state of what we used for OWB 1/1.5. There's some test failures, I haven't looked at yet, but wanted to get it running through Jenkins to make sure it's not my machine. John

[jira] [Created] (DELTASPIKE-1264) Remove portions of BeanProvider/BeanManagerProvider

2017-06-03 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1264: - Summary: Remove portions of BeanProvider/BeanManagerProvider Key: DELTASPIKE-1264 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1264 Project

[jira] [Created] (DELTASPIKE-1263) Remove BeanBuilder

2017-06-03 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1263: - Summary: Remove BeanBuilder Key: DELTASPIKE-1263 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1263 Project: DeltaSpike Issue Type

[jira] [Created] (DELTASPIKE-1260) Remove Servlet Module

2017-06-03 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1260: - Summary: Remove Servlet Module Key: DELTASPIKE-1260 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1260 Project: DeltaSpike Issue Type

[jira] [Created] (DELTASPIKE-1261) Remove BeanVal Module

2017-06-03 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1261: - Summary: Remove BeanVal Module Key: DELTASPIKE-1261 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1261 Project: DeltaSpike Issue Type

Re: Creating a branch for DeltaSpike 2.0? Or 1.x maintenance?

2017-06-03 Thread John D. Ament
00 Gerhard Petracek <gpetra...@apache.org>: > > > > > > > @romain: +1 > > > > > > > > regards, > > > > gerhard > > > > > > > > > > > > > > > > 2017-06-03 16:19 GMT+02:00 Romain Manni-Buca

Re: [VOTE] [CANCEL] Release Apache DeltaSpike-1.8.0

2017-06-03 Thread John D. Ament
t; > >> > > I'd recommend just running a mvn deploy -Pdistribution from the > 1.8.0 > >> > tag, > >> > > that should resolve this. > >> > > >> > Sadly not. Since the dist modules only get added conditionally they > >> didn't >

Creating a branch for DeltaSpike 2.0? Or 1.x maintenance?

2017-06-03 Thread John D. Ament
Hey guys I'm not sure there's much more for us to do in 1.x as far as feature goes, but I could be wrong. I do think we should start to ramp up work DeltaSpike 2.0: - Baseline on CDI 2.0, Java EE 8, Java 8 - Remove older components that are not needed any more - See if there's new features we

Re: [1/2] deltaspike git commit: further release fixes

2017-05-28 Thread John D. Ament
don't know... > In any case, if a pom is part of the reactor, then it should also > reference back to the build chain somehow. > > LieGrue, > strub > > > > Am 28.05.2017 um 17:24 schrieb John D. Ament <johndam...@apache.org>: > > > > I think that was the goal

Re: [VOTE] Apache DeltaSpike 1.8.0 - 2nd take

2017-05-28 Thread John D. Ament
+1 On Sun, May 28, 2017 at 6:42 AM Mark Struberg wrote: > Hi! > > I just rerolled the release. > release branch and tag again staged at my github account > https://github.com/struberg/deltaspike/tree/release_deltaspike_1.8.0 > > Staging repo is > >

[jira] [Created] (DELTASPIKE-1257) Research why BOM isn't working right in a release

2017-05-28 Thread John D. Ament (JIRA)
John D. Ament created DELTASPIKE-1257: - Summary: Research why BOM isn't working right in a release Key: DELTASPIKE-1257 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1257 Project

[jira] [Updated] (DELTASPIKE-1257) Research why BOM isn't working right in a release

2017-05-28 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1257: -- Fix Version/s: 1.8.1 > Research why BOM isn't working right in a rele

[jira] [Updated] (DELTASPIKE-1257) Research why BOM isn't working right in a release

2017-05-28 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1257: -- Affects Version/s: 1.8.0 > Research why BOM isn't working right in a rele

Re: [1/2] deltaspike git commit: further release fixes

2017-05-28 Thread John D. Ament
so the boms are really error prone. They ONLY work in the exact pom you > > declare them in. > > So if you import the bom in your parent project and then reference the > > various deltaspike modules only in some specific parts of your build then > > it doesn't work anyway

Re: [1/2] deltaspike git commit: further release fixes

2017-05-28 Thread John D. Ament
Mark, On Sun, May 28, 2017 at 6:37 AM wrote: > Repository: deltaspike > Updated Branches: > refs/heads/master 6721ca6ec -> a62a93fca > > > further release fixes > > > Project: http://git-wip-us.apache.org/repos/asf/deltaspike/repo > Commit:

Re: [2/2] deltaspike git commit: clean up superfluous stuff in our poms

2017-05-28 Thread John D. Ament
This is actually pretty import to keep, all of the dependencies in the dist pom. Without these with the explicit scope of compile, the remaining targets won't work correctly. On Sun, May 28, 2017 at 6:37 AM wrote: > clean up superfluous stuff in our poms > > yet another

Re: [VOTE] Release Apache DeltaSpike-1.8.0

2017-05-27 Thread John D. Ament
l of the artifacts. I'd recommend just running a mvn deploy -Pdistribution from the 1.8.0 tag, that should resolve this. > I can put them to dist/dev. > Which of the artifacts do you need? > bom, full distribution. > > LieGrue, > strub > > > Am 27.05.2017 um 17:15

Re: [VOTE] Release Apache DeltaSpike-1.8.0

2017-05-27 Thread John D. Ament
27, 2017 at 11:10 AM John D. Ament <john.d.am...@gmail.com> wrote: > Did you run with -Pdistribution -DreleaseProfiles=distribution as > mentioned on [1]? > > [1]: http://deltaspike.apache.org/steps_for_a_release.html > > On Sat, May 27, 2017 at 11:06 AM Mark Struberg &l

Re: [VOTE] Release Apache DeltaSpike-1.8.0

2017-05-27 Thread John D. Ament
o if the bom was not produced via the maven build then it is not here - > and most probably never has been. > > Note that an ASF release is ONLY about the sources and not about any > binary. > Binaries are just served for convenience. > > LieGrue, > strub > > > > Am 27

Re: jbossas 7.1.1.Final build

2017-05-21 Thread John D. Ament
Mark, Is it the same issue as [1]? John [1]: https://lists.apache.org/thread.html/d01555301db719485d5ced44b15f4e875af3472a8693e78193410308@%3Cdev.deltaspike.apache.org%3E On Sun, May 21, 2017 at 11:49 AM Mark Struberg wrote: > Hi folks! > > Could someone from JBoss

[jira] [Assigned] (DELTASPIKE-1212) Introduce a ConfigResolver.resolveAllProperties method

2017-05-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1212: - Assignee: John D. Ament > Introduce a ConfigResolver.resolveAllPropert

[jira] [Commented] (DELTASPIKE-1212) Introduce a ConfigResolver.resolveAllProperties method

2017-05-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013120#comment-16013120 ] John D. Ament commented on DELTASPIKE-1212: --- I disagree with closing hard to implement

[jira] [Updated] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-940: - Fix Version/s: (was: 2.0) 1.8.0 > @Transactio

[jira] [Updated] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-16 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-940: - Attachment: ds940.patch This is basically what I had in mind for the first pass

Re: [DISCUSS] release 1.8.0 next week?

2017-05-09 Thread John D. Ament
IMHO, we should resolve [1] first, and then figure out if when we want to cut 1.8.0. [1]: https://lists.apache.org/thread.html/dd64597c0e79c7b2dfc2c5bdea09d7d12efc1979b41dc494b1ee8da4@%3Cdev.deltaspike.apache.org%3E On Tue, May 9, 2017 at 8:18 AM Mark Struberg wrote:

[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002558#comment-16002558 ] John D. Ament commented on DELTASPIKE-940: -- While we shouldn't remove the old behavior pre-DS

[jira] [Updated] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-940: - Fix Version/s: 1.8.0 > @Transactional and @EntityManagerConfig each use a differ

[jira] [Closed] (DELTASPIKE-1053) Support JPA 2.1 StoredProcedureQueries

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed DELTASPIKE-1053. - Resolution: Duplicate > Support JPA 2.1 StoredProcedureQuer

[jira] [Assigned] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-940: Assignee: John D. Ament (was: Thomas Hug) > @Transactio

[jira] [Updated] (DELTASPIKE-1115) Entity meta data discovery works not the same as in JPA

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1115: -- Component/s: (was: Data-Module) > Entity meta data discovery wo

[jira] [Assigned] (DELTASPIKE-1193) Repository methods should consider Boolean and boolean the same

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1193: - Assignee: John D. Ament > Repository methods should consider Bool

[jira] [Assigned] (DELTASPIKE-1225) deltaspike.testcontrol.stop_container should stop the container after all tests executed

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1225: - Assignee: John D. Ament > deltaspike.testcontrol.stop_container should s

[jira] [Assigned] (DELTASPIKE-1229) Allow the use of @Alternative to implement a custom TimestampsProvider

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1229: - Assignee: John D. Ament > Allow the use of @Alternative to implem

[jira] [Closed] (DELTASPIKE-1236) unit testing a servlet that uses injection

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed DELTASPIKE-1236. - Resolution: Won't Fix > unit testing a servlet that uses inject

[jira] [Commented] (DELTASPIKE-1240) [Config] add List support

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002541#comment-16002541 ] John D. Ament commented on DELTASPIKE-1240: --- FYI, while there's documentation committed

[jira] [Resolved] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1252. --- Resolution: Fixed > data-documentation missing Optional return va

[jira] [Commented] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002531#comment-16002531 ] John D. Ament commented on DELTASPIKE-1252: --- Fair point... stream is missing there as well

[jira] [Updated] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1252: -- Fix Version/s: 1.8.0 > data-documentation missing Optional return va

[jira] [Assigned] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reassigned DELTASPIKE-1252: - Assignee: John D. Ament > data-documentation missing Optional return va

Re: [DISCUSS] updating prerequisite to Java 1.7 for DeltaSpike-1.8.x and higher?

2017-05-08 Thread John D. Ament
What feature is that? On May 8, 2017 2:51 PM, "Mark Struberg" wrote: Paths and other nio features for accessing file attributes. Those are only available in Java7, and I need those now for a new DeltaSpike feature... Java6 is EOL since 2013 anyway. I don't even have

Re: [DISCUSS] streamline our support

2017-04-02 Thread John D. Ament
Some notes in line: On Sun, Apr 2, 2017 at 3:55 PM Mark Struberg wrote: > Hi folks! > > I would like to start a discussion about which Containers we like to > support in 1.8.0 and later. > We still have CI builds for ancient servers which are known to be buggy > and

Re: JBossAS 7 build stuck

2017-04-02 Thread John D. Ament
Are you running Java 8 as your JVM? John On Sun, Apr 2, 2017 at 8:24 AM Mark Struberg wrote: > hi folks! > > mvn clean install -Pjbossas-build-managed-7 | tee mvn-jbossas_7.log > > This gets stuck whenever I run it. Used to work in the (maybe distant) > past. > Any

[jira] [Updated] (DELTASPIKE-1238) Create a better default TransactionStrategy

2017-03-31 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1238: -- Description: Create a better default TransactionStrategy that handles more use

[jira] [Updated] (DELTASPIKE-1238) Create a better default TransactionStrategy

2017-03-31 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1238: -- Summary: Create a better default TransactionStrategy (was: Make

[jira] [Reopened] (DELTASPIKE-1238) Make EnvironmentAwareTransactionStrategy the default

2017-03-31 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reopened DELTASPIKE-1238: --- Hey, I disagree. We can talk through it more, but it isn't a top priority for me

[jira] [Resolved] (DELTASPIKE-1195) Servlet module forces application to use distributed sessions

2017-03-31 Thread John D. Ament (JIRA)
[ https://issues.apache.org/jira/browse/DELTASPIKE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1195. --- Resolution: Won't Fix Wasn't me, but the user mentioned that issue is not ours

Re: Deltaspike data-ear

2017-03-28 Thread John D. Ament
You can. But please note that the scope of each bean is tied to its deployment archive. A WAR is better and a bit easier, much more highly recommended. What container do you deploy to? If you face any issues, please don't hesitate to reach out. John On Tue, Mar 28, 2017 at 1:59 PM pedro

  1   2   3   4   5   6   7   8   9   >