dev@jersey.java.net

Re: Jersey 0.6 release

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Tue, 22 Apr 2008 14:22:24 +0200

I completely forgot... there is also a pom.xml in the jersey/maven
directory.

It defers to the ant build.xml for the clean, compile, package and
install phases, which is great.

I think we should try and do as much as possible in maven and only
defer to ant for otherwise tricky things or as a temporary/transitory
solution.

Paul.

On Apr 22, 2008, at 1:45 PM, Paul Sandoz wrote:

> Hi Doug,
>
> I have been playing around with the pom.xml.
>
> I needed to add a new plugin repository to
> "respository.codehaus.org" to pick up the FindBugs plugin.
>
> Then we i do "mvn install" it cannot find the artifacts:
>
> - com.sun.net.httpserver:httpserver:jar:1.5
>
> - com.sun.xml.wsLjaxws-tools:jar:2.1
>
> - javax.persistence:persistence-api:jar:1.0.2
>
> Did you install these manually? or is there a configuration setup
> to get these from the jersey/lib directory as declared by the
> <systemPath> element?
>
> Thanks,
> Paul.
>
>
> On Apr 4, 2008, at 11:27 PM, Doug Kohlert wrote:
>
>> Paul,
>> I just committed a maven2 pom.xml. It isn't perfect but it is a
>> good start.
>>
>> Currently, there are test failures so the jersey.jar file is not
>> created. The tests errors need to be resolved or comment out the
>> <testSourceDirectory> in the pom.xml to get the jersey.jar file
>> generated.
>>
>> I commented out the FindBugs plugin as it is causing a OutofMemory
>> error.
>>
>> Let me know if you have any questions.
>>
>> >>> Paul Sandoz <Paul.Sandoz_at_Sun.COM> 4/1/2008 1:58 AM >>>
>> Doug Kohlert wrote:
>> > Thanks Paul,
>> > Is there any plan to put it into a Maven 2 repository?
>>
>> Not yet. I presume when/if we switch to a maven 2 build process we
>> would
>> push to the maven 2 repo. Currently we don't have the resources to
>> switch to maven 2 so i am looking for any volunteers to help out :-)
>>
>> Paul.
>>
>> --
>> | ? + ? = To question
>> ----------------\
>> Paul Sandoz
>> x38109
>> +33-4-76188109
>> NOTICE: This email message is for the sole use of the intended
>> recipient(s) and may contain confidential and privileged
>> information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient,
>> please contact the sender by reply email and destroy all copies of
>> the original message.
>