[imaging] - Release Date and Production Suitability?

[Mickley, Joshua R (Genworth)]

Greetings All,

I am evaluating the use of Commons Imaging for a project involving image 
conversion and manipulation.

My question is around a timeline for an official release of Commons Imaging and 
suitability for use in a Production environment.

I am currently using the SNAPSHOT version and am curious what bits of 
functionality are needed prior to releasing the code.  The unit testing I have 
achieved to date gives me a good impression but I wanted to inquire and gain 
some additional insight.

Let me know if there are any specific areas where I can help contribute.

Thanks!
  -Josh

RE: [imaging] - Release Date and Production Suitability?

[Gary Gregory]

We certainly can use the help.  Maybe Damjan can she'd some light here...

Gary

 Original message From: "Mickley, Joshua R 
(Genworth)"  Date:11/18/2014  14:36  
(GMT-05:00) To: dev@commons.apache.org Subject: [imaging] 
- Release Date and Production Suitability? 
Greetings All,

I am evaluating the use of Commons Imaging for a project involving image 
conversion and manipulation.

My question is around a timeline for an official release of Commons Imaging and 
suitability for use in a Production environment.

I am currently using the SNAPSHOT version and am curious what bits of 
functionality are needed prior to releasing the code.  The unit testing I have 
achieved to date gives me a good impression but I wanted to inquire and gain 
some additional insight.

Let me know if there are any specific areas where I can help contribute.

Thanks!
  -Josh

[OT] Java Image Processing Survival Guide - Re: [imaging] - Release Date and Production Suitability?

[Siegfried Goeschl]

Hi Josh,

this message is a little bit off-topic (since it promotes some of my work which 
is not directly related to Apache Commons Imaging) but you might check out

* 
https://github.com/sgoeschl/java-image-processing-survival-guide/tree/master/paper
 

* 
https://github.com/sgoeschl/java-image-processing-survival-guide/raw/master/slides/jipsg.pdf
 

* 
https://github.com/sgoeschl/java-image-processing-survival-guide/tree/master/code/jipsg

For two customer projects I converted millions of images using Apache Commons 
Imaging, Apache PDFBox, ImageIO, JAI & TwelveMonkeys and wrote a paper & 
presentation including sample code to compare the various image processing 
libraries. 

Depending on the scale of image processing you might experience a few of my 
problems and there are better things in life than tracing image conversion 
problems :-)

Cheers,

Siegfried Goeschl


> On 18 Nov 2014, at 20:36, Mickley, Joshua R (Genworth) 
>  wrote:
> 
> Greetings All,
> 
> I am evaluating the use of Commons Imaging for a project involving image 
> conversion and manipulation.
> 
> My question is around a timeline for an official release of Commons Imaging 
> and suitability for use in a Production environment.
> 
> I am currently using the SNAPSHOT version and am curious what bits of 
> functionality are needed prior to releasing the code.  The unit testing I 
> have achieved to date gives me a good impression but I wanted to inquire and 
> gain some additional insight.
> 
> Let me know if there are any specific areas where I can help contribute.
> 
> Thanks!
>  -Josh

[OT] Java Image Processing Survival Guide - Re: [imaging] - Release Date and Production Suitability?

[Mickley, Joshua R (Genworth)]

Siegfried,

Thank you for your response.  I have reviewed your paper and slides and found 
them to be very informative.  The requirements of my project are very closely 
aligned to the ones you have referenced.  I am glad to hear that you were able 
to achieve a successful end result and that Commons Imaging played a hand in 
it.  Hearing your story has given me increased confidence in its 
stability/reliability.

Thanks again!

From: Siegfried Goeschl [mailto:siegfried.goes...@it20one.com]
Sent: Tuesday, November 18, 2014 4:16 PM
To: Commons Developers List; Mickley, Joshua R (Genworth)
Subject: [OT] Java Image Processing Survival Guide - Re: [imaging] - Release 
Date and Production Suitability?

Hi Josh,

this message is a little bit off-topic (since it promotes some of my work which 
is not directly related to Apache Commons Imaging) but you might check out

* 
https://github.com/sgoeschl/java-image-processing-survival-guide/tree/master/paper
* 
https://github.com/sgoeschl/java-image-processing-survival-guide/raw/master/slides/jipsg.pdf
* 
https://github.com/sgoeschl/java-image-processing-survival-guide/tree/master/code/jipsg

For two customer projects I converted millions of images using Apache Commons 
Imaging, Apache PDFBox, ImageIO, JAI & TwelveMonkeys and wrote a paper & 
presentation including sample code to compare the various image processing 
libraries.

