[VOTE] Release JXPath 1.3 based on RC4

[Matt Benson]

Thanks to anyone who reported/resolved issues with the
previous release candidates.

The artifacts are here:
http://people.apache.org/~mbenson/jxpath-1.3-rc4/

The tag is here:
http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/

Site:
http://people.apache.org/~mbenson/jxpath-1.3-rc4/site

Clirr Report (compared to 1.2; one-shot not working w/
M2)
http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt

Thanks in advance to whomever can take the time to
check and vote on the artifacts.  This vote will be
open through Thursday, July 10 (I do these long votes
because I'm too slow to act any faster myself anyway).

Thanks,
Matt




     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Oliver Heger-3]

Everything looks fine, but a mvn site:site fails for me with the error
message "Embedded error: conf\findbugs-exclude-filter.xml (File cannot
be found.)" This file seems to be missing in the source distribution
(there is no conf directory at all).

Oliver

Matt Benson schrieb:

> Thanks to anyone who reported/resolved issues with the
> previous release candidates.
>
> The artifacts are here:
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/
>
> The tag is here:
> http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/
>
> Site:
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/site
>
> Clirr Report (compared to 1.2; one-shot not working w/
> M2)
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt
>
> Thanks in advance to whomever can take the time to
> check and vote on the artifacts.  This vote will be
> open through Thursday, July 10 (I do these long votes
> because I'm too slow to act any faster myself anyway).
>
> Thanks,
> Matt
>
>
>
>
>      
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[sebb-2-2]

Hashes sigs look fine

There is an extraneous 'options' file in the apidocs directory and the
javadoc jar.

The Manifest files in the source and javadoc jars don't contain anything useful.
I expect this is a Maven feature, but that does not mean that it is correct ;-)
I think the manifests should contain the following:

Built-By: mbenson
Build-Jdk: 1.5.0_13
Implementation-Title: Commons JXPath
Implementation-Vendor: The Apache Software Foundation
Implementation-Vendor-Id: org.apache
Implementation-Version: 1.3
Specification-Title: Commons JXPath
Specification-Vendor: The Apache Software Foundation
Specification-Version: 1.3

And perhaps:
X-Compile-Source-JDK: 1.3
X-Compile-Target-JDK: 1.3

On 05/07/2008, Oliver Heger <oliver.heger@...> wrote:

> Everything looks fine, but a mvn site:site fails for me with the error
> message "Embedded error: conf\findbugs-exclude-filter.xml
> (File cannot be found.)" This file seems to be missing in the source
> distribution (there is no conf directory at all).
>
>  Oliver
>
>  Matt Benson schrieb:
>
>
> > Thanks to anyone who reported/resolved issues with the
> > previous release candidates.
> >
> > The artifacts are here:
> > http://people.apache.org/~mbenson/jxpath-1.3-rc4/
> >
> > The tag is here:
> >
> http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/
> >
> > Site:
> > http://people.apache.org/~mbenson/jxpath-1.3-rc4/site
> >
> > Clirr Report (compared to 1.2; one-shot not working w/
> > M2)
> >
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt
> >
> > Thanks in advance to whomever can take the time to
> > check and vote on the artifacts.  This vote will be
> > open through Thursday, July 10 (I do these long votes
> > because I'm too slow to act any faster myself anyway).
> >
> > Thanks,
> > Matt
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>
>
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@...
>  For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jörg Schaible-2]

Hi Matt,

Builds from source and works fine on my compiler zoo except for all
IBM-JDKs, but that's a different story
(http://jira.codehaus.org/browse/MNG-3580).

Some minor issues though in the docs:

- download page goes nowhere, I suspect this is caused by the current
location and automatically fixed for the release
- the links to the older APIs does not work, again I suspect this is fixed
for the release
- the user's guide contains a table of content at its top. However, quite
all of the link anchors do not work

Issue in the POM:

- it defines a property "commons.release.version" with value 1.2. This is
used by the download-page-template.xml to generate the download page in
xdocs. Therefore currently all liks are generated for JXPath 1.2. Maybe the
property's value in the POM should be defined as ${project.version} in
general and its definition can move up to the parent-pom.
- it declares an optional provided dep to commons-logging, which is simply
not true, since jxpath does not make usage of commons-logging. However
commons-beanutils has it as transitive dep in an old version, therefore
commons-logging should be declared in a dependencyManagement with version
1.1.1 to overwrite the old transitive version
- it declares an optional runtime dep to commons-collection, but it is not
used by any other dependency and can therefore removed completely (all
tests run fine without it)
- I don't under stand why deps are declared with scope provided *and*
optional. IMHO provided is enough, but it may have also effect on the
generated dependencies page

Wiki:

- talks about release plan for 1.2 ;-)


