- 0,5 on supporting Java5
On Wed, Dec 28, 2011 at 9:40 AM, Mark Struberg strub...@yahoo.de wrote:
Since we have quite a few vetos against Java5 usage for this new project, I'd
say we go with Java6. Java7 is right around the corner, and Java5 is really
only legacy now. If projects still
[
https://issues.apache.org/jira/browse/DELTASPIKE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-28.
Resolution: Later
we have to re-visit this topic, if a majority of the
Hi!
Whenever you spot the following sequence in a class:
//X TODO some comment about the 'why'
then it means that there is some unfinished stuff lying around...
I'd say we now start adding stuff and mark all parts which cause sentiments
with such a comment and clean this mess up in a 2nd
[
https://issues.apache.org/jira/browse/DELTASPIKE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-21.
-
Resolution: Fixed
Fix Version/s: 0.1-SNAPSHOT
Implementation finished
[
https://issues.apache.org/jira/browse/DELTASPIKE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176549#comment-13176549
]
Mark Struberg commented on DELTASPIKE-20:
-
CdiUtils sounds a bit too loose. I'd
-1 for supporting Java5
Let Microsoft deal with the legacy stuff ^^
Regards,
Jakob
2011/12/28 Matthias Wessendorf mat...@apache.org:
- 0,5 on supporting Java5
On Wed, Dec 28, 2011 at 9:40 AM, Mark Struberg strub...@yahoo.de wrote:
Since we have quite a few vetos against Java5 usage for
oki, seems the majority is for dropping Java5 support. I've upgraded the parent
pom to language target level 1.6 already.
Please note that this doesn't mean that we drop JavaEE-5 support! I still like
to support CDI containers running on EE-5 if possible.
LieGrue,
strub
- Original
[
https://issues.apache.org/jira/browse/DELTASPIKE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-20.
-
Resolution: Fixed
Fix Version/s: 0.1-SNAPSHOT
resolved as part of the work for
Actually this is the most common case _why_ one likes to veto a bean. Because
if you create a producer method for a MyBean, then you'll get an
AmbiguousResolutionException otherwise.
The spec conform easy way would be to simply use
@Typed()
public class MyBean {}
to disable the bean. Imo we
On 2011-12-28, at 10:05 AM, Mark Struberg wrote:
Actually this is the most common case _why_ one likes to veto a bean. Because
if you create a producer method for a MyBean, then you'll get an
AmbiguousResolutionException otherwise.
Well, I would say that domain entities may be an even more
[
https://issues.apache.org/jira/browse/DELTASPIKE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-24.
Resolution: Fixed
Deactivatable
-
Key:
[
https://issues.apache.org/jira/browse/DELTASPIKE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176957#comment-13176957
]
Gerhard Petracek commented on DELTASPIKE-36:
[
https://issues.apache.org/jira/browse/DELTASPIKE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176957#comment-13176957
]
Gerhard Petracek edited comment on DELTASPIKE-36 at 12/29/11 2:47 AM:
13 matches
Mail list logo