40+ issues still open for Alpha2 ?
by Max Rydahl Andersen
Hi,
Alpha2 codefroze last week and we are ETA on release on friday but we still got 40+ issues assigned to it.
https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=p...
In there a bunch of N&N is still unresolved: See subtasks of https://issues.jboss.org/browse/JBIDE-12669
1. CLONE - CLONE - CLONE - Hibernate Component N&N Koen Aers
2. CLONE - CLONE - CLONE - ESB Component N&N Brian Fitzpatrick
3. CLONE - CLONE - CLONE - AS Component N&N Rob Stryker
4. CLONE - CLONE - Visual Editor Component N&N Yahor Radtsevich
5. CLONE - CLONE - CLONE - WS Component N&N Brian Fitzpatrick
6. CLONE - CLONE - Forge Component N&N Koen Aers
Please take the time to review these and fix/reject as appropriate ASAP.
Thank you,
Max
12 years, 1 month
[gitmigration] org.jboss.tools.jsf.doc.user/doc.zip needed ..ever?
by Max Rydahl Andersen
Hi,
jbosstools-javaee is currently clocking at about 555 MB history/git repo.
the biggest culprit here currently is:
jsf/plugins/org.jboss.tools.jsf.doc.user/doc.zip
jsf/plugins/org.jboss.tools.jsf.doc.user/doc_orig.zip
seam/plugins/org.jboss.tools.seam.doc.user/doc.zip
...but as I recall - these plugins have never been part of any release - they were just
experiments that never made it in (ironically because of being too big ;)
I'm wondering what we can do about these - they are required by the builds and thus if I remove the directory or just the file I will break
the builds of those branches.
Suggestions welcome!
p.s. I can basically do whatever with the content - easy: remove, delete, harder, but possible is to change it to something "smaller" that would continue
to work but not sure what that is.
btw. otherwise the biggest problem in javaee is the tendency in early days to commit and add complete web projects with full jar dependencies -
but those I can't remove since that would break more or less everything.
/max
12 years, 1 month
[gitmigration] BPEL was renamed from bpel to bpel-old, do we need bpel-old ?
by Max Rydahl Andersen
hi,
Checking the history of jbosstools-bpel I see that I just included bpel and not bpel-old which was present for a while.
Did bpel-old *ever* take part in any of our builds? do we need it in git history ?
I *assume* no, but since it was copied in svn instead of just deleted I would like to be sure.
To jock the memory here are the log entries that refer to bpel-old files:
commit 5bf2b587f35bf6c0c666c45a29831c95e78aebbd
Author: Nick Boldt <nboldt(a)redhat.com>
Date: Thu Nov 24 15:14:11 2011 +0000
bpel-old exists in the 3.3.0.M4 branch and is no longer needed in trunk. time to delete
git-svn-id: http://svn.jboss.org/repos/jbosstools/trunk@36618 a97e2381-89e5-4abb-bab3-167db6db766c
commit 4244eb44d3760d84021d47d651c237b691e1d1b3
Author: Nick Boldt <nboldt(a)redhat.com>
Date: Fri Oct 7 23:52:00 2011 +0000
fix copyrights - cannot be 'copyright JBoss by Red Hat, because the copyright holder is Red Hat, Inc. 'JBoss by Red Hat' is only the plugin/feature provider, not the copyright h
git-svn-id: http://svn.jboss.org/repos/jbosstools/trunk@35499 a97e2381-89e5-4abb-bab3-167db6db766c
commit ba24f65f993dc3651ce1f5f5134e2e1a66a449dc
Author: Nick Boldt <nboldt(a)redhat.com>
Date: Thu Sep 29 15:34:16 2011 +0000
to support migrating to Eclipse BPEL, bbrodt's requested and SVN move from bpel/ to bpel-old/, followed by a fresh start in bpel/ (JBDS-1810)
git-svn-id: http://svn.jboss.org/repos/jbosstools/trunk@35156 a97e2381-89e5-4abb-bab3-167db6db766c
/max
12 years, 1 month
[gitmigration] big file status
by Max Rydahl Andersen
I think I've found the biggest sinners of bad commits/files.
I've used the following checks:
Find top 10 big files: git verify-pack -v .git/objects/pack/pack-*.idx | grep blob | sort -k3nr | head | while read s x b x; do git rev-list --all --objects | grep $s | awk '{print "'"$b"'",$0;}'; done
Check for /target/ commits: git log --name-status | grep "/target/"
(and while typing this I realized I should go check for *.class commits too..)
Below is the current sizes for the resulting repos for those curious.
249M jbosstools-base Mainly all the jars from projecttemplates.
9.6M jbosstools-birt images for docs
23M jbosstools-bpel nothing special (except 300k large java file from BPEL package ;)
1.2M jbosstools-build nothing special
2.6M jbosstools-build-continous nothing special - only weird part is large log files like util/checkSVNArtifactVersions.sh_changesInM1_sinceJBT3.1.0.txt
1.8M jbosstools-build-sites nothing special
19M jbosstools-central jars and doc images
38M jbosstools-deltacloud jars and docs
201M jbosstools-documentation docs/images
43M jbosstools-forge jars from older versions
4.2M jbosstools-freemarker freemarker jars and old screenhots
11M jbosstools-gwt sample-hello-webContent.zip (expected)
355M jbosstools-hibernate doc.zip + hibernate jar updates
515M jbosstools-javaee doc.zip + test jars + doc builds resources.
48M jbosstools-jbpm docs build resources
38M jbosstools-jst test jars
204K jbosstools-maven-plugins fine
48M jbosstools-portlet jbds-compatilibity.zip + jsfportlet jars + accidental docs/target commits.
464K jbosstools-runtime-soa fine
123M jbosstools-server *tons* of target folder commits.(removed)
70M jbosstools-vpe contrib/org.mozilla.xulrunner.gtk.linux.x86_64_1.8.1.4-20080112.jar (removed) + org.jboss.tools.vpe.mozilla..*dll/so/jars (expected?)
43M jbosstools-webservices cpd-report.txt + test jars.
299M jbosstools-xulrunner libxul.so etc. (expected?)
/max
12 years, 1 month