[jbosstools-fuse-dev] [jbosstools-dev] How to build fuseide locally? All I get is fails.

[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 ?

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 ?

>>>>
>>>> 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 ? :)

>>>>>> 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 ?

/max
http://about.me/maxandersen