[jbosstools-dev] An excursion into integration testing plugins with Arquillian

Max Rydahl Andersen manderse at redhat.com
Fri Jul 18 08:08:29 EDT 2014


On 10 Jul 2014, at 11:24, phantomjinx wrote:

> On 07/10/2014 09:06 AM, Max Rydahl Andersen wrote:
>>
>>> On 09/07/2014, at 14.38, phantomjinx 
>>> <p.g.richardson at phantomjinx.co.uk> wrote:
>>>
>> On 07/04/2014 05:01 PM, Max Rydahl Andersen wrote:
>>>>>>>
>>>>>>> My main concern is that this is bringing in dependencies outside 
>>>>>>> or our target
>>>>>>> platform thus less easy to contain/check for overlaps. Also - 
>>>>>>> using mvn copy goal
>>>>>>> seems to me to be the better way rather than using ant auto 
>>>>>>> builders?
>>>>>>
>>>>>> The ant auto builder [1] does hands-off maven by calling 'mvn 
>>>>>> process-sources'. This
>>>>>> always executes the mvn copy-dependencies goal so bringing in the 
>>>>>> dependencies [2]. It
>>>>>> has always been essential that any process happening while 
>>>>>> developing in Eclipse must
>>>>>> also occur when building on the command line through maven. This 
>>>>>> is an example of that
>>>>>> with the ant providing the plumbing between Eclipse and maven.
>>>>>
>>>>> ..isn't that what the tycho-m2 plugin does for you ?
>>
>> Well I am no expert in tycho so I may be wrong or not-up-to-date but 
>> no tycho cannot help.
>>
>> Tycho looks only looks for dependencies in pom files, which are osgi 
>> bundles. Normal maven jar
>> libraries are ignored hence for those libraries to be available on 
>> the classpath to both
>> eclipse's P2 and Tycho, they much be listed in the manifest file. I 
>> do this by specifying them
>> as dependencies in the pom file and using copy-dependencies to get 
>> them into the lib directory
>> of the plugin.
>>
>>
>>> Yes, we do this in other places too and tycho m2e integration makes 
>>> it happen without needing
>>> the ant step.
>>
>>> /max
>
> Well eliminating the need for the ant build scripts would certainly 
> simplify things. Can you point
> me to an example project as the tycho-m2e documentation on the net is 
> a little scant.

sorry for delay.

one example is the openshift project.

https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.2.0.Beta3x/plugins/org.jboss.tools.openshift.express.client/pom.xml#L32

shows how we define copy dependencies.

When you import it as a maven project you'll get errors/warnings about 
"plugin not covered by lifecycle" for tycho related plugins.

Run Quickfix and download the m2e-tycho plugin.

restart eclipse.

now when you maven update the copy goal should be taking into account.

/max

>
> Cheers
>
> PGR
>
> - --
> Paul Richardson
>
> * p.g.richardson at phantomjinx.co.uk
> * p.g.richardson at redhat.com
> * pgrichardson at linux.com
>
> "I know exactly who reads the papers ...
>
> * The Daily Mirror is read by people who think they run the country.
> * The Guardian is read by people who think they ought to run the 
> country.
> * The Times is read by people who do actually run the country.
> * The Daily Mail is read by the wives of the people who run the 
> country.
> * The Financial Times is read by the people who own the country.
> * The Morning Star is read by the people who think the country ought 
> to be run by another country.
> * The Daily Telegraph is read by the people who think it is."
>
> Jim Hacker, Yes Minister


/max
http://about.me/maxandersen



More information about the jbosstools-dev mailing list