i agree with mark.
regards,
gerhard
2011/12/21 Mark Struberg strub...@yahoo.de
As I see it we have 3 different options:
1.) .api.* + .impl.* because it's more easy to 'grab' any api package in
e.g. an Arquillian test. If we don't have the modulename.api package name,
then we cannot do
BeanManagerProvider
---
Key: DELTASPIKE-17
URL: https://issues.apache.org/jira/browse/DELTASPIKE-17
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Reporter: Gerhard Petracek
[
https://issues.apache.org/jira/browse/DELTASPIKE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-18:
---
Description:
we need tests for:
- after a container is bootstrapped,
[
https://issues.apache.org/jira/browse/DELTASPIKE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-18:
--
Assignee: Mark Struberg (was: Gerhard Petracek)
unit and integration
[
https://issues.apache.org/jira/browse/DELTASPIKE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-19:
--
Assignee: Mark Struberg (was: Gerhard Petracek)
documentation for
[
https://issues.apache.org/jira/browse/DELTASPIKE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-20:
--
Assignee: Mark Struberg (was: Gerhard Petracek)
move util methods to
[
https://issues.apache.org/jira/browse/DELTASPIKE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-4.
---
Resolution: Fixed
we agreed on adding it - see http://s.apache.org/is
ProjectStage
Key: DELTASPIKE-21
URL: https://issues.apache.org/jira/browse/DELTASPIKE-21
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Reporter: Gerhard Petracek
Assignee: Mark
[
https://issues.apache.org/jira/browse/DELTASPIKE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-21:
---
Description: original feature:
https://issues.apache.org/jira/browse/EXTCDI-9
documentation for ProjectStage
--
Key: DELTASPIKE-23
URL: https://issues.apache.org/jira/browse/DELTASPIKE-23
Project: DeltaSpike
Issue Type: Sub-task
Reporter: Gerhard Petracek
Assignee:
hi @ all,
it looks like we have an agreement. i'm going to create the corresponding
jira issues.
(imo: since we haven't seen objections btw. a discussion about it and it
isn't a formal vote, we can start right now.)
regards,
gerhard
2011/12/20 Marius Bogoevici marius.bogoev...@gmail.com
+1
On Wed, Dec 21, 2011 at 12:00 PM, Mark Struberg strub...@yahoo.de wrote:
As I see it we have 3 different options:
1.) .api.* + .impl.* because it's more easy to 'grab' any api package in
e.g. an Arquillian test. If we don't have the modulename.api package name,
then we cannot do something
[
https://issues.apache.org/jira/browse/DELTASPIKE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-23:
---
Component/s: (was: Core)
Documentation
documentation
[
https://issues.apache.org/jira/browse/DELTASPIKE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-19:
---
Component/s: (was: Core)
Documentation
documentation
[
https://issues.apache.org/jira/browse/DELTASPIKE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-3:
--
Fix Version/s: 1.0.0-incubating
review and discuss BeanManagerProvider
[
https://issues.apache.org/jira/browse/DELTASPIKE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reopened DELTASPIKE-24:
Deactivatable
-
Key: DELTASPIKE-24
[
https://issues.apache.org/jira/browse/DELTASPIKE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-10:
--
Assignee: Jason Porter (was: Gerhard Petracek)
review and discuss
[
https://issues.apache.org/jira/browse/DELTASPIKE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-10:
---
Description:
BeanBuilder - DELTASPIKE-16
NarrowingBeanBuilder - DELTASPIKE-16
[
https://issues.apache.org/jira/browse/DELTASPIKE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-9:
-
Assignee: Jason Porter (was: Gerhard Petracek)
review and discuss
review and discuss CodiConfig
-
Key: DELTASPIKE-27
URL: https://issues.apache.org/jira/browse/DELTASPIKE-27
Project: DeltaSpike
Issue Type: Sub-task
Reporter: Gerhard Petracek
Assignee:
review and discuss ServiceProvider
--
Key: DELTASPIKE-28
URL: https://issues.apache.org/jira/browse/DELTASPIKE-28
Project: DeltaSpike
Issue Type: Sub-task
Reporter: Gerhard Petracek
review and discuss StartupEventBroadcaster
--
Key: DELTASPIKE-31
URL: https://issues.apache.org/jira/browse/DELTASPIKE-31
Project: DeltaSpike
Issue Type: Sub-task
Reporter: Gerhard
+1 rebase
On Tue, Dec 20, 2011 at 6:48 PM, Mark Struberg strub...@yahoo.de wrote:
It was only about
git pull --rebase
Which means that _your_ _own_ commits done in the meantime (and not pushed
upwards) will get rebased to the tip of HEAD.
If you don't do this, you will always get this
hi @ all,
fyi: please check [1] before you answer.
[2] is the implementation used in owb. i suggest to start with it (instead
of the version of codi), because the version of codi provides additional
mechanisms we might need later on (if we include the corresponding
features).
the basic concept:
+1
regards,
gerhard
2011/12/21 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
fyi: please check [1] before you answer.
[2] shows how to provide custom config-values in a type-safe manner.
the basic concept:
CodiConfig itself is just a marker interface to find all config classes
+1
regards,
gerhard
2011/12/21 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
fyi: please check [1] before you answer.
[2] is the implementation used in owb. i suggest to start with it (instead
of the version of codi), because the version of codi provides additional
mechanisms
hi @ all,
fyi: please check [1] before you answer.
the basic concept:
in myfaces codi all names for named beans (@Named of cdi) are placed as
variables in an interface (one per module). to find such interfaces easily
they implement a marker interface called BeanNames (see e.g. [2])
please send
+1
regards,
gerhard
2011/12/21 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
fyi: please check [1] before you answer.
the basic concept:
in myfaces codi all names for named beans (@Named of cdi) are placed as
variables in an interface (one per module). to find such interfaces
hi @ all,
fyi: please check [1] before you answer.
the basic concept:
during the startup of an application myfaces codi writes information about
the current environment to the log.
(e.g. the values configured via [2] and the detected version and
implementation of cdi and other modules do the
+1
regards,
gerhard
2011/12/21 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
fyi: please check [1] before you answer.
the basic concept:
during the startup of an application myfaces codi writes information about
the current environment to the log.
(e.g. the values configured
+1
Please note that CodiConfig doesn't contain any logic! It's really just a
marker interface to mark our SPI classes which are to be
implemented/overwritten in a customer project to configure the provided
functionality.
LieGrue,
strub
- Original Message -
From: Gerhard Petracek
+0.8 nice to have, but we should broaden this to a general logging discussion
imo.
LieGrue,
strub
- Original Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Wednesday, December 21, 2011 10:07 PM
Subject: [DISCUSS]
combined with std. ide features it can be useful. it's a bit nicer than
just searching for all usages of @Named, if you are interested only in the
bean-names of codi (btw. if we add it of deltaspike)
but it's a low priority topic (without a big impact). i just picked it
right now because it's an
33 matches
Mail list logo
