[jbosstools-dev] Funkyness with .target using google adt site

Nick Boldt nboldt at redhat.com
Wed Mar 27 23:21:01 EDT 2013


On 03/27/2013 09:08 PM, Max Andersen wrote:
> Were you able to run mvn install on my repo without any errors ?

Yes - which is why I said I could not reproduce your error.

> Why does one have to do All these steps when adding just a dependency for testing? Seems like massive overkill.
> What does fix version do that isn't already present when I've specified the exact versions ?

To verify that the sites listed are still current with respect to the 
list of IUs. Maybe something has changed. Maybe the list of IUs you 
added have new versions. Rather than having to look at all the URLs by 
hand, you can simply run the version update step, wait a few seconds, 
and be sure that it's all current and up to date.

"Massive overkill" only takes a few seconds. But if you know for sure 
that the list of URLs and IUs in your target file are current and up to 
date, then yes, it's an unnecessary step. You would therefore need only 
steps 2 and 3:

pushd jbosstools/multiple && mvn clean install && popd

pushd jbosstools/unified && mvn install 
-DtargetRepositoryUrl=file://path/to/jbosstools/multiple/target/jbosstools-multiple.target.repo/ 
&& popd

N

> Sent from a mobile device
>
> On 27/03/2013, at 14.51, Nick Boldt <nboldt at redhat.com> wrote:
>
>> Cannot reproduce your error.
>>
>> If I install those two features from the Android site into Eclipse 4.3, I get these 5 plugins and 2 features:
>>
>> $➔ find . -maxdepth 2 -name "*android*" -o -name "*adt*"
>> ./plugins/com.android.ide.eclipse.adt.package_21.1.0.v201302060044-569685
>> ./plugins/com.android.ide.eclipse.base_21.1.0.v201302060044-569685.jar
>> ./plugins/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
>> ./plugins/overlay.com.android.ide.eclipse.adt.overlay_21.1.0.v201302060044-569685.jar
>> ./plugins/com.android.ide.eclipse.ddms_21.1.0.v201302060044-569685.jar
>> ./features/com.android.ide.eclipse.ddms_21.1.0.v201302060044-569685
>> ./features/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685
>>
>> If I resolve the target platform, I get the same 5 plugins and 2 features (except that they're all jars, none unpacked):
>>
>> $➔ find . -name "*android*" -o -name "*adt*"
>> ./jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt.package_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.base_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/plugins/overlay.com.android.ide.eclipse.adt.overlay_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.ddms_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/features/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
>> ./jbosstools-multiple.target.repo/features/com.android.ide.eclipse.ddms_21.1.0.v201302060044-569685.jar
>>
>> --
>>
>> Here's what I did [1]:
>>
>> BASEDIR=${HOME}/tru/targetplatforms/
>> for PROJECT in jbosstools; do
>>
>>   # 1. Merge changes in new target file to actual target file (this verifies that the versions on the stated sites match the versions in the .target file)
>>   pushd ${BASEDIR}/${PROJECT}/multiple && mvn org.jboss.tools.tycho-plugins:target-platform-utils:0.0.1-SNAPSHOT:fix-versions -DtargetFile=${PROJECT}-multiple.target && rm -f ${PROJECT}-multiple.target ${PROJECT}-multiple.target_update_hints.txt && mv -f ${PROJECT}-multiple.target_fixedVersion.target ${PROJECT}-multiple.target && popd
>>
>>   # 2. Resolve the new target platform (pull all the IUs listed and their dependencies into an update site on disk), using the updated .target file
>>   pushd ${BASEDIR}/${PROJECT}/multiple && mvn clean install
>>
>>   # 3. Verify the "multiple" target platform is self-contained by building unified.target locally, pointed at the multiple site you resolved in step 2
>>   pushd ${BASEDIR}/${PROJECT}/unified && mvn install -DtargetRepositoryUrl=file://${BASEDIR}/${PROJECT}/multiple/target/${PROJECT}-multiple.target.repo/ && popd
>>
>> done
>>
>> [1] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.30.x/README.md#updating-versions-of-ius-in-target-files
>>
>> On 03/24/2013 12:56 PM, Nick Boldt wrote:
>>> Why add android to the TP? It's only a 3rd party thing for Central.
>>> Nothing in JBT depends on it... right?
>>>
>>> As to the failure...
>>>
>>>> Could not find
>>> "com.android.ide.eclipse.ddms.feature.group/21.1.0.v201302060044-569685"
>>> in the repositories of the current location
>>>
>>> Sounds like the feature you asked for isn't on the site.
>>>
>>> On 03/23/2013 11:40 PM, Max Rydahl Andersen wrote:
>>>> Hey,
>>>>
>>>> I made an experiment today at
>>>> https://github.com/maxandersen/jbosstools-target-platforms/blob/tp_process
>>>> where the jbosstools .targt file got the following added to it:
>>>>
>>>> <location includeAllPlatforms="false" includeMode="planner"
>>>> includeSource="true" type="InstallableUnit">
>>>>        <unit id="com.android.ide.eclipse.ddms.feature.group"
>>>> version="21.1.0.v201302060044-569685"/>
>>>>        <unit id="com.android.ide.eclipse.adt.feature.group"
>>>> version="21.1.0.v201302060044-569685"/>
>>>>        <repository location="https://dl-ssl.google.com/android/eclipse"/>
>>>>      </location>
>>>>
>>>> mvn install for the multiple completes, but the only IU's added are:
>>>>
>>>> ./multiple/target/jbosstools-multiple.target.repo/features/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
>>>>
>>>> ./multiple/target/jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt.package_21.1.0.v201302060044-569685.jar
>>>>
>>>> ./multiple/target/jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
>>>>
>>>> ./multiple/target/jbosstools-multiple.target.repo/plugins/overlay.com.android.ide.eclipse.adt.overlay_21.1.0.v201302060044-569685.jar
>>>>
>>>>
>>>> where it should include much more.
>>>>
>>>> After that it then fails during validation of unified stating:
>>>>
>>>> [INFO] Validating
>>>> /Users/max/code/jbosstools/jbosstools-target-platforms/jbosstools/unified/target/jbosstools-unified.target...
>>>>
>>>> [INFO] Failed, see Error log below
>>>> [ERROR] Validation found errors in 1 .target files:
>>>> Could not resolve content of jbosstools-unified.target
>>>> Could not find
>>>> "com.android.ide.eclipse.ddms.feature.group/21.1.0.v201302060044-569685"
>>>> in the repositories of the current location
>>>>
>>>> No other errors/warnings reported afaics.
>>>>
>>>> Anyone with an idea on what is going on here?
>>>>
>>>> /max
>>>>
>>>> _______________________________________________
>>>> 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

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


More information about the jbosstools-dev mailing list