[
http://jira.codehaus.org/browse/MEXEC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134269#action_134269
]
Jerome Lacoste commented on MEXEC-38:
-------------------------------------
Andrew,
(1) I have a gut feeling this isn't exec related. MNGECLIPSE-30 seems to
confirm that (similar issue, no exec plugin used)
I've still spent some time trying to reproduce the problem but wasn't able to.
rev 10706 doesn't contain schemadocs, nor associated profile. I've changed the
tools/pom.xml to enable it, but that didn't reproduce my problem.
I've tried with HEAD, currently r11579, but that doesn't build:
Results :
Failed tests:
registration (org.mule.util.properties.PropertyExtractorManagerTestCase)
create pool (org.mule.util.object.PooledObjectFactoryTestCase)
fail on exhaust (org.mule.util.object.PooledObjectFactoryTestCase)
block expiry on exhaust (org.mule.util.object.PooledObjectFactoryTestCase)
on remove calls dispose (org.mule.util.object.PooledObjectFactoryTestCase)
Tests in error:
create if necessary factory (org.mule.util.object.ObjectFactoryUtilsTestCase)
create if necessary bad factory
(org.mule.util.object.ObjectFactoryUtilsTestCase)
manager (org.mule.util.properties.PropertyExtractorManagerTestCase)
default extractor (org.mule.util.properties.PropertyExtractorManagerTestCase)
cache update (org.mule.registry.TransformerCachingTestCase)
empty server url (org.mule.internal.admin.MuleAdminAgentTestCase)
non empty server url (org.mule.internal.admin.MuleAdminAgentTestCase)
successful exception router
(org.mule.routing.outbound.ExceptionBasedRouterTestCase)
both failing (org.mule.routing.outbound.ExceptionBasedRouterTestCase)
do work executes synchronously (org.mule.MuleWorkManagerTestCase)
schedule work executes asynchronously (org.mule.MuleWorkManagerTestCase)
start work executes asynchronously (org.mule.MuleWorkManagerTestCase)
round trip encryption (org.mule.mule.security.PbeEncryptionStrategyTestCase)
within component (org.mule.util.object.PooledObjectFactoryTestCase)
lookup object (org.mule.util.object.PooledObjectFactoryTestCase)
functions from extractor manager
(org.mule.util.properties.FunctionPropertyExtractorTestCase)
create inbound endpoint (org.mule.endpoint.EndpointFactoryTestCase)
create inbound endpoint from global endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
create inbound endpoint from named concrete endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
create outbound endpoint (org.mule.endpoint.EndpointFactoryTestCase)
createoutbound endpoint from global endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
createoutbound endpoint from named concrete endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
create inbound endpoint with builder
(org.mule.endpoint.EndpointFactoryTestCase)
create outbound endpoint with builder
(org.mule.endpoint.EndpointFactoryTestCase)
create endpoint (org.mule.endpoint.EndpointFactoryTestCase)
create endpoint from global endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
create endpoint from named concrete endpoint
(org.mule.endpoint.EndpointFactoryTestCase)
routing exception null u m o message valid u m o immutable endpoint
(org.mule.ExceptionsTestCase)
recipient list router
(org.mule.routing.outbound.StaticRecipientListRouterTestCase)
roundtrip transform
(org.mule.transformer.compression.GZipTransformerRawBytesTestCase)
roundtrip bad return type
(org.mule.transformer.compression.GZipTransformerRawBytesTestCase)
round trip (org.mule.transformer.compression.GZipTransformerRawBytesTestCase)
build inbound endpoint (org.mule.endpoint.EndpointURIEndpointBuilderTestCase)
build outbound endpoint
(org.mule.endpoint.EndpointURIEndpointBuilderTestCase)
ignore bad input does not break chain
(org.mule.transformer.TransformerChainingTestCase)
Tests run: 558, Failures: 5, Errors: 35, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to
/home/jerome/Code/OSS/m2/exec-maven-plugin/src/test/projects/mule-testcase/mule-2.x/core/target/surefire-reports
for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 37 seconds
[INFO] Finished at: Sun May 11 08:45:31 CEST 2008
[INFO] Final Memory: 33M/112M
[INFO] ------------------------------------------------------------------------
This with
$ svn info
Path: .
URL: https://svn.codehaus.org/mule/branches/mule-2.x
Repository Root: https://svn.codehaus.org/mule
Repository UUID: bf997673-6b11-0410-b953-e057580c5b09
Revision: 11719
Node Kind: directory
Schedule: normal
Last Changed Author: tcarlson
Last Changed Rev: 11579
Last Changed Date: 2008-04-15 21:50:13 +0200 (Tue, 15 Apr 2008)
and if I skip tests, the build won't go on:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.mule:mule-core:test-jar:tests:2.1.0-M2-SNAPSHOT
So yes I can fiddle with POMs to try to build mule but given (1) I don't think
it's worth it except if I get a
* an exact description of how to reproduce the problem. In particular
** maven version used
** JDK used
** OS used
** svn co command
** diff to be applied before building
** instructions on how to reproduce the problem with a clean local repository
* better, a simple project that reproduces the problem :)
> ${version} being set?
> ---------------------
>
> Key: MEXEC-38
> URL: http://jira.codehaus.org/browse/MEXEC-38
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Affects Versions: 1.1-beta-1
> Reporter: andrew cooke
> Priority: Critical
> Fix For: 1.1
>
> Attachments: MULE-V2X-670-console-log.txt
>
>
> ok, apologies in advance - this isn't going to be a very helpful report - i
> did try to make a small "demo" test case, but failed, and i don't fully
> understand the issues. but here goes...
> i added a sub-project to the mule build that uses the maven-exec-plugin.
> unfortunately, when this was enabled along with another profile the build
> failed with reports of missing versions of packages that never existed.
> you can see a failure report here:
> http://dev.mulesource.com/bamboo/browse/MULE-V2X-670
> in the log at http://dev.mulesource.com/bamboo/browse/MULE-V2X-670/log you
> can see that there are a bunch of errors due to missing packages with version
> 2.4.1 - those packages do not exist. the version number is bogus.
> the package itself can be seen here:
> http://cvs.codehaus.org/browse/mule/branches/mule-2.x/tools/schemadocs
> some more experimenting showed that what seems to be happening is that when
> poms are pulled in from the repo and they contain ${version}, the value of
> version is being set to some random value by the exec plugin (you can check
> this by editing the pom in the repo and replacing the ${version} with the
> correct value - the associated error then goes away).
> our workaround was to add fake dependencies so that the sub-project using the
> plugin comes last (or at least later) in the build.
> i also found this report, which seems similar:
> http://jira.codehaus.org/browse/MNGECLIPSE-30
> your best chance at duplicating is probably to check mule out from svn,
> remove the dependencies at the top of the schemadocs pom (that refer to
> distributions) and running "mvn -Pdistributions,schemadocs install" (the
> profiles just enable the appropriate sub-packages).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
