Yes - these docs says you can do "mvn clean verify" but that was not the case
for the Pr.
So that is why I'm asking - why didn't mvn clean verify work ? Incomplete PR or
outofdate docs ?
On 19 Feb 2016, at 06:28, Nick Boldt <nboldt(a)redhat.com>
Verifying local changes to repo references to ensure IU versions are
On Fri, Feb 19, 2016 at 12:24 AM, Max Rydahl Andersen
> Adding back the list.
>> I suspect you were in the wrong folder. When I build it, I only build
>> the multiple/pom.xml, not the unified one.
> Gotcha. My bad. I missed the cd. Been too long since I build the tp locally.
> Can you Remind me what is needed to build the full TP for these PRs ? i thought once
once could build these with a mvn verify.
>> On Thu, Feb 18, 2016 at 5:47 PM, Max Rydahl Andersen
>> <manderse(a)redhat.com> wrote:
>>> On 18 Feb 2016, at 20:07, Nick Boldt wrote:
>>>> Build target-platform:
>>>> $ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
>>>> $ git fetch origin pull/195/head && git checkout FETCH\_HEAD
>>>> $ mvn clean install
>>> I tried this and I got:
>>> [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts)
>>> @ jbdevstudio-unified ---
>>> [INFO] --- target-platform-validation-plugin:0.23.1:validate-target-platform
>>> (default) @ jbdevstudio-unified ---
>>> [INFO] Validating
>>> [INFO] Adding repository
>>> [INFO] Failed, see Error log below
>>> [ERROR] Validation found errors in 1 .target files:
>>> Could not resolve content of jbdevstudio-unified.target
>>> Known issue ?
>>> so in short, i'm all for getting the changes in but I cannot build any
>>> the suggested PR's
>>> so I can't verify them. :/
>>>> Then, to test the new "multiple" target platform against your
>>>> $ cd /path/to/your/jbosstools-component
>>>> $ mvn clean verify -Dtpc.version=4.52.0.CR1-SNAPSHOT
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio