Hi Martin,
On Wed, May 28, 2008 at 05:28:34PM +0200, Jakub Podlesak wrote:
>
> > Ok. Having jersey snapshots available would be really great!
> >
> > >
> > > I tried to tweak a bit the [pom.xml] (see attached) in [jersey/maven] subdirectory
> > > (changed packaging to jar, updated version, added some stuff to distribution management),
> > > but it produces (and pushes) a jar file, which differs from that created by ant (in [dist] subdirectory).
> > >
> > > Could you please help?
> > I have never used mvn deploy, but I would think that deploy:deploy-file
> > is appropriate here - using the jar file created by ant you wouldn't
> > have to change the packaging I'd think. Can you try that? Or shall I try
> > getting mvn deploy to work (starting with a local repo as you did)?
>
> Ok, i will try deploy:deploy-file and if it works, will configure Hudson this way.
I have just tried to add an aux [deploy.pom] into jersey repository and
deploy a Jersey snapshot [1] via:
mvn deploy:deploy-file -f maven/deploy.pom -Dfile=../dist/jersey.jar -DgroupId=com.sun.jersey -DartifactId=jersey-project -Dversion=0.8-ea-SNAPSHOT -Dpackaging=jar -DrepositoryId=dev.java.net.m2 -Durl=java-net:/maven2-repository/trunk/www/repository/
Martin, can you confirm it is all-right and could be configured this way on Hudson,
so that we have most recent snapshots updated automatically?
Thanks,
~Jakub
[1]
http://download.java.net/maven/2/com/sun/jersey/jersey-project/0.8-ea-SNAPSHOT/
>
> ~Jakub
>
> >
> > >
> > > Apart from that, let me look at mavenizing the rest of examples.
> > > I will let you know if i have issues with that.
> > Yeah, really great! :)
> >
> > Cheers,
> > Martin
> >
> >
> > >
> > > Thanks,
> > >
> > > ~Jakub
> > >
> > >
> > > On Wed, May 28, 2008 at 02:46:35PM +0200, Martin Grotzke wrote:
> > > > Hi,
> > > >
> > > > I want to clarify how we proceed with the mavenization of jersey.
> > > >
> > > > IMO there are these TODOs:
> > > > 1) Continue/finish mavenization of jersey examples
> > > > 2) Split jersey into (maven) modules
> > > > 3) Configure maven plugins so that all required artifacts are created
> > > >
> > > > Concerning 1) I could mavenize another jersey example and provide a
> > > > simple howto that describes what has to been done to mavenize a
> > > > "standard" jersey example.
> > > >
> > > > Concerning 2) I could also create (or support creating) maven modules
> > > > from jersey: impl, api and spi (the content of the jersey/src folder).
> > > > What about the naming of the modules?
> > > >
> > > > For 3) we need to clarify what artifacts have to be created. I know of
> > > > these:
> > > > - Default artifacts (jar files, poms for parent modules)
> > > > - Binary distribution of the whole jersey project, including contribs
> > > > and samples
> > > > - Source distribution of the same
> > > >
> > > > Are there other suggestions?
> > > >
> > > > What about the timeframe / schedule?
> > > >
> > > > Cheers,
> > > > Martin
> > > >
> > > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> > > For additional commands, e-mail: users-help_at_jersey.dev.java.net
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>