On 01/09/2014 04:59 AM, Max Rydahl Andersen wrote:
>>> Works for me for all modules, except forge, which fails
with error
>>>
>>> Failed to execute goal
>>> org.jboss.forge.furnace:furnace-maven-plugin:2.0.0.Beta4:addon-install
>>> (deploy-addons) on project org.jboss.tools.forge2.runtime:
>>> Execution deploy-addons of goal
>>> org.jboss.forge.furnace:furnace-maven-plugin:2.0.0.Beta4:addon-install
>>> failed:
>>> org.eclipse.aether.resolution.DependencyResolutionException:
>>> Failure to find
>>> org.jboss.forge.addon:core:jar:forge-addon:2.0.0.Beta4 in
>>>
[
http://maven.repository.redhat.com/techpreview/all/](http://maven.reposit...
>>> was cached in the local repository, resolution will not be
>>> reattempted until the update interval of
>>> redhat-techpreview-all-repository has elapsed or updates are forced
>>> -> [Help 1]
>>
>> I assume that tech preview from
redhat.com comes from your own
>> settings.xml ?
>
> Yep and that was wrong. Now without it, forge build works.
That is actually bad if including that repo fails the build.
Can you show the settings.xml that was giving your build failures ?
I just had settings.xml below, looks like maven looked only into repo
from active porfile.
<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
<settings
xmlns="http://maven.apache.org/SETTINGS/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd">
<profiles>
<profile>
<id>redhat-techpreview-all-repository</id>
<repositories>
<repository>
<id>redhat-techpreview-all-repository</id>
<name>Red Hat Tech Preview repository (all)</name>
<
url>http://maven.repository.redhat.com/techpreview/all/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>redhat-techpreview-all-repository</id>
<name>Red Hat Tech Preview repository (all)</name>
<
url>http://maven.repository.redhat.com/techpreview/all/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>redhat-techpreview-all-repository</activeProfile>
</activeProfiles>
</settings>
Denis
/max
>>
>> /max
>>
>>>
>>> Denis
>>>
>>>
>>> On 01/07/2014 05:56 AM, Mickael Istria wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Here is a proposal for a new 4.40.0.Alpha2-SNAPSHOT target
>>>> platform:
>>>>
[
https://github.com/jbosstools/jbosstools-target-platforms/pull/32](https:...
>>>> It consists in the following changes:
>>>> * Update to Luna M4
>>>> ** most projects have contributed a new build for M4
>>>> ** some projects did not change compared to previous TP (Orbit,
>>>> Mylyn, SWTBot)
>>>> ** TP now includes latest 3.2.0 release of EGit
>>>> ** TP now includes Jetty 8.1.12 release instead of 8.1.10 (so does
>>>> the Eclipse Luna M4 package)
>>>> ** 3rd party stuff (Atlassian, GWT) was not updated.
>>>>
>>>>
>>>> Please review this PR and yell if there is anything shocking. You
>>>> can use the following stuff to try to build build the TP locally
>>>> and try out against your component:
>>>>
>>>> Build target-platform:
>>>>
>>>> $ cd jbosstools-target-platforms
>>>> $ git fetch mistria LunaM4
>>>> $ git checkout FETCH_HEAD
>>>> $ cd jbosstools/multiple
>>>> $ mvn clean install -P \!multiple2repo
>>>>
>>>> Try with just built target-platform:
>>>> $ cd /path/to/your/component
>>>> $ mvn clean verify -Dtpc.version=4.40.0.Alpha2-SNAPSHOT
>>>> -Pmultiple.target
>>>>
>>>> Cheers,
>>>>
>>> --
>>>> 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@lists.jboss.org](mailto:jbosstools-dev@lists.jboss.org)
>>>>
>>>>
>>>>
[
https://lists.jboss.org/mailman/listinfo/jbosstools-dev](https://lists.jb...
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev