It actually points at 3.2 snapshot in 40203.
On 6/21/11 5:26 PM, Jane Young wrote:
> 3.1 is already released/promoted. Why is the pom still referencing
> 3.1-SNAPSHOT?
> If you want to reference 3.2-SNAPSHOT, you should specify a repository
> element in the pom so build will not break w/o modifying the
> settings.xml. See more details here:
> http://knol.google.com/k/emerson-farrugia/declaring-repositories-in-snapshot/2u2m6rp0ot3oc/1#
>
> FYI: this is the issue that Bobby was encountering when building
> devtests.
>
> On 6/21/11 2:19 PM, Justin Lee wrote:
>> Since this code is intended to be run mostly against the trunk code,
>> using -SNAPSHOT makes perfect sense. Nothing in this tree gets
>> deployed to any public repos. The ultimate plan is to use maven to
>> able to pull in deps for these devtests and relying on the prior
>> major release to test current development is useless. IMO, this
>> change should be rolled back.
>>
>> On 6/21/11 5:06 PM, janey_at_java.net wrote:
>>> Project: glassfish
>>> Repository: svn
>>> Revision: 47603
>>> Author: janey
>>> Date: 2011-06-21 21:06:50 UTC
>>> Link:
>>>
>>> Log Message:
>>> ------------
>>> parent pom should be non-SNAPSHOT or define with relativePath.
>>>
>>>
>>>
>>>
>>> Revisions:
>>> ----------
>>> 47603
>>>
>>>
>>> Modified Paths:
>>> ---------------
>>> trunk/v2/appserv-tests/util/reportbuilder/pom.xml
>>>
>>>
>>> Diffs:
>>> ------
>>> Index: trunk/v2/appserv-tests/util/reportbuilder/pom.xml
>>> ===================================================================
>>> --- trunk/v2/appserv-tests/util/reportbuilder/pom.xml (revision
>>> 47602)
>>> +++ trunk/v2/appserv-tests/util/reportbuilder/pom.xml (revision
>>> 47603)
>>> @@ -46,7 +46,7 @@
>>> <parent>
>>> <groupId>org.glassfish</groupId>
>>> <artifactId>glassfish-parent</artifactId>
>>> -<version>3.1-SNAPSHOT</version>
>>> +<version>3.1</version>
>>> </parent>
>>> <modelVersion>4.0.0</modelVersion>
>>> <groupId>org.glassfish.devtests</groupId>
>>>
>>>
>>>
>