Hi Martin,
I think the 1st task should be to push Jersey snapshots to maven repository
(i.e. via mvn deploy)
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?
Apart from that, let me look at mavenizing the rest of examples.
I will let you know if i have issues with that.
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
>
>