Hi Kasper,

I don't think there are official pom.xml's for jglobus v < 2.
I'm using jglobus 1.8.4 with some modifications and set up a maven
repository, feel free to use that. Repository:

                <repository>
                        <id>releases</id>

<url>http://code.ceres.auckland.ac.nz/nexus/content/groups/public/</url>
                        <releases>
                                <enabled>true</enabled>
                                <updatePolicy>daily</updatePolicy>
                                <checksumPolicy>warn</checksumPolicy>
                        </releases>
                        <snapshots>
                                <enabled>false</enabled>
                                <updatePolicy>always</updatePolicy>
                                <checksumPolicy>fail</checksumPolicy>
                        </snapshots>
                </repository>


And those are the dependencies, not sure whether some of them are
unnecessary:

                <dependency>
                        <groupId>org.bouncycastle</groupId>
                        <artifactId>bcprov-jdk15</artifactId>
                        <version>${bcprov.version}</version>
                        <scope>provided</scope>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>cog-jglobus</artifactId>
                        <version>1.8.4-nesi</version>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>cog-url</artifactId>
                        <version>1.7.0</version>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>cryptix32</artifactId>
                        <version>1.7.0</version>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>cryptix-asn1</artifactId>
                        <version>1.7.0</version>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>cryptix</artifactId>
                        <version>1.7.0</version>
                </dependency>

                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>jgss</artifactId>
                        <version>1.7.0</version>
                </dependency>
                <dependency>
                        <groupId>external.jglobus</groupId>
                        <artifactId>puretls</artifactId>
                        <version>1.7.0</version>
                </dependency>


Cheers,
Markus


On Mon, 2013-02-04 at 08:58 +0000, Kasper van den Berg wrote:
> Hi all,
> 
> I'm converting a project to maven.  The project, written in java, imports the 
> package org.globus.io.streams for the class GridFTPStream.
> 
> Googling it gives javadocs from version 1.2.
> 
> The maven pom-file for the project contains a dependency on 
> org.jglobus:JGlobus-Core:2.0.4.
> 
> For now being able to compile the project without errors is sufficient.  
> Upgrading dependencies to state of the art is of later concern.
> 
> Is org.globus.io.streams.GridFTPStream still available? Either in the current 
> release in an older version?
> Which (additional) maven dependency should I use?
> 
> 
> With kind regards,
> Kasper van den Berg
> =====================================
> Disclaimer MAASTRO clinic:
> 
> Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen 
> bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, 
> verzoeken wij u dit onmiddellijk aan ons te melden en de inhoud van het 
> bericht te vernietigen.
> 
> This message shall not constitute any obligations. This message is intended 
> solely for the addressee. If you have received this message in error, please 
> inform us immediately and delete its contents.
> =====================================


Reply via email to