On Thu, May 29, 2008 at 08:49:50AM +0200, Martin Grotzke wrote:
> Probably you should use the generated/configured jersey-pom.xml from
> build/maven. This has correct properties like artifactId, version,
> packaging etc.. The pom.xml in the repo ([1]) seems to be a configured
> one, IMHO you should disable pom generation.
>
> You might invoke mvn like this:
>
> mvn deploy:deploy-file -f maven/deploy.pom -Dfile=../dist/jersey.jar
> -DpomFile=../build/maven/jersey-pom.xml -DrepositoryId=dev.java.net.m2
> -Durl=java-net:/maven2-repository/trunk/www/repository/
> -DgeneratePom=false
Danke, Martin!
Configured this way on Hudson, added -DuniqueVersion=false to save
some disk space.
>
> (I didn't test if this works...)
>
> Btw: are you going to configure mvn deploy for jersey-spring also? This
> should be simply mvn deploy, as we don't have to use a custom pom file,
> jar file etc.
you mean cd jersey/contribs && mvn deploy ?
it currently gives me:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Contributions to Jersey
[INFO] jersey-spring
[INFO] ------------------------------------------------------------------------
[INFO] Building Contributions to Jersey
[INFO] task-segment: [deploy]
[INFO] ------------------------------------------------------------------------
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /export/home/japod/workspace/jersey-trunk/jersey/contribs/pom.xml to /export/home/japod/.m2/repository/com/sun/jersey/jersey-contribs/0.8-ea-SNAPSHOT/jersey-contribs-0.8-ea-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.3
check that the following section of the pom.xml is present and correct:
<distributionManagement>
<!-- use the following if you're not using a snapshot version. -->
<repository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</repository>
<!-- use the following if you ARE using a snapshot version. -->
<snapshotRepository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</snapshotRepository>
</distributionManagement>
Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu May 29 17:06:53 CEST 2008
[INFO] Final Memory: 10M/139M
[INFO] ------------------------------------------------------------------------
~Jakub
>
> Cheers,
> Martin
>
>
> >
> > 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
>