Apache JDO Project - Patch for project.xml

Author

Patch for project.xml

Michael Watzek

2005-08-05, 7:45 am

Hi,

I suggest to update the reference to c3p0 to version "0.9.0". The
attached file contains a patch of "project.xml". Before you run the
patch, make sure to download that version. This is the download URL:

http://prdownloads.sourceforge.net/...?use_mirror=ovh

Regards,
Michael
--
-------------------------------------------------------------------
Michael Watzek Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
-------------------------------------------------------------------

Craig Russell

2005-08-07, 2:45 am

Andy Jefferson

2005-08-07, 2:45 am

> Is maven not able to do use sourceforge download? What's the story?
>
> Please don't tell me to just download it manually. That obviously
> works. Why not automatic?

> Attempting to download c3p0-0.9.0.jar.
> WARNING: Failed to download c3p0-0.9.0.jar.
> The build cannot continue because of the following unsatisfied
> dependency:
>
> c3p0-0.9.0.jar (try downloading from http://
> prdownloads.sourceforge.net/c3p0/c3p0-0.9.0.bin.zip?use_mirror=unc)

Hi Craig,

Maven can download from a Maven repository. SourceForge doesn't have one. The
issue isn't that.

It's probably that the "maven.repo.remote" environment variable (which I
always put in $HOME/build.properties) is only set to
"http://www.jpox.org/downloads/maven" now (added by this patch).
It really ought to be

http://www.ibiblio.org/maven, http://www.jpox.org/downloads/maven

(i.e comma separated list of all repos that you want to look at) so then Maven
will look at IBiblio first and, if the artifact isn't there, will use the
JPOX repo (which only contains JPOX artifacts) next.

--
Andy

Karan Malhi

2005-08-07, 7:45 am

Hi Andy,

You are right. I am sorry Craig, i guess i should have read the maven
documentation before submitting the patch. The reason i added the repository
to the project.properties of tck20 is because i looked into the
project.xmlof the other projects and found that only tck20 depended on
jpox.

So, i guess i overrided the remote repository settings for the tck20 project
by submitting the patch. It would have been nice if i would have been able
to append to the existing remote repository settings. I did read the maven
documentation this time, and there i found out that in the next release of
maven we can append a remote repository to the existing one like this:

maven.repo.remote=${maven.repo.remote}, http://www.jpox.org/downloads/maven

Maybe we should consider upgrading to the next stable release of maven
(whenever it is released), just to keep our lives simpler.

I will be submitting a patch to fix the current problem.

However, i looked into the ibiblio maven repository and found that the
repository contained entries for antlr. I could not find antlr version 2.7.3,
but i did find the version 2.7.1 , 2.7.2, 2.7.4, 2.7.5.
My questions are as follows --

1. Does this project depend on 2.7.3 or can we move to 2.7.4 or 2.7.2. If
yes, then this will allow us to set maven to automatically download antlr.

2. Andy, if we can upload something to ibiblio repository using the
following (as you mentioned in a mail earlier)
maven create-upload-bundle

then why do we need a seperate repository for jpox to be hosted at
www.jpox.org <http://www.jpox.org>. Can the jpox group upload the jars at
the ibiblio repository?
3. What is the best practice while specifying the remote repository
location? Do we just keep appending to ~/build.properties or do we keep
appending new locations to the individual projects' project.properties?

On 8/7/05, Andy Jefferson <andy@jpox.org> wrote:
>
>
>
> Hi Craig,
>
> Maven can download from a Maven repository. SourceForge doesn't have one.
> The
> issue isn't that.
>
> It's probably that the "maven.repo.remote" environment variable (which I
> always put in $HOME/build.properties) is only set to
> "http://www.jpox.org/downloads/maven" now (added by this patch).
> It really ought to be
>
> http://www.ibiblio.org/maven, http://www.jpox.org/downloads/maven
>
> (i.e comma separated list of all repos that you want to look at) so then
> Maven
> will look at IBiblio first and, if the artifact isn't there, will use the
> JPOX repo (which only contains JPOX artifacts) next.
>
> --
> Andy
>

--
Karan Malhi

Andy Jefferson

2005-08-07, 5:45 pm

> 2. Andy, if we can upload something to ibiblio repository using the
> following (as you mentioned in a mail earlier)
> maven create-upload-bundle

Hi Karan,

