Hi Josh,

there is no official release yet - try

    <repositories>
        <repository>
          <id>repository.apache.org</id>
          <name>repository.apache.org</name>
          <url>https://repository.apache.org/content/groups/snapshots/</url>
        </repository>
    </repositories>       

    <dependencies>
        <dependency>
            <groupId>org.apache.commons</groupId>
            <artifactId>commons-imaging</artifactId>
            <version>1.0-SNAPSHOT</version>           
            <scope>test</scope>
        </dependency>
    </dependencies>

Cheers,

Siegfried Goeschl

----- Ursprüngliche Mail -----
Von: Gary Gregory <[email protected]>
An: Commons Users List <[email protected]>
Gesendet: Tue, 14 Oct 2014 23:59:18 +0200 (CEST)
Betreff: Re: [Imaging] sanselan dependency missing Imaging class

Your best bet is to depend on a 1.0-SNAPSHOT build

Gary

On Tue, Oct 14, 2014 at 5:20 PM, Josh Highley <[email protected]> wrote:

> Per the main imaging page, I've added sanselan as a dependency to my
> project:
>
> <groupId>org.apache.sanselan</groupId>
> <artifactId>sanselan</artifactId>
> <version>0.97-incubator</version>
>
> However, this does not include the org.apache.commons.imaging.Imaging class
> referenced in the javadocs and the image read example:
>
> https://svn.apache.org/repos/asf/commons/proper/imaging/trunk/src/test/java/org/apache/commons/imaging/examples/ImageReadExample.java
>
> I can't find commons-imaging in a Maven repo.  What information am I
> missing?
>
> Thanks,
>
> Josh
>



-- 
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to