[weld-dev] (Archetype JBoss docs) Re: Getting started with Weld and JBoss AS 6

[Pete Muir]

On 8 Dec 2009, at 22:46, Steven Boscarine wrote:

> 
>> 
>> 
>>> 
>>> If you see any opportunities for merging the docs, I can help
>>    out.  I
>>> think maven instructions will be helpful for maven users.
>>> 
>>> 
>>> Can the ANT script use JBOSS_HOME so the user can start without
>>    editing
>>> any properties files?
>> 
>>    It could do, it would be better to investigate the JBoss maven
>>    plugin IMO.
>> 
>> 
>> I know the JBoss deploy plugin quite well. It does use JBOSS_HOME by 
>> default, but can be overridden in the Maven plugin configuration. But 
>> the best solution is to assign the JBOSS_HOME to a Maven property and 
>> then use that propery in the plugin configuration. Then, you can use 
>> either JBOSS_HOME or the Maven property to tune the value. What I 
>> don't think is possible (w/o some build magic) is to have Maven read 
>> the value in build.properties (because that would just make life too 
>> easy, say the Maven guys).
>> 
>> -Dan
> If it matters, I wasn't really suggesting changing the maven setup, just 
> wondering if life would be easier for the ANT users if their script read 
> JBOSS_HOME as it is the only value needed to run the examples in JBoss. 
> 
> The obvious side effect would be that they could simply set an 
> environment variable that was probably already set on their system and 
> then run either the maven or the ant version without editing files. 
> 
> There's a tiny benefit for those checking out the code from SVN.  They 
> won't get icons in Tortoise/Eclipse telling them they have uncommitted 
> changes.  I usually personally avoid setting machine-specific files in 
> SCM if I can find an alternative as I hate it when I am the dummy who 
> accidentally commits his local config. 

Right, we have local.build.properties for this. 

But this is a good change overall, if you want to change it, that would be great :-) (affected are examples and TCK runs I think)