[jbosstools-dev] Source lookup in maven component

Fri May 4 00:55:42 EDT 2012

Yeah. We should prolly spawn multiple docs for all the various 
use-cases. Otherwise the single doc will be unmanageable.

Maybe it's time for a FAQ / index where we can list all the ways to 
build based on usecase, then link to the various sub-documents matching 
that workflow?

N

On 05/03/2012 05:39 PM, Denis Golovin wrote:
> do you mean to have it as a separate article? Something like "How to
> build JBoss Tools aggregated update site locally?"
>
> Denis
>
> On 05/02/2012 07:20 PM, Nick Boldt wrote:
>> Sounds like a reasonable process, including using the "local-site"
>> workaround.
>>
>> Would you mind adding this to the wiki?
>>
>> N
>>
>> On 05/02/2012 06:25 PM, Denis Golovin wrote:
>>> There is a way to test it with aggregate/local-site
>>>
>>> Nick, correct me if I'm missing something from or wrong about how whole
>>> process works currently.
>>>
>>> So, first get update for build/aggregate/local-site, because I fixed
>>> urls to local update sites and removed remote composite repo to make
>>> this site really local
>>> Then add new feature into component's update site category.xml (which
>>> you probably did already).
>>> Then build everything first with
>>>
>>> mvn clean package -DskipTests
>>>
>>> and add new feature to aggregated aggregate/site/site.xml and build
>>> aggregated update site locally using
>>>
>>> mvn clean package -DskipTests build/aggregate/pom.xml
>>> -Djbosstools-nightly-staging-composite=file:///home/eskimo/Projects/jbds-build/jbosstools-src/build/aggregate/local-site
>>>
>>>
>>>
>>> where
>>> /home/eskimo/Projects/jbds-build/jbosstools-src/build/aggregate/local-site
>>>
>>> is a path to your build/aggregate/local-site
>>>
>>> Then commit should be done in several steps if you don't want to break
>>> the aggregation build:
>>> 1. commit your feature and component/site/category.xml where new
>>> features are included
>>> 2. Wait until component is built and update site is published to staging
>>> area
>>> 3. commit aggregated site.xml
>>>
>>> this process build aggregate update site from local component's update
>>> sites.
>>>
>>> Denis
>>>
>>>
>>> On 05/02/2012 02:18 PM, Snjezana Peco wrote:
>>>> I have built JBT locally, then started to build site.
>>>> Maven has downloaded all components from the remote site.
>>>>
>>>> Snjeza
>>>>
>>>>
>>>> Nick Boldt wrote:
>>>>> Not sure; I'd expect Maven is smart enough to copy from local vs.
>>>>> downloading anew if the stuff on the server == stuff already on local.
>>>>>
>>>>> N
>>>>>
>>>>> On 05/02/2012 03:50 PM, Snjezana Peco wrote:
>>>>>> Nick Boldt wrote:
>>>>>>> Yes, there is: you run the update site aggregation build locally.
>>>>>>>
>>>>>>> You either get a build, or an error.
>>>>>>>
>>>>>>> If content on disk is newer than remote, site will be built from
>>>>>>> local
>>>>>>> .m2 repo.
>>>>>> If they are the same, site will be built from remote?
>>>>>>
>>>>>> Snjeza
>>>>>>
>>>>>>> This is how I've been building/testing Central& all the aggregate
>>>>>>> sites (JBT Core, JBT SOA, webtools, JBT Core tests, JBT SOA tests,
>>>>>>> JBDS Core, JBDS Extras, JBDS SOA), locally for months.
>>>>>>>
>>>>>>> N
>>>>>>>
>>>>>>> On 05/02/2012 11:07 AM, Max Rydahl Andersen wrote:
>>>>>>>>> No, because the build is an aggregation designed to pull from
>>>>>>>>> upstream.
>>>>>>>> hmm....that sucks.
>>>>>>>>
>>>>>>>> so no way for devs to actually test their local files such as
>>>>>>>> site.xml for correctness ;(
>>>>>>>>
>>>>>>>> /max
>>>>>>>>
>>>>>>>>> See also this pom, which explains how to build the other
>>>>>>>>> aggregates and
>>>>>>>>> skip unneeded download steps:
>>>>>>>>>
>>>>>>>>> http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/pom.xml
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 04/30/2012 07:59 AM, Snjezana Peco wrote:
>>>>>>>>>> This command downloads components from the JBoss site.
>>>>>>>>>> Is there any command that uses components that are built locally?
>>>>>>>>>>
>>>>>>>>>> Snjeza
>>>>>>>>>>
>>>>>>>>>> Mickael Istria wrote:
>>>>>>>>>>> When you got a CI build OK for the component your worked on, try
>>>>>>>>>>> that:
>>>>>>>>>>>
>>>>>>>>>>> cd build/aggregate/site/
>>>>>>>>>>> mvn clean install -P jbosstools-nightly-staging-composite
>>>>>>>>>>>
>>>>>>>>>>> It will create the aggregated site locally using the latest CI
>>>>>>>>>>> builds
>>>>>>>>>>> for all components. If you did something wrong in site.xml, it
>>>>>>>>>>> fails
>>>>>>>>>>> quickly.
>>>>>>>>>>>
>>>>>>>>>>> On 04/29/2012 09:47 PM, Snjezana Peco wrote:
>>>>>>>>>>>> I have built locally the whole JBoss Tools without any error. I
>>>>>>>>>>>> have used:
>>>>>>>>>>>>
>>>>>>>>>>>> mvn clean install -DskipTests
>>>>>>>>>>>>
>>>>>>>>>>>> How can I check if site.xml is valid?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Snjeza
>>>>>>>>>>>>
>>>>>>>>>>>> Nick Boldt wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Found& fixed a typo in the aggregate/site/site.xml which was
>>>>>>>>>>>>> preventing it from finding the new feature.
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Next spin should be good - also running locally to verify.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Devs, when you're adding new features, please ensure your
>>>>>>>>>>>>> changes to
>>>>>>>>>>>>> shared components (eg., build/aggregate/site/site.xml) build
>>>>>>>>>>>>> locally
>>>>>>>>>>>>> before committing!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks in advance,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nick
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 04/27/2012 06:30 PM, Snjezana Peco wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> The source lookup feature builds locally.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Snjeza
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Max Andersen wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Nick - forgot to mention snjezana will be adding
>>>>>>>>>>>>>>> sourcelookup
>>>>>>>>>>>>>>> to the
>>>>>>>>>>>>>>> maven component as a separate feature.
>>>>>>>>>>>>>>> If you spot something problematic dependency/build wise then
>>>>>>>>>>>>>>> let me
>>>>>>>>>>>>>>> know.
>>>>>>>>>>>>>>> /max (sent from my phone)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Mickael Istria
>>>>>>>>>>> Eclipse developer at JBoss, by Red
>>>>>>>>>>> Hat<http://www.jboss.org/tools>
>>>>>>>>>>> My blog<http://mickaelistria.wordpress.com> - My Tweets
>>>>>>>>>>> <http://twitter.com/mickaelistria>
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>>>> --
>>>>>>>>> Nick Boldt :: JBoss by Red Hat
>>>>>>>>> Productization Lead :: JBoss Tools& Dev Studio
>>>>>>>>> http://nick.divbyzero.com
>>>>>>>>> _______________________________________________
>>>>>>>>> jbosstools-dev mailing list
>>>>>>>>> jbosstools-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com