Summary:
-1, simply because of the wrong download links, anything else is not
critical

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jörg Schaible-2]

Forgot to add the path for the POM, just in case you will do another RC.

Jörg Schaible wrote:

> Hi Matt,
>
> Builds from source and works fine on my compiler zoo except for all
> IBM-JDKs, but that's a different story
> (http://jira.codehaus.org/browse/MNG-3580).
>
> Some minor issues though in the docs:
>
> - download page goes nowhere, I suspect this is caused by the current
> location and automatically fixed for the release
> - the links to the older APIs does not work, again I suspect this is fixed
> for the release
> - the user's guide contains a table of content at its top. However, quite
> all of the link anchors do not work
>
> Issue in the POM:
>
> - it defines a property "commons.release.version" with value 1.2. This is
> used by the download-page-template.xml to generate the download page in
> xdocs. Therefore currently all liks are generated for JXPath 1.2. Maybe
> the property's value in the POM should be defined as ${project.version} in
> general and its definition can move up to the parent-pom.
> - it declares an optional provided dep to commons-logging, which is simply
> not true, since jxpath does not make usage of commons-logging. However
> commons-beanutils has it as transitive dep in an old version, therefore
> commons-logging should be declared in a dependencyManagement with version
> 1.1.1 to overwrite the old transitive version
> - it declares an optional runtime dep to commons-collection, but it is not
> used by any other dependency and can therefore removed completely (all
> tests run fine without it)
> - I don't under stand why deps are declared with scope provided *and*
> optional. IMHO provided is enough, but it may have also effect on the
> generated dependencies page
>
> Wiki:
>
> - talks about release plan for 1.2 ;-)
>
>
> Summary:
> -1, simply because of the wrong download links, anything else is not
> critical
>
> - Jörg

[pom.patch]

---

Index: pom.xml
===================================================================
--- pom.xml (Revision 674189)
+++ pom.xml (Arbeitskopie)
@@ -62,7 +62,7 @@
 
   <properties>
     <commons.componentid>jxpath</commons.componentid>
-    <commons.release.version>1.2</commons.release.version>
+    <commons.release.version>{project.version}</commons.release.version>
     <commons.binary.suffix />
     <commons.jira.id>JXPATH</commons.jira.id>
     <commons.jira.pid>12310480</commons.jira.pid>
@@ -100,18 +100,21 @@
       </plugin>
     </plugins>
   </build>
+  <dependencyManagement>
+    <dependencies>
+      <dependency>
+        <groupId>commons-logging</groupId>
+        <artifactId>commons-logging</artifactId>
+        <version>1.1.1</version>
+      </dependency>
+    </dependencies>
+  </dependencyManagement>
   <dependencies>
     <dependency>
-      <groupId>commons-logging</groupId>
-      <artifactId>commons-logging</artifactId>
-      <version>1.1.1</version>
-      <optional>true</optional>
-      <scope>runtime</scope>
-    </dependency>
-    <dependency>
       <groupId>xerces</groupId>
       <artifactId>xercesImpl</artifactId>
       <version>2.4.0</version>
+      <scope>provided</scope>
       <optional>true</optional>
     </dependency>
     <dependency>
@@ -154,13 +157,6 @@
       <optional>true</optional>
     </dependency>
     <dependency>
-      <groupId>commons-collections</groupId>
-      <artifactId>commons-collections</artifactId>
-      <version>3.2</version>
-      <optional>true</optional>
-      <scope>runtime</scope>
-    </dependency>
-    <dependency>
       <groupId>com.mockrunner</groupId>
       <artifactId>mockrunner-jdk1.3-j2ee1.3</artifactId>
       <version>0.4</version>

---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Rahul Akolkar]

On 7/5/08, Jörg Schaible <joerg.schaible@...> wrote:
<snip/>
>
>  Issue in the POM:
>
>  - it defines a property "commons.release.version" with value 1.2. This is
>  used by the download-page-template.xml to generate the download page in
>  xdocs. Therefore currently all liks are generated for JXPath 1.2. Maybe the
>  property's value in the POM should be defined as ${project.version} in
>  general and its definition can move up to the parent-pom.
<snap/>

