[JBoss JIRA] (JBIDE-12926) CLONE - missing empty folders after migration of hibernatetools (svn) to jbosstools-hibernate (git)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12926:
----------------------------------
Summary: CLONE - missing empty folders after migration of hibernatetools (svn) to jbosstools-hibernate (git)
Key: JBIDE-12926
URL: https://issues.jboss.org/browse/JBIDE-12926
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.0.0.CR1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.0.CR1
Attachments: missing-empty-folders-after-esb-migrated-to-github.png
See attached image comparing old SVN tunk sources on the left w/ new Github sources on the right:
!missing-empty-folders-after-hibernatetools-migrated-to-hibernate.png!
Note that differences in pom.xml are due to refactoring I did - not a problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12475) Split JBoss Tools into several functional groups of components for migration to Github
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12475:
----------------------------------
Summary: Split JBoss Tools into several functional groups of components for migration to Github
Key: JBIDE-12475
URL: https://issues.jboss.org/browse/JBIDE-12475
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.M1
As part of the planned migration to git [0] it's been suggested that we combine some of the existing components into larger groups [1] so that it's more manageable in terms of checking out sources and tagging/branching [2].
Because 25 is a large number, and 1 is a small number, and we need some happy compromise.
Here's my proposal for how to divide the JBT 4.0 sources into 7 github repos (chunks), comprising 4 tiers of dependency. This is akin to the +0, +1, +2, +3 labels assigned to projects within the annual Eclipse release trains [3], used to define delivery times based on dependencies between projects.
== TIER 0: no upstream JBoss.org chunks ==
Base = tests + common + usage
== TIER 1: 1 upstream chunk, Base ==
AppServer = openshift + as + archives + jmx
-> depends on Base
Hibernate/Birt/Freemarker = hibernate + birt + freemarker
-> depends on Base
Visual Editing = vpe + xulrunner + gwt + struts + jsf + jst + cdi
-> depends on Base
Web Services = WS + Forge
-> Depends on Base
== TIER 2: 4 upstream chunks ==
Seam/Runtime = Seam + Runtime
-> depends on Hib + Vis + AppServer + Base
== TIER 3: 5 upstream chunks ==
Central/Examples/Maven/Portlet = central + examples + maven + portlet
-> depends on Seam/Runtime + Hib + Vis + AppServer + Base
I'm not thrilled with the names of the chunks, as something like "Central/Examples/Maven/Portlet" doesn't exactly roll off the tongue. If you have better names for the chunks, please suggest them.
But regardless of name, I think the above separation of concerns, and the implied build sequence workflow makes a lot of sense.
[0] http://tinyurl.com/git-migration-plan
[1] http://ether-man.rhcloud.com/p/build.next
[2] http://ether-man.rhcloud.com/p/jbosstools-2012-08-23
[3] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... - "These delivery times are based on the dependencies between projects. They are labeled +0, +1, +2, and +3, with +0 coming first (the Platform) and +3 coming last (EPP). Projects themselves decide if they are +0, +1, +2, or +3."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12844) VPE tests slowing with time
by Yahor Radtsevich (JIRA)
Yahor Radtsevich created JBIDE-12844:
----------------------------------------
Summary: VPE tests slowing with time
Key: JBIDE-12844
URL: https://issues.jboss.org/browse/JBIDE-12844
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core, Visual Page Editor Templates
Affects Versions: 4.0.0.Alpha2
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Fix For: 4.0.0.CR1
When VPE tests are run, every next test is executed slower and slower.
Looks like there is a resource leak.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12773) Create a hudson.target and use it on CI
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12773:
--------------------------------------
Summary: Create a hudson.target and use it on CI
Key: JBIDE-12773
URL: https://issues.jboss.org/browse/JBIDE-12773
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng, target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Instead of relying on profiles to use the local mirror of TP, we could create and use a hudson.target which would simply be a copy of unified.target, but using a different URL.
Then jobs could use it, and we'd finally use target-platforms on CI!
As soon as Tycho 0.16 is resolved, we can replace this hudson.target by Tycho repository mirroring.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months