|
Home > Archive > Apache JDO Project > July 2005 > Place to download JPOX nightly builds
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Place to download JPOX nightly builds
|
|
|
|
| Trygve Laugstøl 2005-07-29, 5:45 pm |
| On Fri, Jul 29, 2005 at 09:54:22AM -0700, erik@jpox.org wrote:
>
> A JPOX on you. :-)
>
> http://www.jpox.org/downloads/nightly/
Is it possible to make these jars available in a Maven repository? I'm
working on Maven Continuum (a CI server) and we're using the latest JPOX
code and it would make our lifes much easier if these where available to
us.
--
Trygve
| |
| erik@jpox.org 2005-07-29, 5:45 pm |
| Trygve,
We usually make releases available in ibiblio, but not nightly builds. It takes
days to have a jar deployed in ibiblio, unless you know a way to go though
that, do you? :-)
Regards,
Erik Bengtson
Quoting Trygve Laugstøl <trygvis@inamo.no>:
> On Fri, Jul 29, 2005 at 09:54:22AM -0700, erik@jpox.org wrote:
>
> Is it possible to make these jars available in a Maven repository? I'm
> working on Maven Continuum (a CI server) and we're using the latest JPOX
> code and it would make our lifes much easier if these where available to
> us.
>
> --
> Trygve
>
| |
| Trygve Laugstøl 2005-07-29, 5:45 pm |
| On Fri, Jul 29, 2005 at 10:11:46AM -0700, erik@jpox.org wrote:
> Trygve,
>
> We usually make releases available in ibiblio, but not nightly builds. Ittakes
> days to have a jar deployed in ibiblio, unless you know a way to go though
> that, do you? :-)
Yes I do:
1) Just make a simple Maven repository under the jpox site, for example
like this:
http://www.jpox.org/downloads/maven
And use Maven to deploy to this repository.
2) Talk to the Maven repository team (I'm a part of the team) to get the
snapshots uploaded into the SNAPSHOTs repository. As a part of our work
on Maven 2 we have done substansial work on the repository structure
and one of these changes are splitting the repo into release and
snapshot repositories.
Note that 2) requires 1) in one form or another, it can be private but I
don't see a reason why you would want that.
Also note that 1) is useful on it's own; I can have multiple remote
repositories in my Maven project configuration.
--
Trygve
| |
|
|
| Trygve Laugstøl 2005-07-29, 5:45 pm |
| On Fri, Jul 29, 2005 at 06:51:24PM +0100, Andy Jefferson wrote:
>
> Should be populated from the next nightly build.
Awesome! Thanks. Given that the repository contains valid POMs we can get
this synchronized over to the Maven snapshot repository. Now, it seems
that we only have support for rsynch-ing repositories over ssh, so I hope
that can be arranged.
--
Trygve
| |
| Trygve Laugstøl 2005-07-30, 2:45 am |
| On Fri, Jul 29, 2005 at 06:51:24PM +0100, Andy Jefferson wrote:
>
> Should be populated from the next nightly build.
Yep, they where populated but it doesn't seem like you're using the
artifact plugin[1] to deploy them. For us to be able to synch the
repository we need the proper metadata available which the artifact plugin
will do. This includes fully resolving the POM (collapsing the parent and
child POM). It also resolve the SNAPSHOT to a specific timestamp.
Andy: I reported a issue about the project.xml files having a circular
dependency a while ago, was that issue resolved? I tried to find the issue
again but when I tried to search in the issue tracker I wasn't able to
find it. It seemed like it would reset my filter and just return the
default set of issues.
[1]: http://maven.apache.org/reference/plugins/artifact
--
Trygve
| |
| Andy Jefferson 2005-07-30, 2:45 am |
| > Yep, they where populated but it doesn't seem like you're using the
> artifact plugin[1] to deploy them. For us to be able to synch the
> repository we need the proper metadata available which the artifact plugin
> will do. This includes fully resolving the POM (collapsing the parent and
> child POM). It also resolve the SNAPSHOT to a specific timestamp.
Only because the nightly build ran before all updates were available from CVS
(i.e anonymous CVS on SourceForge which is a few hours behind developer CVS),
consequently the artifact part wasn't included, but is now.
> Andy: I reported a issue about the project.xml files having a circular
> dependency a while ago, was that issue resolved? I tried to find the issue
> again but when I tried to search in the issue tracker I wasn't able to
> find it. It seemed like it would reset my filter and just return the
> default set of issues.
The issue log is not currently supported. As I pointed out in your issue, the
"circular dependency" issue is not an issue since the DBCP plugin is built
once only, and hasnt changed since beta-3, hence JPOX Core has a dependency
on jpox-dbcp-1.1.0-beta-3 (which could be removed, but that is for tests only
and we've got better things to spend our time on). We won't be moving to
Maven 2 before JPOX 1.1 is released.
--
Andy
|
|
|
|
|