It can't be ${project.version} since that will break the download page
when the version rolls (such as on to the next snap when 1.3 is
released). So a separate property is used.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[sebb-2-2]

On 05/07/2008, Rahul Akolkar <rahul.akolkar@...> wrote:

> On 7/5/08, Jörg Schaible <joerg.schaible@...> wrote:
>  <snip/>
>
> >
>  >  Issue in the POM:
>  >
>  >  - it defines a property "commons.release.version" with value 1.2. This is
>  >  used by the download-page-template.xml to generate the download page in
>  >  xdocs. Therefore currently all liks are generated for JXPath 1.2. Maybe the
>  >  property's value in the POM should be defined as ${project.version} in
>  >  general and its definition can move up to the parent-pom.
>
> <snap/>
>
>  It can't be ${project.version} since that will break the download page
>  when the version rolls (such as on to the next snap when 1.3 is
>  released). So a separate property is used.

In which case, it might be sensible to add comments to the pom to say
that the two values need to be in agreement for releases. Maybe move
them close together as well.

>
>  -Rahul
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@...
>  For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Matt Benson]

--- Jörg Schaible <joerg.schaible@...> wrote:

> Forgot to add the path for the POM, just in case you
> will do another RC.
>

So... can you explain again what is the effect of
moving [logging] to the separate dependencyManagement
section of the POM?

Thanks,
Matt

> Jörg Schaible wrote:
>
> > Hi Matt,
> >
> > Builds from source and works fine on my compiler
> zoo except for all
> > IBM-JDKs, but that's a different story
> > (http://jira.codehaus.org/browse/MNG-3580).
> >
> > Some minor issues though in the docs:
> >
> > - download page goes nowhere, I suspect this is
> caused by the current
> > location and automatically fixed for the release
> > - the links to the older APIs does not work, again
> I suspect this is fixed
> > for the release
> > - the user's guide contains a table of content at
> its top. However, quite
> > all of the link anchors do not work
> >
> > Issue in the POM:
> >
> > - it defines a property "commons.release.version"
> with value 1.2. This is
> > used by the download-page-template.xml to generate
> the download page in
> > xdocs. Therefore currently all liks are generated
> for JXPath 1.2. Maybe
> > the property's value in the POM should be defined
> as ${project.version} in
> > general and its definition can move up to the
> parent-pom.
> > - it declares an optional provided dep to
> commons-logging, which is simply
> > not true, since jxpath does not make usage of
> commons-logging. However
> > commons-beanutils has it as transitive dep in an
> old version, therefore
> > commons-logging should be declared in a
> dependencyManagement with version
> > 1.1.1 to overwrite the old transitive version
> > - it declares an optional runtime dep to
> commons-collection, but it is not
> > used by any other dependency and can therefore
> removed completely (all
> > tests run fine without it)
> > - I don't under stand why deps are declared with
> scope provided *and*
> > optional. IMHO provided is enough, but it may have
> also effect on the
> > generated dependencies page
> >
> > Wiki:
> >
> > - talks about release plan for 1.2 ;-)
> >
> >
> > Summary:
> > -1, simply because of the wrong download links,
> anything else is not
> > critical
> >
> > - Jörg
>
> > Index: pom.xml
>

===================================================================
> --- pom.xml (Revision 674189)
> +++ pom.xml (Arbeitskopie)
> @@ -62,7 +62,7 @@
>  
>    <properties>
>    
> <commons.componentid>jxpath</commons.componentid>
> -  
>
<commons.release.version>1.2</commons.release.version>
> +  
>
<commons.release.version>{project.version}</commons.release.version>

>      <commons.binary.suffix />
>      <commons.jira.id>JXPATH</commons.jira.id>
>      <commons.jira.pid>12310480</commons.jira.pid>
> @@ -100,18 +100,21 @@
>        </plugin>
>      </plugins>
>    </build>
> +  <dependencyManagement>
> +    <dependencies>
> +      <dependency>
> +        <groupId>commons-logging</groupId>
> +        <artifactId>commons-logging</artifactId>
> +        <version>1.1.1</version>
> +      </dependency>
> +    </dependencies>
> +  </dependencyManagement>
>    <dependencies>
>      <dependency>
> -      <groupId>commons-logging</groupId>
> -      <artifactId>commons-logging</artifactId>
> -      <version>1.1.1</version>
> -      <optional>true</optional>
> -      <scope>runtime</scope>
> -    </dependency>
> -    <dependency>
>        <groupId>xerces</groupId>
>        <artifactId>xercesImpl</artifactId>
>        <version>2.4.0</version>
> +      <scope>provided</scope>
>        <optional>true</optional>
>      </dependency>
>      <dependency>
> @@ -154,13 +157,6 @@
>        <optional>true</optional>
>      </dependency>
>      <dependency>
> -      <groupId>commons-collections</groupId>
> -      <artifactId>commons-collections</artifactId>
> -      <version>3.2</version>
> -      <optional>true</optional>
> -      <scope>runtime</scope>
> -    </dependency>
> -    <dependency>
>        <groupId>com.mockrunner</groupId>
>      
> <artifactId>mockrunner-jdk1.3-j2ee1.3</artifactId>
>        <version>0.4</version>
>
>
> >

