[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Johnny Verhaeg updated JBIDE-5318: ---------------------------------- Description: The Eclipse-based client DNA publishing projects, currently hosted under https://svn.jboss.org/repos/dna/trunk/tools, need to be ported over to the JBoss Tools SVN repository (and removed from DNA's SVN repository) and included in the JBoss Tools build and distribution process. (was: The Eclipse-based client DNA publishing projects, currently hosted under https://svn.jboss.org/repos/dna/trunk/tools, need to be ported over to the JBoss Tools SVN repository (and removed from DNA's SVN repository)) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5318: ----------------------------------- FYI, you don't strictly have to have your sources in the same repo as the rest of JBT. For example, pi4soa is built from sources hosted on sourceforge.net. Do you need to retain history? (I would guess yes.) Does SVN have tools for cloning trees between disparate repos? (I assume so, but do they retain history?) And when would you want to do this migration? Is there a "shutdown" window during which time you can safely do the copy and tell all your devs to use the new repo? Perhaps between Dec 25 and Jan 01? Will you be responsible for notification of the change so that your team will all be able to continue work in the new repo (after a fresh workspace checkout, of course). --- Perhaps instead of moving DNA, you only move the Eclipse plugins (as per jira DNA-564) ? Then you can build the runtime, and the Eclipse plugins can be built downstream from that (ultimately as part of JBoss Tools). Does that make sense? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Randall Hauch commented on JBIDE-5318: -------------------------------------- First of all, this is a pretty new plugin that was developed on a separate branch and just recently merged (rather 'added') into trunk. I don't think that minimal history is worth keeping. Second, it's a pretty small plug-in that interacts with a DNA RESTful web service (just a deployable JAR). There's the main plugin project, plus a feature plugin and an updatesite plugin (see http://anonsvn.jboss.org/repos/dna/trunk/tools/). The main plugin does reuses some of the code in a few of the other Mavenized DNA modules, so the Eclipse plugin definitely has to be released after DNA has been released. Third, all of the other modules in DNA are Mavenized, so this doesn't really fit where it is and certainly doesn't fit within the build/release system. The purpose of DNA-564 was to move it outside of http://anonsvn.jboss.org/repos/dna/trunk/ so that it doesn't get tagged at the same time the Maven modules are. After all, the Eclipse plugin is and should be downstream. Fourth, we're going to be releasing DNA 0.7 in a week or two, and then quickly rebranding and releasing as "ModeShape" 1.0-beta-1 (hopefully a week later). It may not even be worth having the Eclipse plugin in a released state under DNA, but to instead rebrand it, move it to a new SVN home, and release it downstream of ModeShape 1.0-beta-1. Bottom line is this: We need to find a new home for it, and it seems like JBT SVN is just as good a place as any. However, if there are good reasons _not_ to do this, then we can certainly find a home outside of DNA/ModeShape SVN. There's not much history, so I think we'd all be fine with it being added without history in its new home and release it downstream of ModeShape 1.0-beta-1. WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-5318: --------------------------------------- Fix Version/s: 3.2.next -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5318: ----------------------------------- First build passed (but is red because of no test results). Re-running w/ expectation of tests removed from job config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5318: ----------------------------------- Also need to create an SDK feature to contain the source plugins/features, and decide which categori(es) you want your stuff posted on in the JBT update site. Here's the complete list of categories: https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Dan Florian commented on JBIDE-5318: ------------------------------------ I'll be working this instead of John. I just checked in an AllTests test suite class. Can you explain what you mean by needing an SDK feature? Currently there are 2 features: one for source and one for test. What should I include in this new SDK feature? Thanks for you help Nick. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5318: ----------------------------------- Just got your tests (40 of them) running via Tycho. Trying 'em in Athena next. Hudson is being hella slow so I may not be able to get this working tonight. :( To build w/ Tycho: cd /tmp; \ svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/; \ cd /tmp/build; \ ant -DCOMPONENTS=tests,common,modeshape -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-5318: ----------------------------------- Does Modeshape prereq JDK6? I ask because the rest of the JBT build currently runs w/ JDK5, not 6. These plugins state their preference for 6.0 ("Bundle-RequiredExecutionEnvironment: JavaSE-1.6"); is it really required or are you just using the default that PDE provides? plugins/org.jboss.tools.modeshape.rest/META-INF/MANIFEST.MF tests/org.jboss.tools.modeshape.rest.test/META-INF/MANIFEST.MF -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu... ] Dan Florian commented on JBIDE-5318: ------------------------------------ Checked in initial version of the SDK feature requested by Nick. Used the JMX SDK feature as an example. Let me know if you need any more changes. Thanks again Nick. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-5318?page=com.atlassian.jira.plugin.s... ] Dan Florian resolved JBIDE-5318. -------------------------------- Resolution: Done I moved the ModeShape Eclipse plugin to JBoss Tools SVN (https://svn.jboss.org/repos/jbosstools/trunk/modeshape/) quite some time ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira