[jira] [Resolved] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/main/meecrowave/conf/*

2017-06-20 Thread Mark Struberg (JIRA) 

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

Mark Struberg resolved MEECROWAVE-41.
-
Resolution: Fixed

> make meecrowave:bundle pick up content from src/main/meecrowave/conf/*
> --
>
> Key: MEECROWAVE-41
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-41
> Project: Meecrowave
>  Issue Type: New Feature
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently files in src/main/meecrowave/conf etc get ignored during 
> meecrowave:bundle.
> We should just copy over all those files.
> If certain files like log4j2.xml and meecrowave.properties does not exist in 
> the source folder then we generate sensible default ones.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/main/meecrowave/conf/*

2017-06-20 Thread Mark Struberg (JIRA) 

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

Mark Struberg updated MEECROWAVE-41:

Summary: make meecrowave:bundle pick up content from 
src/main/meecrowave/conf/*  (was: make meecrowave:bundle pick up content from 
src/meecrowave/*)

> make meecrowave:bundle pick up content from src/main/meecrowave/conf/*
> --
>
> Key: MEECROWAVE-41
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-41
> Project: Meecrowave
>  Issue Type: New Feature
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently files in src/meecrowave/conf etc get ignored during 
> meecrowave:bundle.
> We should just copy over all those files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MEECROWAVE-42) allow to auto package meecrowave in meecrowave:bundle goal

2017-06-20 Thread Romain Manni-Bucau (JIRA) 

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

Romain Manni-Bucau resolved MEECROWAVE-42.
--
Resolution: Fixed

> allow to auto package meecrowave in meecrowave:bundle goal
> --
>
> Key: MEECROWAVE-42
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-42
> Project: Meecrowave
>  Issue Type: Improvement
>Reporter: Romain Manni-Bucau
>Assignee: Romain Manni-Bucau
> Fix For: 0.3.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/meecrowave/*

2017-06-20 Thread Mark Struberg (JIRA) 
Mark Struberg created MEECROWAVE-41:
---

 Summary: make meecrowave:bundle pick up content from 
src/meecrowave/*
 Key: MEECROWAVE-41
 URL: https://issues.apache.org/jira/browse/MEECROWAVE-41
 Project: Meecrowave
  Issue Type: New Feature
Affects Versions: 0.3.1
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 4.0


Currently files in src/meecrowave/conf etc get ignored during meecrowave:bundle.
We should just copy over all those files.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: OWB-2.0.0 to be released soon

2017-06-20 Thread Romain Manni-Bucau 
Oh yes, Mark changed something about it and the default scanning mode of
CDI doesn't help. Maybe we need to just ignore the classes explicitly


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | JavaEE Factory


2017-06-20 3:23 GMT+02:00 John D. Ament :

> Ok, so I started to add the missing dependencies, that's not going to
> work.  In scheduler I added log4j then it complained about some terracotta
> class.  I think there's a regression in the arquillian adapter,
> specifically how it handles classes that may not be present.
>
> On Mon, Jun 19, 2017 at 8:39 PM John D. Ament 
> wrote:
>
> > I had a hunch it was that, so did a dependency tree - no luck.
> >
> > https://paste.apache.org/X3c5
> >
> > John
> >
> >
> > On Mon, Jun 19, 2017 at 3:22 AM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> >> IncompatibleClassChangeError, classpath is probably corrupted with an
> owb 1.0 dependency somehow
> >>
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau  |  Blog
> >>  | Old Blog
> >>  | Github
> >>  | LinkedIn
> >>  | JavaEE Factory
> >> 
> >>
> >> 2017-06-19 8:19 GMT+02:00 Mark Struberg :
> >>
> >>> Oh txs for the catch, will check.
> >>>
> >>> LieGrue,
> >>> Strub
> >>>
> >>> Am 19.06.2017 um 04:47 schrieb John D. Ament :
> >>>
> >>> Hmm so DeltaSpike is seeing 11 test failures with OWB2.
> >>>
> >>>
> >>> https://builds.apache.org/view/A-D/view/DeltaSpike/job/
> DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/
> >>>
> >>> CDI Ctrl Servlet - it looks like a weird error, the impl of this bean
> >>> hasn't been changed in 2 years.  Not sure if this is a new validation
> in
> >>> place.
> >>>
> >>> ClasspathResourceTest - I'm not sure if the path is getting skewed due
> >>> to duplicate resources, or the same resource being added multiple
> times.
> >>>
> >>> JSF & Scheduler look like changes in the dependency structure.  If on
> >>> purpose, I'll push up a fix sometime tomorrow.
> >>>
> >>> On Sun, Jun 18, 2017 at 10:04 AM Romain Manni-Bucau <
> >>> rmannibu...@gmail.com> wrote:
> >>>
>  2 things to check before the release:
> 
>  1. se API (not covered by tck and poorly covered by us ATM)
>  2. the fastMatching flag should get removed if we can (created due to
> 1
>  tck)
> 
> 
>  Romain Manni-Bucau
>  @rmannibucau  |  Blog
>   | Old Blog
>   | Github
>   | LinkedIn
>   | JavaEE Factory
>  
> 
>  2017-06-18 15:41 GMT+02:00 Mark Struberg :
> 
> > OWB itself did always ignore it and log a warning. This code did not
> > get changed for a while.
> >
> > But we have/had a bug in the arquillian connector which lead to
> > blowing up on NoClassDefFound.
> > I need to check whether we fixed this already with another commit.
> >
> > The ticket is https://issues.apache.org/jira/browse/OWB-1179
> >
> > LieGrue,
> > strub
> >
> >
> >
> > > Am 18.06.2017 um 13:45 schrieb John D. Ament <
> johndam...@apache.org
> > >:
> > >
> > > Just wondering, did you change the behavior when a class isn't
> found
> > to
> > > ignore the bean? Prior versions of OWB would throw an exception.
> > >
> > > John
> > >
> > > On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg <
> > strub...@yahoo.de.invalid>
> > > wrote:
> > >
> > >> Yes, it should 'just work' afaict.
> > >> We even kept the SPI the same.
> > >> We most likely will add an async event related API for better
> > integration
> > >> within TomEE in the future.
> > >> But this should still be perfectly backward compatible as OWB will
> > provide
> > >> a default implementation anyway!
> > >>
> > >> If you catch any (unexpected) problems then just ping us.
> > >>
> > >> txs and LieGrue,
> > >> strub
> > >>
> > >>
> > >>> Am 17.06.2017 um 22:36 schrieb John D. Ament <
> > johndam...@apache.org>:
> > >>>
> > >>> So... just to confirm.  Outside of changing the geronimo specs,
> > taking a
> > >> OWB 1.x profile that I may have will just work with OWB 2?
> > >>>
> > >>> John
> > >>>
> > >>> On Sat, Jun