[
https://issues.jboss.org/browse/JBDS-2490?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-2490 at 4/6/13 7:54 PM:
----------------------------------------------------------
Unless we plan to build more 3.3.x (5.0.x) or 4.0.x (6.0.x) releases, then 3.3.x (5.0.x)
and 4.0.x (6.0.x) are (for now) done maintenance. That may change and prompt the need to
potentially backport this later. But I'm not going to do it proactively *_just in
case_* we decide to do a release later, since there's an existing (if imperfect)
workflow in place already for manually rebuilding discovery plugins for 3.3.x (5.0.x) and
4.0.x (6.0.x) releases.
Therefore, here are the sources for the various maintenance/development streams:
In 3.3.x, 2 SVN repos:
https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/...
http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plu...
In 4.0.x, 1 github repo + 1 SVN repo:
https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce...
http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu...
In 4.1.x, 1 github repo:
https://github.com/jbosstools/jbosstools-discovery
[~maxandersen] Does that work?
was (Author: nickboldt):
Unless we plan to build more 3.3.x (5.0.x) or 4.0.x (6.0.x) releases, then 3.3.x
(5.0.x) and 4.0.x (6.0.x) are (for now) done maintenance. That may change and prompt the
need to potentially backport this later. But I'm not going to do it proactive just in
case we decide to do a release later, since there's an existing (if imperfect)
workflow in place already for manually rebuilding discovery plugins for 3.3.x (5.0.x) and
4.0.x (6.0.x) releases.
Therefore, here are the sources for the various maintenance/development streams:
In 3.3.x, 2 SVN repos:
https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/...
http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plu...
In 4.0.x, 1 github repo + 1 SVN repo:
https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce...
http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu...
In 4.1.x, 1 github repo:
https://github.com/jbosstools/jbosstools-discovery
[~maxandersen] Does that work?
migrate JBT and JBDS discovery plugins to new github repo,
jbosstools-discovery
-------------------------------------------------------------------------------
Key: JBDS-2490
URL:
https://issues.jboss.org/browse/JBDS-2490
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: central
Affects Versions: 7.0.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 7.0.0.Alpha2
Migrate 2 -3- branches of git sources (including history):
https://github.com/jbosstools/jbosstools-central/tree/master/central/plug...
https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.1.0.Al...
OMIT:
https://github.com/jbosstools/jbosstools-central/tree/jbosstools-4.0.x/ce...
and 2 -3- branches of svn sources (including history):
http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds...
http://svn.jboss.org/repos/devstudio/branches/devstudio-7.0.0.Alpha1/prod...
OMIT:
http://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plu...
to a new Github project called "jbosstools-discovery" under which there would
be:
* jbdevstudio/com.jboss.jbds.central.discovery/
* jbosstools/org.jboss.tools.central.discovery/
--
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