Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
P
protobuf
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
protobuf
Commits
6396a47d
Commit
6396a47d
authored
Dec 04, 2019
by
Tomo Suzuki
Committed by
Rafi Kamal
Dec 04, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Simplifying linkage monitor test setup (#6855)
parent
ef210164
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
10 deletions
+0
-10
tests.sh
tests.sh
+0
-10
No files found.
tests.sh
View file @
6396a47d
...
...
@@ -251,16 +251,6 @@ build_java_linkage_monitor() {
# Linkage Monitor uses $HOME/.m2 local repository
MVN
=
"mvn -e -B -Dhttps.protocols=TLSv1.2"
cd
java
# Sets java artifact version with SNAPSHOT, as Linkage Monitor looks for SNAPSHOT versions.
# Example: "3.9.0" (without 'rc')
VERSION
=
`
grep
'<version>'
pom.xml |head
-1
|perl
-nle
'print $1 if m/<version>(\d+\.\d+.\d+)/'
`
cd
bom
# This local installation avoids the problem caused by a new version not yet in Maven Central
# https://github.com/protocolbuffers/protobuf/issues/6627
$MVN
install
$MVN
versions:set
-DnewVersion
=
${
VERSION
}
-SNAPSHOT
cd
..
$MVN
versions:set
-DnewVersion
=
${
VERSION
}
-SNAPSHOT
# Installs the snapshot version locally
$MVN
install
-Dmaven
.test.skip
=
true
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment