To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-graph has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jxpath has an issue affecting its community integration.
This issu
There can be quite a few if you have to have them for every class,
interface, annotation, method, field, etc. Then again if you just reuse 1
adapter object all the time it wouldn't be that bad. You would just have to
let users know that they cannot maintain references to those objects after
scanni
On 7 June 2012 21:11, James Carman wrote:
> On Thu, Jun 7, 2012 at 3:56 AM, sebb wrote:
>>
>> Not sure I follow this. Why would an interface use extra memory?
>> I can see that it might add a bit more to the static size of a class,
>> but why would it add more to each instance of a class that use
On Thu, Jun 7, 2012 at 3:56 AM, sebb wrote:
>
> Not sure I follow this. Why would an interface use extra memory?
> I can see that it might add a bit more to the static size of a class,
> but why would it add more to each instance of a class that uses it?
>
It's not the interface itself. It's the
In that environment, does new URL("wsjar:///...") succeed?
On 6/6/12 9:22 PM, "Mark Struberg" wrote:
>Yes, we had this pretty commonly in OWB. You might get funny strings like
>"wsjar:///..." as URL.toExternalForm() :(
>Basically all Systems which do not use the native file system but an own
Hi,
Am 07.06.2012 um 15:45 schrieb Luc Maisonobe:
> Hi,
>
> Le 06/06/2012 18:27, James Carman a écrit :
>> Agreed. I'm in OSGi-land these days (ServiceMix, Camel, ActiveMQ, etc.),
>> so I'm all for it! :)
>>
>>
>> On Wed, Jun 6, 2012 at 12:21 PM, Christian Grobmeier
>> wrote:
>>
>>> No obje
Hi,
Am 07.06.2012 um 15:46 schrieb Jörg Schaible:
> As we see from Felix' patch, we can satisfy OSGi still for the latter reason
> by declaring proper exports. In contrast to the patch I'd select a version
> though that makes it totally clear that it is synthetic e.g. I'd take 1.
> or 1.4.
On Thu, Jun 7, 2012 at 9:45 AM, Luc Maisonobe wrote:
> Hi,
>
> Le 06/06/2012 18:27, James Carman a écrit :
> > Agreed. I'm in OSGi-land these days (ServiceMix, Camel, ActiveMQ, etc.),
> > so I'm all for it! :)
> >
> >
> > On Wed, Jun 6, 2012 at 12:21 PM, Christian Grobmeier <
> grobme...@gmail.c
Hi Gary,
Gary Gregory wrote:
> Opening ...
>
> Should Commons adopt OSGi Semantic Versioning [1] instead of defining our
> own [2] (even though they might in effect be the same)?
>
> Should Commons layer its semantic version details on top of OSGi?
>
> [1] http://www.osgi.org/wiki/uploads/Link
Hi,
Le 06/06/2012 18:27, James Carman a écrit :
> Agreed. I'm in OSGi-land these days (ServiceMix, Camel, ActiveMQ, etc.),
> so I'm all for it! :)
>
>
> On Wed, Jun 6, 2012 at 12:21 PM, Christian Grobmeier
> wrote:
>
>> No objections here.
>> If there is a spec we can follow, we should do it.
Hi,
Ok, then. The issue with patch is IO-333 [1]
Regards
Felix
[1] https://issues.apache.org/jira/browse/IO-333
Am 06.06.2012 um 13:38 schrieb Jochen Wiedmann:
> On Wed, Jun 6, 2012 at 12:40 PM, Felix Meschberger wrote:
>> Would you consider a bug/patch and include it in the release ?
>
>
>
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jmx has an issue affecting its community integration.
T
On 7 June 2012 05:18, Mark Struberg wrote:
>> You mention that interfaces take a bit more space in memory. Is this
>> because there is an adapter class (implementing the interface) and the
>> delegated final implementor? Or are you pointing out some other memory
>> concern?
> It's not much actual
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
17 matches
Mail list logo