---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@...
> For additional commands, e-mail:
dev-help@...



     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Matt Benson]

--- sebb <sebbaz@...> wrote:

> Hashes sigs look fine
>
> There is an extraneous 'options' file in the apidocs
> directory and the
> javadoc jar.
>

Noted; will investigate.

> The Manifest files in the source and javadoc jars
> don't contain anything useful.
> I expect this is a Maven feature, but that does not
> mean that it is correct ;-)
> I think the manifests should contain the following:
>
> Built-By: mbenson
> Build-Jdk: 1.5.0_13
> Implementation-Title: Commons JXPath
> Implementation-Vendor: The Apache Software
> Foundation
> Implementation-Vendor-Id: org.apache
> Implementation-Version: 1.3
> Specification-Title: Commons JXPath
> Specification-Vendor: The Apache Software Foundation
> Specification-Version: 1.3
>
> And perhaps:
> X-Compile-Source-JDK: 1.3
> X-Compile-Target-JDK: 1.3
>

Anyone have any idea how to accomplish these in mvn?

-Matt

> On 05/07/2008, Oliver Heger
> <oliver.heger@...> wrote:
> > Everything looks fine, but a mvn site:site fails
> for me with the error
> > message "Embedded error:
> conf\findbugs-exclude-filter.xml
> > (File cannot be found.)" This file seems to be
> missing in the source
> > distribution (there is no conf directory at all).
> >
> >  Oliver
> >
> >  Matt Benson schrieb:
> >
> >
> > > Thanks to anyone who reported/resolved issues
> with the
> > > previous release candidates.
> > >
> > > The artifacts are here:
> > >
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/
> > >
> > > The tag is here:
> > >
> >
>

http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/
> > >
> > > Site:
> > >
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/site
> > >
> > > Clirr Report (compared to 1.2; one-shot not
> working w/
> > > M2)
> > >
> >
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt

> > >
> > > Thanks in advance to whomever can take the time
> to
> > > check and vote on the artifacts.  This vote will
> be
> > > open through Thursday, July 10 (I do these long
> votes
> > > because I'm too slow to act any faster myself
> anyway).
> > >
> > > Thanks,
> > > Matt
> > >
> > >
> > >
> > >
> > >
> > >
> >
>

---------------------------------------------------------------------

> > > To unsubscribe, e-mail:
> > dev-unsubscribe@...
> > > For additional commands, e-mail:
> dev-help@...
> > >
> > >
> >
> >
> >
>

---------------------------------------------------------------------
> >  To unsubscribe, e-mail:
> dev-unsubscribe@...
> >  For additional commands, e-mail:
> dev-help@...
> >
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@...
> For additional commands, e-mail:
> dev-help@...
>
>



     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jörg Schaible-2]

Hi Matt,

Matt Benson wrote:

>
> --- Jörg Schaible <joerg.schaible@...> wrote:
>
>> Forgot to add the path for the POM, just in case you
>> will do another RC.
>>
>
> So... can you explain again what is the effect of
> moving [logging] to the separate dependencyManagement
> section of the POM?

jxpath does not use logging, it's a dep of beanutils. Therefore it should
not even be declared as (optional) runtime dep, because if somebody uses
(optional) beanutils, it's part of the dependency list anyway. However,
beanutils uses still 1.0.3 and with the dependencyManagement you can
overwrite the version of the transitive dependency:

