Hi Jakub,
On Fri, 2008-06-13 at 09:15 +0200, Jakub Podlesak wrote:
> what is published now at m2 java.net repo should work, i have tested a simple project
> with [jersey-spring] dependency having cleaned my local repos in advance.
> Could you please double-check? I can then configure auto-deployment of [jersey-contribs] from Hudson.
> It will be done by % cd jersey ; mvn clean deploy
I just removed jersey from my local repo and compiled our project again
and it went through without any problems - cool!
Cheers,
Martin
On Fri, 2008-06-13 at 09:15 +0200, Jakub Podlesak wrote:
> On Thu, Jun 12, 2008 at 08:45:44PM +0200, Martin Grotzke wrote:
> > Hi Jakub,
> >
> > On Thu, 2008-06-12 at 16:31 +0200, Jakub Podlesak wrote:
> > > On Tue, Jun 03, 2008 at 03:55:51PM +0200, Jakub Podlesak wrote:
> > > > On Mon, Jun 02, 2008 at 05:52:18PM +0200, Martin Grotzke wrote:
> > > > > Regarding jersey-spring: Have you already tried to deploy this from
> > > > > contribs/spring? It would be really great to have this also available
> > > > > via maven!
> > > >
> > > > I have updated the [contribs/pom.xml] file and did the initial push.
> > > > Could you please check it up and let me know? I can then configure the hudson job accordingly,
> > > > so that bits get pushed automatically.
> > > > You can find the artifacts at [1] and [2].
> > > >
> > > > I am curious, if having jersey version as "${jersey-version}" at [3] is ok?
> > >
> > > i think at the moment i will simply hardcode the current version (0.8-ea-SNAPSHOT) there
> > > to have something working quickly. then will work on a more generic/clean solution.
> > > (we can always make a rollback ;-)
> > As I wrote in [3] IMO this is because the jersey-project pom.xml [2] is
> > a generated one and not the one from the svn repo. The generated pom.xml
> > does not provide the ${jersey-version} property and therefore it cannot
> > be resolved. So I would suggest to deploy the jersey-project with the
> > pom.xml from svn.
>
> done, original [jersey-project] pom was anyway wrong (a relict from an unsuccesful attempt
> to deploy jersey.jar stuff). (i have found only in the meantime how to remove things from
> m2 java-net repo, so it should not happen in the future any more:-p
>
> i have updated the [spring/pom.xml] so that it refers to ${project.version} version
> of jersey (i believe the tho (jersey-spring and jersey) should be in sync) rather
> than to ${jersey-version}
>
> i have also commented out all modules but [contribs] in [jersey-project], so that it does not
> try to redeploy [jersey] (deployed separately for the time being).
>
> what is published now at m2 java.net repo should work, i have tested a simple project
> with [jersey-spring] dependency having cleaned my local repos in advance.
> Could you please double-check? I can then configure auto-deployment of [jersey-contribs] from Hudson.
> It will be done by % cd jersey ; mvn clean deploy
>
> thanks,
>
> -jakub
>
> >
> > Cheers,
> > Martin
> >
> >
> > [1] https://jersey.dev.java.net/servlets/ReadMsg?listName=users&msgNo=1500
> > [2] http://download.java.net/maven/2/com/sun/jersey/jersey-project/0.8-ea-SNAPSHOT/
> >
> >
> > >
> > > -jakub
> > >
> > > >
> > > > Thanks,
> > > >
> > > > ~Jakub
> > > >
> > > > [1]http://download.java.net/maven/2/com/sun/jersey/jersey-contribs/
> > > > [2]http://download.java.net/maven/2/com/sun/jersey/jersey-spring/
> > > > [3]http://download.java.net/maven/2/com/sun/jersey/jersey-spring/0.8-ea-SNAPSHOT/jersey-spring-0.8-ea-SNAPSHOT.pom
> > > >
> > > > >
> > > > > Cheers,
> > > > > Martin
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > ~Jakub
> > > > > >
> > > > > > [1]http://download.java.net/maven/2/javax/ws/rs/jsr311-api/0.8-SNAPSHOT/
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > I am now going to look at how to push it from within Jersey and
> > > > > > > > eventually switch it on.
> > > > > > > Great!
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Martin
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > ~Jakub
> > > > > > > > >
> > > > > > > > > What do you think?
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Martin
> > > > > > > > >
> > > > > > > > > [1] http://download.java.net/maven/2/com/sun/jersey/jersey/0.8-ea-SNAPSHOT/jersey-0.8-ea-SNAPSHOT.pom
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wed, 2008-05-28 at 18:30 +0200, Jakub Podlesak wrote:
> > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> > > For additional commands, e-mail: users-help_at_jersey.dev.java.net
> >
>
>