You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mark Diggory <md...@MIT.EDU> on 2007/10/02 21:59:43 UTC
setting up rsync remote repo and release questions
I'm following the guidelines located here and trying to prepare our
repository to be rsynced into the central repo.
http://maven.dspace.org/release
http://maven.dspace.org/snapshot
I have a few questions.
1.) by "release" do you mean that only true versioned releases (not
snapshots) can be rsynced to the central repo?
2.) We have our own compilations of apache cocoon, lucene and other
various jars (bouncy-castle, jena (hp) which we need to maintain
slightly customized for our project. we keep these under our
org.dspace groupId, is it ok to place "releases" of these third party
jars in our groupId space?
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>jena</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>handle</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>jargon</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>mets</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>bcprov-jdk15</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>bcmail-jdk15</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>lucene</artifactId>
> </dependency>
> <dependency>
> <groupId>org.dspace</groupId>
> <artifactId>tm-extractors</artifactId>
> </dependency>
thanks,
Mark
~~~~~~~~~~~~~
Mark R. Diggory - DSpace Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology
Re: setting up rsync remote repo and release questions
Posted by Mark Diggory <md...@MIT.EDU>.
Sorry, thats an error, yes some of the Apache stuff we are working
with did not have latest versions in the central repo, I see Lucene
2.2.0 was placed in there earlier this summer and I'll switch us to
that. We'll also ask about getting the latest bouncycastle jars
added as well.
-Mark
On Oct 2, 2007, at 11:06 PM, Dan Tran wrote:
> just curious, why repackage lucene?
>
> -D
>
> On 10/2/07, Carlos Sanchez <ca...@apache.org> wrote:
>> 1) yes
>> 2) yes
>>
>> On 10/3/07, Mark Diggory <md...@mit.edu> wrote:
>>> I'm following the guidelines located here and trying to prepare our
>>> repository to be rsynced into the central repo.
>>>
>>> http://maven.dspace.org/release
>>> http://maven.dspace.org/snapshot
>>>
>>> I have a few questions.
>>>
>>> 1.) by "release" do you mean that only true versioned releases (not
>>> snapshots) can be rsynced to the central repo?
>>>
>>> 2.) We have our own compilations of apache cocoon, lucene and other
>>> various jars (bouncy-castle, jena (hp) which we need to maintain
>>> slightly customized for our project. we keep these under our
>>> org.dspace groupId, is it ok to place "releases" of these third
>>> party
>>> jars in our groupId space?
>>>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>jena</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>handle</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>jargon</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>mets</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>bcprov-jdk15</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>bcmail-jdk15</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>lucene</artifactId>
>>>> </dependency>
>>>> <dependency>
>>>> <groupId>org.dspace</groupId>
>>>> <artifactId>tm-extractors</artifactId>
>>>> </dependency>
>>>
>>> thanks,
>>> Mark
>>>
>>> ~~~~~~~~~~~~~
>>> Mark R. Diggory - DSpace Systems Manager
>>> MIT Libraries, Systems and Technology Services
>>> Massachusetts Institute of Technology
>>>
>>>
>>>
>>
>>
>> --
>> I could give you my word as a Spaniard.
>> No good. I've known too many Spaniards.
>> -- The Princess Bride
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: setting up rsync remote repo and release questions
Posted by Dan Tran <da...@gmail.com>.
just curious, why repackage lucene?
-D
On 10/2/07, Carlos Sanchez <ca...@apache.org> wrote:
> 1) yes
> 2) yes
>
> On 10/3/07, Mark Diggory <md...@mit.edu> wrote:
> > I'm following the guidelines located here and trying to prepare our
> > repository to be rsynced into the central repo.
> >
> > http://maven.dspace.org/release
> > http://maven.dspace.org/snapshot
> >
> > I have a few questions.
> >
> > 1.) by "release" do you mean that only true versioned releases (not
> > snapshots) can be rsynced to the central repo?
> >
> > 2.) We have our own compilations of apache cocoon, lucene and other
> > various jars (bouncy-castle, jena (hp) which we need to maintain
> > slightly customized for our project. we keep these under our
> > org.dspace groupId, is it ok to place "releases" of these third party
> > jars in our groupId space?
> >
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>jena</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>handle</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>jargon</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>mets</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>bcprov-jdk15</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>bcmail-jdk15</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>lucene</artifactId>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.dspace</groupId>
> > > <artifactId>tm-extractors</artifactId>
> > > </dependency>
> >
> > thanks,
> > Mark
> >
> > ~~~~~~~~~~~~~
> > Mark R. Diggory - DSpace Systems Manager
> > MIT Libraries, Systems and Technology Services
> > Massachusetts Institute of Technology
> >
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: setting up rsync remote repo and release questions
Posted by Carlos Sanchez <ca...@apache.org>.
1) yes
2) yes
On 10/3/07, Mark Diggory <md...@mit.edu> wrote:
> I'm following the guidelines located here and trying to prepare our
> repository to be rsynced into the central repo.
>
> http://maven.dspace.org/release
> http://maven.dspace.org/snapshot
>
> I have a few questions.
>
> 1.) by "release" do you mean that only true versioned releases (not
> snapshots) can be rsynced to the central repo?
>
> 2.) We have our own compilations of apache cocoon, lucene and other
> various jars (bouncy-castle, jena (hp) which we need to maintain
> slightly customized for our project. we keep these under our
> org.dspace groupId, is it ok to place "releases" of these third party
> jars in our groupId space?
>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>jena</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>handle</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>jargon</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>mets</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>bcprov-jdk15</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>bcmail-jdk15</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>lucene</artifactId>
> > </dependency>
> > <dependency>
> > <groupId>org.dspace</groupId>
> > <artifactId>tm-extractors</artifactId>
> > </dependency>
>
> thanks,
> Mark
>
> ~~~~~~~~~~~~~
> Mark R. Diggory - DSpace Systems Manager
> MIT Libraries, Systems and Technology Services
> Massachusetts Institute of Technology
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org