joehni@paddy ~/src/Commons/proper/jxpath $ mvn dependency:tree
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Commons JXPath
[INFO]    task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree]
[INFO] commons-jxpath:commons-jxpath:jar:1.3-SNAPSHOT
[INFO] +- xerces:xercesImpl:jar:2.4.0:provided
[INFO] +- javax.servlet:servlet-api:jar:2.4:provided
[INFO] +- javax.servlet:jsp-api:jar:2.0:provided
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- xml-apis:xml-apis:jar:1.3.04:provided
[INFO] +- jdom:jdom:jar:1.0:compile
[INFO] +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
[INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile (version
managed from 1.0.3)
[INFO] \- com.mockrunner:mockrunner-jdk1.3-j2ee1.3:jar:0.4:test
[INFO]    \- org.mockejb:mockejb:jar:0.6-beta2:test
[INFO]       \- cglib:cglib-full:jar:2.0.2:test
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21 seconds
[INFO] Finished at: Sat Jul 05 17:01:51 CEST 2008
[INFO] Final Memory: 10M/20M
[INFO] ------------------------------------------------------------------------

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

On Sat, 2008-07-05 at 17:04 +0200, Jörg Schaible wrote:

> Hi Matt,
>
> Matt Benson wrote:
>
> >
> > --- Jörg Schaible <joerg.schaible@...> wrote:
> >
> >> Forgot to add the path for the POM, just in case you
> >> will do another RC.
> >>
> >
> > So... can you explain again what is the effect of
> > moving [logging] to the separate dependencyManagement
> > section of the POM?
>
> jxpath does not use logging, it's a dep of beanutils. Therefore it should
> not even be declared as (optional) runtime dep, because if somebody uses
> (optional) beanutils, it's part of the dependency list anyway. However,
> beanutils uses still 1.0.3 and with the dependencyManagement you can
> overwrite the version of the transitive dependency:
>
> joehni@paddy ~/src/Commons/proper/jxpath $ mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Commons JXPath
> [INFO]    task-segment: [dependency:tree]
> [INFO] ------------------------------------------------------------------------
> [INFO] [dependency:tree]
> [INFO] commons-jxpath:commons-jxpath:jar:1.3-SNAPSHOT
> [INFO] +- xerces:xercesImpl:jar:2.4.0:provided
> [INFO] +- javax.servlet:servlet-api:jar:2.4:provided
> [INFO] +- javax.servlet:jsp-api:jar:2.0:provided
> [INFO] +- junit:junit:jar:3.8.1:test
> [INFO] +- xml-apis:xml-apis:jar:1.3.04:provided
> [INFO] +- jdom:jdom:jar:1.0:compile
> [INFO] +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile (version
> managed from 1.0.3)
> [INFO] \- com.mockrunner:mockrunner-jdk1.3-j2ee1.3:jar:0.4:test
> [INFO]    \- org.mockejb:mockejb:jar:0.6-beta2:test
> [INFO]       \- cglib:cglib-full:jar:2.0.2:test
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Sat Jul 05 17:01:51 CEST 2008
> [INFO] Final Memory: 10M/20M
> [INFO] ------------------------------------------------------------------------
>

+1.

If jxpath doesn't use logging directly, but does via another optional
dependency then using dependencyManagement looks to be the right option
to set.

This isn't release critical IMO, because users can always override the
logging version themselves, but bumping the version to 1.1.1 by default
seems like a nice helpful thing to do.

Cheers, Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Matt Benson]

--- Jörg Schaible <joerg.schaible@...> wrote:

> Hi Matt,
>
> Builds from source and works fine on my compiler zoo
> except for all
> IBM-JDKs, but that's a different story
> (http://jira.codehaus.org/browse/MNG-3580).
>
> Some minor issues though in the docs:
>
> - download page goes nowhere, I suspect this is
> caused by the current
> location and automatically fixed for the release

Correct; it's a relative path assuming that the site
is installed at http://commons.apache.org/jxpath.

> - the links to the older APIs does not work, again I
> suspect this is fixed
> for the release

Correct again.

> - the user's guide contains a table of content at
> its top. However, quite
> all of the link anchors do not work

Fixed.

>
> Issue in the POM:

Addressed as discussed elsewhere.

[SNIP]
>
> Wiki:
>
> - talks about release plan for 1.2 ;-)
>

mmm... Being that I'm already in the process of
releasing 1.3, it seems a little too late to come up
with a release plan.  Should a release plan be
obliterated from the Wiki once the release has taken
place?

>
> Summary:
> -1, simply because of the wrong download links,
> anything else is not
> critical

Since you called that a -1, despite acknowledging that
it probably wasn't a problem on the deployed site, I'm
not sure where that leaves this issue.  I'm cutting a
new RC, but the download link will still lead nowhere
unless we change the way the site is built--the M1
navigation.xml as well as the M2 src/site.xml actually
list all these links explicitly including
"commons.apache.org" but that is apparently stripped
out as the site is built.