Depending on the scale of image processing you might experience a few of my 
problems and there are better things in life than tracing image conversion 
problems :-)

Cheers,

Siegfried Goeschl


On 18 Nov 2014, at 20:36, Mickley, Joshua R (Genworth) 
mailto:joshua.mick...@genworth.com>> wrote:

Greetings All,

I am evaluating the use of Commons Imaging for a project involving image 
conversion and manipulation.

My question is around a timeline for an official release of Commons Imaging and 
suitability for use in a Production environment.

I am currently using the SNAPSHOT version and am curious what bits of 
functionality are needed prior to releasing the code.  The unit testing I have 
achieved to date gives me a good impression but I wanted to inquire and gain 
some additional insight.

Let me know if there are any specific areas where I can help contribute.

Thanks!
 -Josh

[imaging] - Release Date and Production Suitability?

[Mickley, Joshua R (Genworth)]

Greetings All,

I am evaluating the use of Commons Imaging for a project involving image 
conversion and manipulation.

My question is around a timeline for an official release of Commons Imaging and 
suitability for use in a Production environment.

I am currently using the SNAPSHOT version and am curious what bits of 
functionality are needed prior to releasing the code.  The unit testing I have 
achieved to date gives me a good impression but I wanted to inquire and gain 
some additional insight.

Let me know if there are any specific areas where I can help contribute.

Thanks!
  -Josh

[site] Adding Github/Git mirrors to source-repository.html

[Bernd Eckenfels]

Hello,

what do you think, would it be a good idea to add a section about
git.apache.org and its GitHub mirror to the source-repository.html
report? 

I am not sure if it can be easily done as the SCM section will not
contain that information (for non-migrated projects), but I guess from
the project.id enough URL information can be derived for the both?

Gruss
Bernd

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Announce: Commons Inject

[Mark Struberg]

Hi Olivier!

There are ways to just exclude known jars from getting scanned by OpenWebBeans. 
And if the current solution isn't sufficient then just pop up on our list and 
we gonna implement it. Maybe I've overlooked you on the list or did you not yet 
reach out to us?


LieGrue,
strub





- Original Message -
> From: Oliver Heger 
> To: Commons Developers List 
> Cc: 
> Sent: Saturday, 8 November 2014, 20:51
> Subject: Re: Announce: Commons Inject
> 
> Hi Jochen,
> 
> do you intend to position this framework for specific use cases? In
> which way is it different or special from other implementations?
> 
> Just as one example: In the company I am working for, we are using CDI
> in a pretty large JSE application. Due to the huge class path the setup
> of the CDI container takes a long time and consumes a lot of memory
> (tested with both Weld SE and OpenWebBeans). So a fast and lightweight
> implementation for this special purpose would be interesting.
> 
> Oliver
> 
> 
> Am 04.11.2014 um 15:55 schrieb Jochen Wiedmann:
>>  Hi,
>> 
>>  As some of you (hopefulyl not all) may have noticed, have added a
>>  project called Commons Inject to the Sandbox [1] today. Commons Inject
>>  is a JSR 330 compliant dependency injection framework. It is something
>>  I had in the works for quite some time, but now it has reached a
>>  decent state with my preliminary milestones reached:
>> 
>>  - Passes the JSR 330 TCK.
>>  - Integrated lifecycle handling via @PostConstruct and @PreDestroy.
>>  Works with all scopes,
>>including lazy singletons. (I never got this to work with Guice,
>>  which has been my major
>>driver for doing this.)
>>  - Integrated logger injection framework for Log4J, SLF4J, and Commons
>>  Logging. Others can
>>easily be added.
>> 
>>  I intend to use this for serious works from now on and consequently
>>  hope to create a release real soon, at which point I'll ask to move
>>  this to proper.
>> 
>>  Any feedback welcome.
>> 
>>  Jochen
>> 
>>  [1] https://svn.apache.org/viewvc/commons/sandbox/commons-inject/trunk/
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Announce: Commons Inject

[Mark Struberg]

>> - I'm under the impression there are already well established
>> implementations of JSR 330

Well, the problem I see with this very approach is that it says it 'implements 
JSR-330'.
As an EG member I can tell you that atinject is only the least common 
denominator of the 'user side' of the story. It totally misses how those beans 
get created, how the scoped are filled, etc. It's really just the common part 
of Spring, CDI, Guice and EJB. 

That's basically like specifying a 'book' as a piece with pages with written 
words on it and packaged in a cover. This definition is fine for storing books 
in a library but it doesn't say anything about the content.

A concrete example: atinject defines @Scope. But how does those beans behave? 
How do they get stored and how do they get produced? Atinject defines none of 
those aspects. You would need to invent all of pieces on that side yourself.

