2:53 a.m.
Am 06.07.2015 um 09:46 schrieb Max Rydahl Andersen:
>>>>>> Caused by:
org.eclipse.aether.transfer.ArtifactNotFoundException:
>>>>>> Could
>>>>>> not find artifact
>>>>>> org.apache.camel:camel-core:jar:2.15.1.redhat-620129
>>>>>> in redhat-techpreview-all-repository
>>>>>> (http://maven.repository.redhat.com/techpreview/all/)
>>>>> --> 129 used to be the GA build number for Fuse 6.2. They changed
>>>>> recently to 133 and the old 129 is probably no
>>>>> longer available from the repository. I will fix it asap.
>>>> eh - what maven repository are we relying on where they remove
>>>> releases ?!
> -> mostly EA repository / staging repository. once a version goes GA
> it
> will be available from the release repo.
By EA/staging you mean the vpn only accessible repos ?
-->
https://repository.jboss.org/nexus/content/groups/ea/ if I recall
correctly. And that should be public.
Are you saying we are using VPN only accessible bits in our open source
project
thus noone outside red hat can build it ? thats not nice.
Can't we have a default build that uses publicly available bits ?
--> see above.
>>>> Which branch are being built/used instead ?
> --> nobody is working on master branch atm. We aim for 7.3.1 atm and
> thats why master is currently a bit outdated. (not much though)
If noone is working on it why is it even broken ? :)
--> How about the switch to Mars and the now no longer available
Terminal stuff? Is that reason enough :D
Btw. that has been fixed end of last week. The build is now working.
>>>>>> If it doesn't work for me, it most likely
also doesn't work for
>>>>>> other
>>>>>> possible external contributors. One way to test this is to wipe
>>>>>> your
>>>>>> .m2
>>>>>> folder and try to build your stuff and make sure it works.
>>>>> --> the only way to make the build work again is to exclude the
>>>>> whole
>>>>> JMX and Servers stuff. I will do that asap.
>>>> Did we break API already ? :)
> --> yes and no. The terminal for apache karaf servers is no longer
> supported but you already know about that issue. The JMX one is more
> an
> internal refactoring issue.
so fuse had an internal dependency ? is it one we can avoid ?
--> This has been
fixed end of last week.
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-fuse-dev mailing list
jbosstools-fuse-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-fuse-dev