-Matt

>
> - Jörg
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@...
> For additional commands, e-mail:
> dev-help@...
>
>



     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Matt Benson]

Officially cancelling this vote, blah blah...

--- Matt Benson <gudnabrsam@...> wrote:

> Thanks to anyone who reported/resolved issues with
> the
> previous release candidates.
>
> The artifacts are here:
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/
>
> The tag is here:
>
http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/
>
> Site:
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/site
>
> Clirr Report (compared to 1.2; one-shot not working
> w/
> M2)
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt

>
> Thanks in advance to whomever can take the time to
> check and vote on the artifacts.  This vote will be
> open through Thursday, July 10 (I do these long
> votes
> because I'm too slow to act any faster myself
> anyway).
>
> Thanks,
> Matt
>
>
>
>
>      
>
>

---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@...
> For additional commands, e-mail:
> dev-help@...
>
>



     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Matt Benson]

--- sebb <sebbaz@...> wrote:

> Hashes sigs look fine
>
> There is an extraneous 'options' file in the apidocs
> directory and the
> javadoc jar.
>

This is caused by the javadoc plugin, apparently.  The
options file appears to be something that specifying
<debug>true</debug> in the plugin's configuration will
cause _not_ to be deleted at the end of the plugin's
having completed its tasks.  Unfortunately, "debug" is
not specified to true that I can see, and I have tried
to the best of my ability to declare it as false in a
vain attempt to remove this options file, which I'm
not terribly eager to have go out in releases
either--thanks for catching it, Sebastian.

Any Maven-knowledgeable folks want to tell me what I'm
doing wrong lest I spout Maven slander as I typically
tend to do?  (...not that I recall ever having had to
eat my own words in that regard...)

> The Manifest files in the source and javadoc jars
> don't contain anything useful.
> I expect this is a Maven feature, but that does not
> mean that it is correct ;-)
> I think the manifests should contain the following:

Once again, no idea how to do this either.

-Matt

>
> Built-By: mbenson
> Build-Jdk: 1.5.0_13
> Implementation-Title: Commons JXPath
> Implementation-Vendor: The Apache Software
> Foundation
> Implementation-Vendor-Id: org.apache
> Implementation-Version: 1.3
> Specification-Title: Commons JXPath
> Specification-Vendor: The Apache Software Foundation
> Specification-Version: 1.3
>
> And perhaps:
> X-Compile-Source-JDK: 1.3
> X-Compile-Target-JDK: 1.3
>
> On 05/07/2008, Oliver Heger
> <oliver.heger@...> wrote:
> > Everything looks fine, but a mvn site:site fails
> for me with the error
> > message "Embedded error:
> conf\findbugs-exclude-filter.xml
> > (File cannot be found.)" This file seems to be
> missing in the source
> > distribution (there is no conf directory at all).
> >
> >  Oliver
> >
> >  Matt Benson schrieb:
> >
> >
> > > Thanks to anyone who reported/resolved issues
> with the
> > > previous release candidates.
> > >
> > > The artifacts are here:
> > >
> http://people.apache.org/~mbenson/jxpath-1.3-rc4/
> > >
> > > The tag is here:
> > >
> >
>

http://svn.apache.org/viewvc/commons/proper/jxpath/tags/JXPATH_1_3_RC4/
> > >
> > > Site:
> > >
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/site
> > >
> > > Clirr Report (compared to 1.2; one-shot not
> working w/
> > > M2)
> > >
> >
>
http://people.apache.org/~mbenson/jxpath-1.3-rc4/clirr-report.txt

> > >
> > > Thanks in advance to whomever can take the time
> to
> > > check and vote on the artifacts.  This vote will
> be
> > > open through Thursday, July 10 (I do these long
> votes
> > > because I'm too slow to act any faster myself
> anyway).
> > >
> > > Thanks,
> > > Matt
> > >
> > >
> > >
> > >
> > >
> > >
> >
>

---------------------------------------------------------------------

> > > To unsubscribe, e-mail:
> > dev-unsubscribe@...
> > > For additional commands, e-mail:
> dev-help@...
> > >
> > >
> >
> >
> >
>

---------------------------------------------------------------------
> >  To unsubscribe, e-mail:
> dev-unsubscribe@...
> >  For additional commands, e-mail:
> dev-help@...
> >
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@...
> For additional commands, e-mail:
> dev-help@...
>
>



     

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...