On Thu, Nov 27, 2008 at 03:50, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:

> Jérôme BERNARD wrote:
> > On Wed, Nov 26, 2008 at 01:35, Dennis Sosnoski <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >     I'd like to be able to use JiBX SNAPSHOT jars in Maven 2 projects,
> but
> >     it looks like we need to have a separate repository for that purpose.
> >
> >
> > Right. We are not allowed to publish SNAPSHOT artifacts to the
> > official Maven repo (through synchronization) as we do right now.
> >
> >
> >     Nigel suggested creating two separate Maven 2 repositories on
> >     Sourceforge, one for snapshots and one for releases. Hopefully we
> >     could
> >     set up the release repository to be automatically replicated to
> >     the main
> >     Maven repository, while keeping SNAPSHOTs only in their Sourceforge
> >     repository. Is anyone able to help set this up (or offer a better
> >     approach)?
> >
> >
> > This is the typical way to solve the issue.
> > I could probably help on that.
>
> Sounds great! How do we get started?


We could simply reuse what we have done so far with the non SNAPSHOTS repo.
This would publish on SF the repo as requested.
Now the real question might be who build the SNAPSHOTs?
You? a CI engine?
We may use my current instance of TeamCity for that if needed (
http://www.rio-project.org/teamcity)


> >     My current need is with Axis2, where I've tried to add my JiBX 1.2
> >     SNAPSHOT jars manually to the build for testing. You're supposed to
> be
> >     able to add jars directly using "mvn install:install-file ...",
> >     but this
> >     gives an error message "POM 'org.apache.axis2:axis2-mar-maven-plugin'
> >     not found in repository..." - and nobody involved in Axis2 seems
> >     to know
> >     enough about the Maven 2 build to tell me how to get around the
> >     problem.
> >     Having a SNAPSHOT repository would hopefully offer an easier approach
> >     for dealing with this type of build issue.
> >
> >
> > You want to publish JiBX SNAPSHOTS or be able to host other kind of
> > dependencies on that repository (like Axis dependencies)?
> > 'Cause it sounds like Axis2 artifacts are already available?
> > http://mvnrepository.com/artifact/org.apache.axis2
>
> The issue is that the Axis2 JiBX support builds on the JiBX jars, and
> before I can modify Axis2 to work with JiBX 1.2 I need to be able to
> reference the JiBX SNAPSHOT jars from the Axis2 build. The only way I
> know to do that is to have a repository I can add to the list being
> checked by my own copy of the Axis2 build, so that the Axis2 build will
> pull in the SNAPSHOT jars.


Ok. So If I got that right all you want to do is to publish JiBX SNASHOTs.
One of the use is going to be able to use those JiBX SNAPSHOTs from a custom
Axis2 build.
Did I got that right?



Jerome

-- 
Jerome Bernard,
Director, EMEA Operations,
Elastic Grid, LLC.

Blog: http://blog.elastic-grid.com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs

Reply via email to