Skip to Content.
Sympa Menu

perfsonar-dev - [pS-dev] [GEANT/SA2/ps-java-services] r6423 - in trunk: . perfsonar-java-rrd-ma-SQL_backend

Subject: perfsonar development work

List archive

[pS-dev] [GEANT/SA2/ps-java-services] r6423 - in trunk: . perfsonar-java-rrd-ma-SQL_backend


Chronological Thread 
  • From:
  • To:
  • Subject: [pS-dev] [GEANT/SA2/ps-java-services] r6423 - in trunk: . perfsonar-java-rrd-ma-SQL_backend
  • Date: Fri, 24 May 2013 20:33:52 +0100 (BST)
  • Authentication-results: sfpop-ironport02.merit.edu; dkim=neutral (message not signed) header.i=none

Author: dante.delvaux
Date: 2013-05-24 20:33:52 +0100 (Fri, 24 May 2013)
New Revision: 6423

Modified:
trunk/
trunk/BUILDING.txt
trunk/RELEASES.txt
trunk/perfsonar-java-rrd-ma-SQL_backend/pom.xml
Log:
RRD MA: correcting Debian package name and updating building and release
documentation.


Property changes on: trunk
___________________________________________________________________
Modified: svn:ignore
- .settings

.project

logs

+ .settings

.project

logs

jenkins-mvn-settings.xml


Modified: trunk/BUILDING.txt
===================================================================
--- trunk/BUILDING.txt 2013-05-23 15:40:53 UTC (rev 6422)
+++ trunk/BUILDING.txt 2013-05-24 19:33:52 UTC (rev 6423)
@@ -80,6 +80,20 @@

- Reporting configuration used to generate a Maven site report.

+- /common/ directory coming from the parent should also be 'svn:externals'
+ linked in the each sub-project. This directory holds common configuration
+ files that needs to be shared, having an 'svn:externals' reference allows
us
+ to have a single holding place for this and to use local reference to those
+ files in each pom (instead of path to the parents that are relative and
thus
+ different in each levels of sub-projects).
+
+Each sub-project can use a different version of the parent pom, the one it
needs
+to comply to. However, each project should tend to use the latest released
+version whenever possible. Take should alsa be taken to update the
+'svn:externals' reference to the common directory when a parent version is
+updated in one of the submodules (use a reference to the tag when using a
+released parent and a reference to the trunk when using the latest snapshot).
+
Note again that currently not all subproducts follow this structure, but any
new
one MUST follow it.


Modified: trunk/RELEASES.txt
===================================================================
--- trunk/RELEASES.txt 2013-05-23 15:40:53 UTC (rev 6422)
+++ trunk/RELEASES.txt 2013-05-24 19:33:52 UTC (rev 6423)
@@ -36,7 +36,8 @@
mvn versions:update-parent

- the svn:externals references to the parent common directory should
also be
- updated as to point to the newly created parent tag instead of the trunk.
+ updated as to point to the newly created parent tag (use the trunk only
when
+ referencing a parent snapshot)


With Jenkins

Modified: trunk/perfsonar-java-rrd-ma-SQL_backend/pom.xml
===================================================================
--- trunk/perfsonar-java-rrd-ma-SQL_backend/pom.xml 2013-05-23 15:40:53
UTC (rev 6422)
+++ trunk/perfsonar-java-rrd-ma-SQL_backend/pom.xml 2013-05-24 19:33:52
UTC (rev 6423)
@@ -242,6 +242,8 @@
<goal>jdeb</goal>
</goals>
<configuration>
+
<deb>[[buildDir]]/[[artifactId]]_[[version]]_all.[[extension]]</deb>
+ <timestamped>true</timestamped>
<dataSet>
<data>

<src>${project.build.directory}/${project.build.finalName}</src>



  • [pS-dev] [GEANT/SA2/ps-java-services] r6423 - in trunk: . perfsonar-java-rrd-ma-SQL_backend, svn-noreply, 05/24/2013

Archive powered by MHonArc 2.6.16.

Top of Page