Ah, so really it's gotten worse now that I changed it as the jar target is always
getting run. We could re-add the warning but this time to ask that the jar target be run
before.
Would that be an option?
When I changed the test target to not depend on the dist etc target, I
did it for all these reasons. It cut test time dramatically. Stuff is
getting called multiple time - "generate-config-model" was getting
called 3 or 4 times. Of course the text book answer to this problem is
to sort that out, but the build is a beast at this stage, with a hornets
nest of dependencies - I'd be afraid to make any major changes to it.
Ever hear of the "Shotgun Surgery" code smell ;-)
Role on maven shmaven ;-)
Daniel Bevenius wrote:
> I see it when I run "ant clean dist test". Should
these be
> integration tests perhaps, or has the build changed to run the
> integration tests under the general "test" build target?
>
I updated the 'test' target, (after the discussion in the "build
question" googlegroups thread) so that it depends on the jar target which means
'ant clean test' should be all that is needed to run the tests. Running dist will
actually run som stuff twice, like generate-config-model.
Running 'ant dist test' is now the same as running the default target.
But the build does take quite some time for me...like 7 min or so. I think that a lot of
jar targets are run regardless of changes to classes. The generate-config-model will
always run even if the schemas are unmodified. This will change when we move to jabx
though.
/Daniel
"ant clean dist test"
I'm running clean, dist, test within Eclipse. Took 21 minutes to
build everything for me ;-)
I'll do another update to make sure nothing changed since yesterday
afternoon, when I did my last one.
I hope the test rule *does not* run the integration tests ;-)
Mark.
On 27 Jun 2007, at 10:27, Tom Fennelly wrote:
> What build rule are you using ;-) ?
>
> I see it when I run "ant clean dist test". Should these be
> integration tests perhaps, or has the build changed to run the
> integration tests under the general "test" build target?
>
> T.
>
>
> Mark Little wrote:
>
>> I did an update and a build, but didn't see this. What build rule
>> were you using?
>>
>> Mark.
>>
>>
>> On 26 Jun 2007, at 16:54, Kurt T Stam wrote:
>>
>>
>>> Anyone getting this? What do I do to fix this?
>>>
>>> [java] [junit] Testcase:
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListenerUni
>>> tTest
>>> took 0 sec
>>> [java] [junit] Caused an ERROR
>>> [java] [junit]
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.RemoteFileSyste
>>> mStrategyException:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> cheException:
>>> org.jgroups.ChannelException: failed to start protocol stack
>>> [java] [junit] org.jboss.soa.esb.ConfigurationException:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.RemoteFileSyste
>>> mStrategyException:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> cheException:
>>> org.jgroups.ChannelException: failed to start protocol stack
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.cr
>>> eateRemoteFileSystemStrategy(ReadOnlyRemoteGatewayListener.java:222)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.<i
>>> nit>(ReadOnlyRemoteGatewayListener.java:83)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListenerUni
>>> tTest.createRemoteGatewayListener
>>> (ReadOnlyRemoteGatewayListenerUnitTest.java:212)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListenerUni
>>> tTest.classSetup(ReadOnlyRemoteGatewayListenerUnitTest.java:76)
>>> [java] [junit] at
>>> org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod
>>> (BeforeAndAfterRunner.java:74)
>>> [java] [junit] at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runBefores
>>> (BeforeAndAfterRunner.java:50)
>>> [java] [junit] at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected
>>> (BeforeAndAfterRunner.java:33)
>>> [java] [junit] at
>>> org.junit.internal.runners.TestClassRunner.run
>>> (TestClassRunner.java:52)
>>> [java] [junit] at
>>> junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32)
>>> [java] [junit] Caused by:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.RemoteFileSyste
>>> mStrategyException:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> cheException:
>>> org.jgroups.ChannelException: failed to start protocol stack
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.ReadOnlyRemoteF
>>> ileSystemStrategy.init(ReadOnlyRemoteFileSystemStrategy.java:63)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.cr
>>> eateRemoteFileSystemStrategy(ReadOnlyRemoteGatewayListener.java:205)
>>> [java] [junit] ... 15 more
>>> [java] [junit] Caused by:
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> cheException:
>>> org.jgroups.ChannelException: failed to start protocol stack
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> che.start(FtpFileCache.java:135)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.ReadOnlyRemoteF
>>> ileSystemStrategy.init(ReadOnlyRemoteFileSystemStrategy.java:59)
>>> [java] [junit] ... 16 more
>>> [java] [junit] Caused by: org.jgroups.ChannelException:
>>> failed to
>>> start protocol stack
>>> [java] [junit] at org.jgroups.JChannel.connect
>>> (JChannel.java:389)
>>> [java] [junit] at
>>> org.jboss.cache.TreeCache.startService(TreeCache.java:1263)
>>> [java] [junit] at
>>> org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCa
>>> che.start(FtpFileCache.java:130)
>>> [java] [junit] ... 17 more
>>> [java] [junit] Caused by: java.lang.Exception: exception
>>> caused by
>>> UDP.start()
>>> [java] [junit] at
>>> org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:582)
>>> [java] [junit] at
>>> org.jgroups.stack.DownHandler.run(Protocol.java:118)
>>> [java] [junit] Caused by: java.lang.Exception: problem creating
>>> sockets (bind_addr=localhost/127.0.0.1, mcast_addr=228.1.2.3:48866)
>>> [java] [junit] at org.jgroups.protocols.UDP.start
>>> (UDP.java:372)
>>> [java] [junit] at
>>> org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:571)
>>> [java] [junit] ... 1 more
>>> [java] [junit] Caused by: java.net.SocketException: bad
>>> argument
>>> for IP_MULTICAST_IF2: No IP addresses bound to interface
>>> [java] [junit] at
>>> java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)
>>> [java] [junit] at
>>> java.net.PlainDatagramSocketImpl.setOption
>>> (PlainDatagramSocketImpl.java:299)
>>> [java] [junit] at
>>> java.net.MulticastSocket.setNetworkInterface(MulticastSocket.java:
>>> 502)
>>> [java] [junit] at
>>> org.jgroups.protocols.UDP.createSockets(UDP.java:490)
>>> [java] [junit] at org.jgroups.protocols.UDP.start
>>> (UDP.java:367)
>>> [java] [junit] ... 2 more
>>> [java] BUILD FAILED
>>> [java] C:\cygwin\home\kstam\dev\jbossesb\product\build.xml:
>>> 131: The
>>> following error occurred while executing this line:
>>> [java] C:\cygwin\home\kstam\dev\jbossesb\product\build.xml:
>>> 141: The
>>> following error occurred while executing this line:
>>> [java]
>>> C:\cygwin\home\kstam\dev\jbossesb\product\rosetta\build.xml:87: The
>>> following error occurred while executing this line:
>>> [java]
>>> C:\cygwin\home\kstam\dev\jbossesb\product\rosetta\tests\build.xml:
>>> 82:
>>> The following error occurred while executing this line:
>>> [java]
>>> C:\cygwin\home\kstam\dev\jbossesb\product\rosetta\tests\build.xml:
>>> 109:
>>> Test
>>> org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListenerUni
>>> tTest
>>> failed
>>> [java] Total time: 3 minutes 57 seconds
>>>
>>> BUILD FAILED
>>> C:\cygwin\home\kstam\dev\jbossesb\product\build.xml:420: The
>>> following
>>> error occurred while executing this line:
>>> C:\cygwin\home\kstam\dev\jbossesb\product\build.xml:87: Java
>>> returned: 1
>>>
>>> _______________________________________________
>>> esb-dev mailing list
>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org>
>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>>
>> ----
>>
>> Mark Little
>> mlittle(a)redhat.com <mailto:mlittle@redhat.com>
>>
>> JBoss, a Division of Red Hat
>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
>> Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
>> Registered in UK and Wales under Company Registration No. 3798903
>> Directors: Michael Cunningham (USA), Charlie Peters (USA) and
>> David Owens (Ireland)
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> esb-dev mailing list
>> esb-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>
>>
> --
> Red Hat:
> Registered Address: Red Hat Ltd, Brian O' Donnell and Partners, 62
> Merrion Square, Dublin 2, Ireland.
> Registered in the Companies Registration Office, Parnell House, 14
> Parnell Square, Dublin 1, Ireland, at No. 304873
> Directors: Charlie Peters (USA), Michael Cunningham (USA). David
> Owens, Brendan Lane
>
>
----
Mark Little
mlittle(a)redhat.com
JBoss, a Division of Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire,
SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Charlie Peters (USA) and David
Owens (Ireland)
--
Red Hat:
Registered Address: Red Hat Ltd, Brian O' Donnell and Partners, 62 Merrion Square,
Dublin 2, Ireland.
Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin
1, Ireland, at No. 304873
Directors: Charlie Peters (USA), Michael Cunningham (USA). David Owens, Brendan Lane
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.