no, JPOX cannot upload things to IBiblio like that. All that maven
create-upload-bundle does is create a jar that can then be passed to the
Maven people to upload. JPOX has to go through the published Maven process
for uploading (http://maven.apache.org/reference/r...ory-upload.html)
If Apache have some way of uploading things to IBiblio using these bundles
then they can use that, but JPOX has no connection with Apache and we follow
the standard process to get things on Ibiblibliblio.

Trygve,
can IBiblio set up an rsync with the JPOX maven repo ? (just like they do with
the "maven-plugins" SF repo). If so, can you please request it from whoever
does such things.

--
Andy
Java Persistent Objects - JPOX

Niclas Hedhman

2005-08-07, 5:45 pm

On Sunday 07 August 2005 20:43, Karan Malhi wrote:
> 1. Does this project depend on 2.7.3 or can we move to 2.7.4 or 2.7.2. If
> yes, then this will allow us to set maven to automatically download antlr.

Someone wrote that the ANTLR version being dependent upon is custom, but the
version numbering doesn't indicate anything special, so perhaps it is just a
"pre-built" with features coming into later versions.

> 2. Andy, if we can upload something to ibiblio repository using the
> following (as you mentioned in a mail earlier)
> maven create-upload-bundle
> then why do we need a seperate repository for jpox to be hosted at
> www.jpox.org <http://www.jpox.org>. Can the jpox group upload the jars at
> the ibiblio repository?

ibiblio.org is a large data store with a long-term noble goal of NEVER
removing anything that has been placed there. Therefor, the general
recommendation is to keep "temporary" artifacts on "other" repository hosts.
Apache uses http://cvs.apache.org/repository, and all Apache committers can
put stuff in there, and it is NOT synced out to ibiblio.org.

It is also expected that all temporary content is removed from there as those
artifacts get released properly.

> 3. What is the best practice while specifying the remote repository
> location? Do we just keep appending to ~/build.properties or do we keep
> appending new locations to the individual projects' project.properties?

I think the general consensus is that this should be specified for each
project, so that "no extra steps" are required to build a project after
checkout. Normally the home dir settings are only used for "personal" things,
like passwords to upload artifacts.

Cheers
Niclas

Trygve Laugstøl

2005-08-07, 5:45 pm

On Sun, Aug 07, 2005 at 01:54:11PM +0100, Andy Jefferson wrote:
>
> Hi Karan,
>
> no, JPOX cannot upload things to IBiblio like that. All that maven
> create-upload-bundle does is create a jar that can then be passed to the
> Maven people to upload. JPOX has to go through the published Maven process
> for uploading (http://maven.apache.org/reference/r...ory-upload.html)
> If Apache have some way of uploading things to IBiblio using these bundles
> then they can use that, but JPOX has no connection with Apache and we follow
> the standard process to get things on Ibiblibliblio.

I though JPOX was supposed to move to Apache as the JDO RI? If so you
could use the same automagic upload process as JDO.

> Trygve,
> can IBiblio set up an rsync with the JPOX maven repo ? (just like they dowith
> the "maven-plugins" SF repo). If so, can you please request it from whoever
> does such things.

We're going to make a separate repository for SNAPSHOTs[1]. We'll get back
to you when the repository is set up. Currently the strategy is that all
folks that want to depend on snapshots has to use the repository from the developers like you already have[2].

Btw, technically the rsync is done by the Maven team, we synch from the
sources (maven-plugins, apache, etc) to our master server and then sync
that to ibiblio.

[1]: http://jira.codehaus.org/browse/MNG-708
[2]: http://www.jpox.org/downloads/maven

--
Trygve

Craig Russell

2005-08-07, 5:45 pm

Craig Russell

2005-08-07, 5:45 pm

Karan Malhi

2005-08-07, 8:45 pm

Hi ,

There is a lot of useful information about maven which was poured in during
this exchange of emails. I am trying to document it for my own use. If any
one of you have any useful comments/suggestions/best practices to
contribute, that would be really useful for me. This will really help a
novice like me to minimize on my mistakes (i am still trying to read the
maven docs whenever i get time). Also later on, this document could also be
shared with people new to maven.

Best Regards

Karan Malhi
On 8/7/05, Craig Russell <Craig.Russell@sun.com> wrote:
>
> Hi Niclas,
> On Aug 7, 2005, at 5:57 AM, Niclas Hedhman wrote:
>
> On Sunday 07 August 2005 20:43, Karan Malhi wrote:
>
> 1. Does this project depend on 2.7.3 or can we move to 2.7.4 or 2.7.2. If
> yes, then this will allow us to set maven to automatically download antlr..
>
>
> Someone wrote that the ANTLR version being dependent upon is custom, but
> the
> version numbering doesn't indicate anything special, so perhaps it is just
> a
> "pre-built" with features coming into later versions.
>
>
> The reason we use 2.7.3 is that there are some "hand-crafted" pieces of
> our .g files that support international characters in a way that is not
> standard, so we need to adapt it for each new release of ANTLR. We're hoping
> that the international support in ANTLR can eventually allow us to drop the
> special stuff and we can go with the latest.
>
> I think Brian tried 2.7.5 but it didn't work so we need to look at it
> more.
>
> Craig
>
> Cheers
> Niclas
>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com <Craig.Russell@sun.com>
>
> P.S. A good JDO? O, Gasp!
>
>
>

--
Karan Malhi