[jbosstools-dev] M1 Status Update - trunk and maintenance branch

Tue May 3 19:47:10 EDT 2011

Nick,

Your last commit broke trunk and brunch at the same time. First problem is

[sources] $ /qa/tools/opt/apache-maven-3.0.3/bin/mvn -f /home/hudson/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--portlet/build/parent/pom.xml "-DMAVEN_FLAGS=clean install -B -U -fae -e -Dmaven.repo.local=${WORKSPACE}/m2-repository -P helios-local-target,jbosstools-nightly-trunk,local.composite,hudson" clean install -B -U -fae -e -Dmaven.repo.local=/home/hudson/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--portlet/m2-repository -P helios-local-target,jbosstools-nightly-trunk,local.composite,hudson
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project ->  [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM /home/hudson/hudson_workspace/workspace/jbosstools-3.2_stable_branch.component--portlet/build/parent/pom.xml: Duplicated tag: 'configuration' (position: START_TAG seen ...l files to set \n\t\t\t\t\tthis for your plugins -->\n\t\t\t\t<configuration>... @202:20)  @ line 202, column 20
	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339)
	at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:632)

fixed in trunk and branch.

Second problem is maven-osgi-source-plugin enablement which leads to 
build failures for plug-ins without sources like smooks.runtime

[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-source-plugin:0.10.0:plugin-source (attach-source) on project org.jboss.tools.smooks.runtime: no source folders found in build.properties ->  [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-source-plugin:0.10.0:plugin-source (attach-source) on project org.jboss.tools.smooks.runtime: no source folders found in build.properties
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

I've removed thid plugin from trunk pom.xml because we're not going to 
have SDK's for 3.2.X releases.
It is commented in trunk, because it supposed to be here, but I don't 
think it is good time now.

Denis

On 05/01/2011 07:11 PM, Nick Boldt wrote:
> JBDS 4.1.0.M1 product builds (H358 or later) here:
>
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-4.1_stable_branch.product/updates/nightly/4.1.0.M1/
> (update site)
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-4.1_stable_branch.product/builds/nightly/4.1.0.M1/
> (installers)
>
> JBDS 4.1 Extras + Tech Preview sites:
>
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-4.1_stable_branch.updatesite/
>
> ----
>
> JBDS 5.0.0.M1 product builds are still broken due to missing SpringIDE
> dependencies [1] (we're moving up to 2.6 in 5.0 [2]).
>
> [1] https://issues.jboss.org/browse/JBDS-1639
> [2] https://issues.jboss.org/browse/JBDS-1594
>
> Nick
>
> On 05/01/2011 01:23 AM, Nick Boldt wrote:
>> In addition to the 3.2.1.M1 builds noted below, we now also have JBT
>> 3.3.0.M1 build H2175 (or newer) to smoke and QE.
>>
>> http://download.jboss.org/jbosstools/updates/nightly/trunk/
>> http://download.jboss.org/jbosstools/builds/nightly/trunk/latestBuild.html
>>
>> ---
>>
>> JBDS product builds are still broken due to their dependence on updated
>> versions of org.eclipse.releng.basebuilder, which I've now pushed to
>> download.jboss.org and have updated the config files used by PDE-based
>> product build. JBDS 5 was also broken due to jpt.feature being
>> refactored to jpt.jpa.feature upstream but not (yet) changed in
>> com.jboss.jbds.product.feature. That should be fixed now too.
>>
>> ---
>>
>> Respinning here:
>>
>> http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/devstudio-4.1_stable_branch.product/355/
>>
>>
>> http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/devstudio-5.0_trunk.updatesite/861/
>> (then downstream .project job #482)
>>
>> Results will be here (in .product folders), once the jobs are blue:
>>
>> http://www.qa.jboss.com/binaries/RHDS/builds/staging/
>> (look for 4.1 build H355 or later&  5.0 build 482 or later)
>>
>> Cheers,
>>
>> Nick
>>
>> On 04/29/2011 04:51 PM, Brian Fitzpatrick wrote:
>>> Thanks for the updates on 3.2.1 M1 jobs and I guess with the Hudson
>>> outage we'll just have to wait until early next week to try things
>>> once the dust has settled.
>>>
>>> _______________________________
>>> Brian Fitzpatrick (aka "Fitz")
>>> Senior Software Engineer, SOA-P
>>> JBoss by Red Hat
>>>
>>> ----- Original Message -----
>>> From: "Nick Boldt"<nboldt at redhat.com>
>>> To: external-exadel-list at redhat.com, jbds-pm-list at redhat.com,
>>> jbosstools-dev at lists.jboss.org
>>> Sent: Friday, April 29, 2011 12:01:06 AM
>>> Subject: [jbosstools-dev] M1 Status Update - trunk and maintenance branch
>>>
>>>
>>> Overall:
>>>
>>> * 2 stuck slaves (vmg17, hudson1) reported to eng-ops@; one taken down,
>>> the other left up because another team's currently using it.
>>>
>>> * Hudson's next scheduled maintenance is April 29th, 2011 - 6:00AM GMT,
>>> so I can't kick jobs to run over night :(
>>>
>>> ---
>>>
>>> JBT 3.3.0.M1 / JBDS 5.0.0.M1:
>>>
>>> * Savara/Scribble missing (refactored?) feature:
>>> https://issues.jboss.org/browse/JBIDE-8817 (blocks aggregate build)
>>>
>>> * AS - single test failure: https://issues.jboss.org/browse/JBIDE-8816
>>>
>>> * VPE had 219 tests on Jan 11; now only 17 tests are running and of
>>> those, 6 are failing
>>>
>>> * Seam has 3 test failures: https://issues.jboss.org/browse/JBIDE-8759
>>>
>>> ---
>>>
>>> JBT 3.2.1.M1 / JBDS 4.1.0.M1:
>>>
>>> * Aggregate builder is fixed (I think!), but hit a network snag trying
>>> to fetch latest bits because I disabled the "wait until all upstream are
>>> done" option in the job in order to test my latest publish.sh fixes.
>>> Respin will fix this&  allow me to verify my fix worked, then I can
>>> re-enable the block-while-upstream-spinning option.
>>>
>>> * One last Seam test failure: https://issues.jboss.org/browse/JBIDE-8818
>>>
>>> * AS&  Deltacloud jobs time out after 2hrs; job timeout increased to
>>> 3hrs. Would respin but Hudson is in shutdown mode.
>>>
>>> * JSF was clean (no failures) but now has 7 new tests and 14 new
>>> failures: https://issues.jboss.org/browse/JBIDE-8819
>>>