temp-jbosstools-build is out of date but otherwise looks OK. Can you
pull a fresh version? parent/pom.xml and target-platforms/* have been updated since you
last pulled it.
Only if it helps something ;)
temp-jbosstools-build-sites is also out of date -- it's missing
the work I started (and need to finish) on p2 repo stats using
org.eclipse.wtp.releng.tools.addRepoProperties tool
(
https://issues.jboss.org/browse/JBIDE-12432)
yes - they are outofdate since the migration run was done a week ago - what is important
for the build repos is if this is the structure we want, is this what makes sense to have
this split?
All three above appear to have the correct branches defined:
the trunk will be removed in the final repo.
* master
remotes/origin/HEAD -> origin/master
remotes/origin/jbosstools-3.2.x
remotes/origin/jbosstools-3.3.x
remotes/origin/jbosstools-4.0.0.Alpha2
remotes/origin/master
remotes/origin/trunk
Testing build of temp-jbosstools-central now using attached root pom.
On 10/04/2012 02:12 PM, Max Rydahl Andersen wrote:
> Hi,
>
>
https://github.com/jbosstools/ now has temp-jbosstools-* repos now loaded with svn
data from 2 days ago.
>
> These are *temporary* repositories so you can do whatever you want with them.
>
> Please try and fork/clone these, import them and see if things work as they should in
eclipse.
>
> Check if you can build with tycho.
>
> check if the branches/tags looks like you expect them to look etc.
>
>
> I've started setting up push rights for the appropriate repos but i'm missing
a bunch of users -
> so please respond to the other email asking for your github username if you need push
access.
>
> /max
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)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
<pom.xml>