Otoh OpenWebBeans core defines all this via CDI and has about 450k. Plus a few 
spec api jars which are not large neither. And this is not even specially 
trimmed down. We might be able to remove even more stuff (we did not try yet). 
There is also the possibility to e.g. switch our our default ScannerService and 
use one where you hand over the classes you like to use via a Set.

In the CDI EG we also currently experimenting with trimming down the 
functionality of CDI for pure CDI usage by e.g. trimming all the bytecode 
tinkering. We'd be happy to not only get feedback but also about additional 
helping hands ;)


LieGrue,
strub




- Original Message -
> From: Phil Steitz 
> To: Commons Developers List 
> Cc: 
> Sent: Saturday, 8 November 2014, 22:03
> Subject: Re: Announce: Commons Inject
> 
> On 11/4/14 9:08 AM, Emmanuel Bourg wrote:
>>  Le 04/11/2014 15:55, Jochen Wiedmann a écrit :
>> 
>>>  Any feedback welcome.
>>  Hi Jochen,
>> 
>>  I'm not a dependency injection expert so I can't really comment on 
> the
>>  design, I could just make trivial observations like the use of the 
> 'I'
>>  prefix for the interfaces which isn't used in the commons components 
> and
>>  may lead to some confusing names (IMutableBindingSource is not immutable).
>> 
>>  I'm more concerned by the viability of this project as a Apache Commons
>>  component:
>>  - Are there other committers interested in maintaining this project?
> 
> That's the right question to ask.
>>  - Will this be used by other Apache projects? I tend to see Apache
>>  Commons as the place to factorize common code used across Apache
>>  projects, I'm not sure it works very well in the other direction.
> 
> Well, [math] is one example of a component that started here and it
> has done OK.  I suspect most usage of [lang], [collections],
> [configuration] and quite a few others are outside apache as well at
> this point.  
>>  - I'm under the impression there are already well established
>>  implementations of JSR 330, what was the motivation behind this
>>  implementation? What are the selling points of this implementation
>>  compared to the others?
> 
> Always a good question to ask, but not a blocker.   Each time we
> start a new JSR-blah thing at the ASF you can ask the same
> question.  Whoever wants to grow a community around the new thing
> has to be able to find some shared itches to make it interesting.
> Ollie mentioned one thing.  Maybe there are others.
>>  - Why bringing this in Apache Commons instead of starting on Github?
> 
> Because we have the sandbox here as a place for committers to
> experiment with new components.  We all see what is going on there,
> so starting there also increases the chance that some other commons
> committers will get interested in the new thing.
> 
> Phil
>> 
>>  Emmanuel Bourg
>> 
>> 
>>  -
>>  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>  For additional commands, e-mail: dev-h...@commons.apache.org
> 
>> 
>> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Announce: Commons Inject

[Mark Struberg]

> Sorry, did not mean to step on somebody's toes.

No worries you didn't. It's most probably our fault as our (OpenWebBeans) 
documentation sucks and we did not properly document all this stuff ;)

If one of you guys is at ApacheCon in Budapest right now, then I'd love to give 
you a quick rush through our code an see if there is something you could use 
and also if we could improve something in OWB.

LieGrue,
strub




- Original Message -
> From: Oliver Heger 
> To: Commons Developers List 
> Cc: 
> Sent: Sunday, 9 November 2014, 11:45
> Subject: Re: Announce: Commons Inject
> 
> 
> 
> On 08.11.2014 21:51, Romain Manni-Bucau wrote:
>>  Le 8 nov. 2014 19:51, "Oliver Heger" 
>  a écrit
>>  :
>>> 
>>>  Hi Jochen,
>>> 
>>>  do you intend to position this framework for specific use cases? In
>>>  which way is it different or special from other implementations?
>>> 
>>>  Just as one example: In the company I am working for, we are using CDI
>>>  in a pretty large JSE application. Due to the huge class path the setup
>>>  of the CDI container takes a long time and consumes a lot of memory
>>>  (tested with both Weld SE and OpenWebBeans). So a fast and lightweight
>>>  implementation for this special purpose would be interesting.
>>> 
>> 
>>  Surely a bad example since you can achieve it with owb, just configure the
>>  scanner service
> 
> Sorry, did not mean to step on somebody's toes.
> 
> Oliver
> 
>> 
>>>  Oliver
>>> 
>>>  Am 04.11.2014 um 15:55 schrieb Jochen Wiedmann:
  Hi,
 
  As some of you (hopefulyl not all) may have noticed, have added a
  project called Commons Inject to the Sandbox [1] today. Commons 
> Inject
  is a JSR 330 compliant dependency injection framework. It is 
