You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by pa...@apache.org on 2018/10/08 12:39:07 UTC
svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Author: painter
Date: Mon Oct 8 12:39:07 2018
New Revision: 1843135
URL: http://svn.apache.org/viewvc?rev=1843135&view=rev
Log:
Backing out parent pom changes due to Jenkins build errors
Modified:
db/torque/torque4/trunk/pom.xml
Modified: db/torque/torque4/trunk/pom.xml
URL: http://svn.apache.org/viewvc/db/torque/torque4/trunk/pom.xml?rev=1843135&r1=1843134&r2=1843135&view=diff
==============================================================================
--- db/torque/torque4/trunk/pom.xml (original)
+++ db/torque/torque4/trunk/pom.xml Mon Oct 8 12:39:07 2018
@@ -389,7 +389,7 @@
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-all</artifactId>
- <version>1.10.19</version>
+ <version>1.9.0</version>
<scope>test</scope>
</dependency>
@@ -434,7 +434,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
- <version>2.10</version>
+ <version>2.9</version>
<configuration>
<workspace>..</workspace>
<downloadSources>true</downloadSources>
@@ -532,7 +532,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
- <version>3.10.0</version>
+ <version>3.2</version>
<configuration>
<linkXref>true</linkXref>
<targetJdk>${maven.compiler.source}</targetJdk>
@@ -541,7 +541,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jxr-plugin</artifactId>
- <version>3.0.0</version>
+ <version>2.5</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
@@ -551,17 +551,17 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
- <version>3.0.0</version>
+ <version>2.13</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>xml-maven-plugin</artifactId>
- <version>1.0.2</version>
+ <version>1.0</version>
</plugin>
<plugin>
<groupId>org.owasp</groupId>
<artifactId>dependency-check-maven</artifactId>
- <version>3.3.2</version>
+ <version>3.1.2</version>
</plugin>
</plugins>
</pluginManagement>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Posted by Jeffery Painter <je...@jivecast.com>.
Reverse that... torque-4.1 is still referencing the older fulcrum
components. We probably want to release the updated fulcrum components
that torque relies on first, then do a torque-4.1 release, then update
fulcrum/security to take advantage of the latest version of torque :-)
-
Jeff
On 10/09/2018 12:33 PM, Jeffery Painter wrote:
> Hi Thomas,
>
> I didn't spend much more time on it, but I think there may have been
> some issues when updating fulcrum components to use mockito 2.22 and
> torque was still using an older version... but who knows, I will dig in
> soon and do as you suggest :-)
>
> -
> Jeff
>
>
> On 10/09/2018 12:30 PM, Thomas Vandahl wrote:
>> Hi Jeff,
>>
>> On 08.10.18 14:42, Jeffery Painter wrote:
>>> I am not sure why those changes failed in Jenkins... everything looked
>>> fine on my end. There were some complaints about some of the Java8
>>> updates after making the dependency updates in the jenkins log file, but
>>> nothing that looked fatal to me.
>> There are a couple of cases where Jenkins does things differently. I had
>> to exclude two tests in the generator which passed locally and failed on
>> Jenkins. The tremendous amount of log output is related to the fact that
>> Cobertura doesn't know about Java8 syntax, however.
>>
>>> I have reverted changes just on the parent pom and see if Jenkins
>>> complains again. Is there a way for me to test the jenkins build params
>>> locally before pushing code to the repo?
>> I'd suggest to change the dependencies one by one, commit and see how it
>> goes. You should be able to log into Jenkins with your Apache
>> credentials and do some research on the build details.
>>
>> Bye, Thomas
>>
>
--
Jeff Painter
CEO and Founder of JiveCast
Software and analytics, made together
https://jivecast.com
301 Fayetteville St. Unit 2301, Raleigh, NC 27601
(919) 533-9024
Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Posted by Jeffery Painter <je...@jivecast.com>.
Reverse that... torque-4.1 is still referencing the older fulcrum
components. We probably want to release the updated fulcrum components
that torque relies on first, then do a torque-4.1 release, then update
fulcrum/security to take advantage of the latest version of torque :-)
-
Jeff
On 10/09/2018 12:33 PM, Jeffery Painter wrote:
> Hi Thomas,
>
> I didn't spend much more time on it, but I think there may have been
> some issues when updating fulcrum components to use mockito 2.22 and
> torque was still using an older version... but who knows, I will dig in
> soon and do as you suggest :-)
>
> -
> Jeff
>
>
> On 10/09/2018 12:30 PM, Thomas Vandahl wrote:
>> Hi Jeff,
>>
>> On 08.10.18 14:42, Jeffery Painter wrote:
>>> I am not sure why those changes failed in Jenkins... everything looked
>>> fine on my end. There were some complaints about some of the Java8
>>> updates after making the dependency updates in the jenkins log file, but
>>> nothing that looked fatal to me.
>> There are a couple of cases where Jenkins does things differently. I had
>> to exclude two tests in the generator which passed locally and failed on
>> Jenkins. The tremendous amount of log output is related to the fact that
>> Cobertura doesn't know about Java8 syntax, however.
>>
>>> I have reverted changes just on the parent pom and see if Jenkins
>>> complains again. Is there a way for me to test the jenkins build params
>>> locally before pushing code to the repo?
>> I'd suggest to change the dependencies one by one, commit and see how it
>> goes. You should be able to log into Jenkins with your Apache
>> credentials and do some research on the build details.
>>
>> Bye, Thomas
>>
>
--
Jeff Painter
CEO and Founder of JiveCast
Software and analytics, made together
https://jivecast.com
301 Fayetteville St. Unit 2301, Raleigh, NC 27601
(919) 533-9024
Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Posted by Jeffery Painter <je...@jivecast.com>.
Hi Thomas,
I didn't spend much more time on it, but I think there may have been
some issues when updating fulcrum components to use mockito 2.22 and
torque was still using an older version... but who knows, I will dig in
soon and do as you suggest :-)
-
Jeff
On 10/09/2018 12:30 PM, Thomas Vandahl wrote:
> Hi Jeff,
>
> On 08.10.18 14:42, Jeffery Painter wrote:
>> I am not sure why those changes failed in Jenkins... everything looked
>> fine on my end. There were some complaints about some of the Java8
>> updates after making the dependency updates in the jenkins log file, but
>> nothing that looked fatal to me.
> There are a couple of cases where Jenkins does things differently. I had
> to exclude two tests in the generator which passed locally and failed on
> Jenkins. The tremendous amount of log output is related to the fact that
> Cobertura doesn't know about Java8 syntax, however.
>
>> I have reverted changes just on the parent pom and see if Jenkins
>> complains again. Is there a way for me to test the jenkins build params
>> locally before pushing code to the repo?
> I'd suggest to change the dependencies one by one, commit and see how it
> goes. You should be able to log into Jenkins with your Apache
> credentials and do some research on the build details.
>
> Bye, Thomas
>
Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Jeff,
On 08.10.18 14:42, Jeffery Painter wrote:
> I am not sure why those changes failed in Jenkins... everything looked
> fine on my end. There were some complaints about some of the Java8
> updates after making the dependency updates in the jenkins log file, but
> nothing that looked fatal to me.
There are a couple of cases where Jenkins does things differently. I had
to exclude two tests in the generator which passed locally and failed on
Jenkins. The tremendous amount of log output is related to the fact that
Cobertura doesn't know about Java8 syntax, however.
> I have reverted changes just on the parent pom and see if Jenkins
> complains again. Is there a way for me to test the jenkins build params
> locally before pushing code to the repo?
I'd suggest to change the dependencies one by one, commit and see how it
goes. You should be able to log into Jenkins with your Apache
credentials and do some research on the build details.
Bye, Thomas
Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml
Posted by Jeffery Painter <je...@jivecast.com>.
Hi Thomas,
I am not sure why those changes failed in Jenkins... everything looked
fine on my end. There were some complaints about some of the Java8
updates after making the dependency updates in the jenkins log file, but
nothing that looked fatal to me.
I have reverted changes just on the parent pom and see if Jenkins
complains again. Is there a way for me to test the jenkins build params
locally before pushing code to the repo?
-
Jeff
On 10/08/2018 08:39 AM, painter@apache.org wrote:
> Author: painter
> Date: Mon Oct 8 12:39:07 2018
> New Revision: 1843135
>
> URL: http://svn.apache.org/viewvc?rev=1843135&view=rev
> Log:
> Backing out parent pom changes due to Jenkins build errors
>
> Modified:
> db/torque/torque4/trunk/pom.xml
>
> Modified: db/torque/torque4/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/db/torque/torque4/trunk/pom.xml?rev=1843135&r1=1843134&r2=1843135&view=diff
> ==============================================================================
> --- db/torque/torque4/trunk/pom.xml (original)
> +++ db/torque/torque4/trunk/pom.xml Mon Oct 8 12:39:07 2018
> @@ -389,7 +389,7 @@
> <dependency>
> <groupId>org.mockito</groupId>
> <artifactId>mockito-all</artifactId>
> - <version>1.10.19</version>
> + <version>1.9.0</version>
> <scope>test</scope>
> </dependency>
>
> @@ -434,7 +434,7 @@
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> - <version>2.10</version>
> + <version>2.9</version>
> <configuration>
> <workspace>..</workspace>
> <downloadSources>true</downloadSources>
> @@ -532,7 +532,7 @@
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-pmd-plugin</artifactId>
> - <version>3.10.0</version>
> + <version>3.2</version>
> <configuration>
> <linkXref>true</linkXref>
> <targetJdk>${maven.compiler.source}</targetJdk>
> @@ -541,7 +541,7 @@
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jxr-plugin</artifactId>
> - <version>3.0.0</version>
> + <version>2.5</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> @@ -551,17 +551,17 @@
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> - <version>3.0.0</version>
> + <version>2.13</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>xml-maven-plugin</artifactId>
> - <version>1.0.2</version>
> + <version>1.0</version>
> </plugin>
> <plugin>
> <groupId>org.owasp</groupId>
> <artifactId>dependency-check-maven</artifactId>
> - <version>3.3.2</version>
> + <version>3.1.2</version>
> </plugin>
> </plugins>
> </pluginManagement>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>