Bug 988599 – Maven client's zanata.project parameter has no effect.

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 988599 - Maven client's zanata.project parameter has no effect.

Summary:	Maven client's zanata.project parameter has no effect.

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Zanata
Classification:	Community
Component:	Component-Maven (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Patrick Huang
QA Contact:	Zanata-QA Mailling List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-25 19:13 EDT by Carlos Munoz
Modified:	2015-07-28 22:48 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-07-28 22:48:04 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Carlos Munoz 2013-07-25 19:13:23 EDT

Description of problem:
The maven client's zanata.project parameter seems not to be parsed. Even when running 'mvn zanata:help -Ddetail -Dgoal=push', the option doesn't show up in the help text. Haven't tried other goals.

Version-Release number of selected component (if applicable):
3.0.0

How reproducible:
Always

Steps to Reproduce:
1. Push files to a project using the maven client's command line parameters only.
2. Make sure the -Dzanata.project=XXX argument is given.

Actual results:
The push fails stating that the project must be specified.

Expected results:
The push succeeds.

Comment 1 Zanata Migrator 2015-07-28 22:48:04 EDT

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-201

Note You need to log in before you can comment on or make changes to this bug.