> something
  I had in the works for quite some time, but now it has reached a
  decent state with my preliminary milestones reached:
 
  - Passes the JSR 330 TCK.
  - Integrated lifecycle handling via @PostConstruct and @PreDestroy.
  Works with all scopes,
 including lazy singletons. (I never got this to work with Guice,
  which has been my major
 driver for doing this.)
  - Integrated logger injection framework for Log4J, SLF4J, and 
> Commons
  Logging. Others can
 easily be added.
 
  I intend to use this for serious works from now on and consequently
  hope to create a release real soon, at which point I'll ask to 
> move
  this to proper.
 
  Any feedback welcome.
 
  Jochen
 
  [1] 
> https://svn.apache.org/viewvc/commons/sandbox/commons-inject/trunk/
 
 
>>> 
>>> 
>>>  -
>>>  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>  For additional commands, e-mail: dev-h...@commons.apache.org
> 
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Announce: Commons Inject

[Mark Struberg]

Jochen, I might have done something wrong so please help me.

I've checked out your svn link and built it. 

Then I did a 

$> mvn clean -DincludeScope=runtime dependency:copy-dependencies
-rw-r--r--+ 1 struberg staff4467 19. Nov 08:41 aopalliance-1.0.jar
-rw-r--r--+ 1 struberg staff 2228009 19. Nov 08:41 guava-16.0.1.jar
-rw-r--r--+ 1 struberg staff  642741 19. Nov 08:41 guice-4.0-beta5.jar
-rw-r--r--+ 1 struberg staff2497 19. Nov 08:41 javax.inject-1.jar


$> du -hs target/dependencies 

show me 2.8 MB


Plus your own jar which is 76k.
Is there something wrong? What are you using guice and guava for?
Also there is an own ASF package for atinject [1].

LieGrue,
strub



[1] 
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-atinject_1.0_spec/1.0/




On Wednesday, 19 November 2014, 8:34, Mark Struberg  wrote:
>> Sorry, did not mean to step on somebody's toes.
>
>No worries you didn't. It's most probably our fault as our (OpenWebBeans) 
>documentation sucks and we did not properly document all this stuff ;)
>
>If one of you guys is at ApacheCon in Budapest right now, then I'd love to 
>give you a quick rush through our code an see if there is something you could 
>use and also if we could improve something in OWB.
>
>LieGrue,
>strub
>
>
>
>
>- Original Message -
>> From: Oliver Heger 
>> To: Commons Developers List 
>> Cc: 
>> Sent: Sunday, 9 November 2014, 11:45
>> Subject: Re: Announce: Commons Inject
>> 
>> 
>> 
>> On 08.11.2014 21:51, Romain Manni-Bucau wrote:
>>>  Le 8 nov. 2014 19:51, "Oliver Heger" 
>>  a écrit
>>>  :
 
  Hi Jochen,
 
  do you intend to position this framework for specific use cases? In
  which way is it different or special from other implementations?
 
  Just as one example: In the company I am working for, we are using CDI
  in a pretty large JSE application. Due to the huge class path the setup
  of the CDI container takes a long time and consumes a lot of memory
  (tested with both Weld SE and OpenWebBeans). So a fast and lightweight
  implementation for this special purpose would be interesting.
 
>>> 
>>>  Surely a bad example since you can achieve it with owb, just configure the
>>>  scanner service
>> 
>> Sorry, did not mean to step on somebody's toes.
>> 
>> Oliver
>> 
>>> 
  Oliver
 
  Am 04.11.2014 um 15:55 schrieb Jochen Wiedmann:
>  Hi,
> 
>  As some of you (hopefulyl not all) may have noticed, have added a
>  project called Commons Inject to the Sandbox [1] today. Commons 
>> Inject
>  is a JSR 330 compliant dependency injection framework. It is 
>> something
>  I had in the works for quite some time, but now it has reached a
>  decent state with my preliminary milestones reached:
> 
>  - Passes the JSR 330 TCK.
>  - Integrated lifecycle handling via @PostConstruct and @PreDestroy.
>  Works with all scopes,
> including lazy singletons. (I never got this to work with Guice,
>  which has been my major
> driver for doing this.)
>  - Integrated logger injection framework for Log4J, SLF4J, and 
>> Commons
>  Logging. Others can
> easily be added.
> 
>  I intend to use this for serious works from now on and consequently
>  hope to create a release real soon, at which point I'll ask to 
>> move
>  this to proper.
> 
>  Any feedback welcome.
> 
>  Jochen
> 
>  [1] 
>> https://svn.apache.org/viewvc/commons/sandbox/commons-inject/trunk/
> 
> 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
>
>> 
 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org