On Aug 6, 2009, at 4:19 PM, Robert Koberg wrote:
>
> On Aug 6, 2009, at 1:39 AM, Paul Sandoz wrote:
>
>>
>> On Aug 6, 2009, at 5:14 AM, Robert Koberg wrote:
>>
>>> Hi,
>>>
>>> Is there are an eclipse .classpath file floating around that has
>>> all of the
>>> $jersey/doc('.classpath'/)/classpath/classpathentry[@src]
>>> directories identified (for the trunk)?
>>>
>>
>> I do not have one. Nor do i think there should be a file that
>> globally references all source because Jersey is separated into
>> maven modules. Every time we refractor a module or add a new module
>> we would have to update this file.
>
> Oh, I wasn't asking for it to be in the distro. Just asking if
> somebody has already taken the time to drill into each directory and
> add the source directories and would like to share their .classpath
> file. If not, I will probably either do it by hand or write some
> kind of script.
>
OK.
> Is everyone using Netbeans here?
>
I think most Sun-based developers use NetBeans.
> I tried to instal m2eclipse maven plugin for eclipse, but could not
> get through the install process. I was able to install their
> development version (I am using eclipse 3.5 - Build id:
> 20090621-0832 on OS X). When I try to run maven against the root
> pom.xml (don't know if I using correct terminology), I get the
> following:
>
> [WARNING]
> [WARNING] Some problems were encountered while building the
> effective model for com.sun.jersey:jersey-project:pom:1.1.2-ea-
> SNAPSHOT
> [WARNING] Invalid POM com.sun.jersey:jersey-project:1.1.2-ea-
> SNAPSHOT (/Users/rkobergmac/Documents/workspace/jersey/jersey/
> pom.xml): 'build.plugins.plugin.version' is missing for
> org.codehaus.mojo:buildnumber-maven-plugin
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because
> they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions will no longer
> support building such malformed projects.
>
> I don't know if this is an issue or just something screwed up with
> my install.
>
Do you know what version of maven is being used?
The warning indicates that a version declaration is missing from the
main Jersey pom.xml file. I would presume since this is a warning that
it should not affect processing for the current version of maven you
are using.
Paul.