7:14 a.m.
Migrate CVS source repository to SVN
------------------------------------
Key: BPEL-307
URL: https://jira.jboss.org/jira/browse/BPEL-307
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled environtments
where outside access is only possible through a HTTP proxy the CVS repository is
inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
--
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
2:53 a.m.
New subject: [JBoss JIRA] Commented: (BPEL-307) Migrate CVS source repository to SVN
[
https://jira.jboss.org/jira/browse/BPEL-307?page=com.atlassian.jira.plugi...
]
Aleksander Adamowski commented on BPEL-307:
-------------------------------------------
BTW, it turns out that the CVS repository is empty now! When checking out using the CVS
parameters documented under the aforementioned link, one gets a directory structure where
the only files are CVS metadata!
It seems that at some point in time someone got the jBPM-BPEL sources migrated to SVN
together with all of jBPM (JBPM-1197 ?).
The problem is, they are in several distinct places and aren't connected in terms of
SVN history - like if they were imported manually, separately by different people at
different points in time.
I've found two locations where the BPEL sources reside, but there may be more:
http://anonsvn.jboss.org/repos/jbpm/legacy/tempranillo/bpel/trunk
http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jpdl-3.2.3.CP/bpel
In this situation it's really hard to find the exact place where the trunk of the
development happens (or should happen if it would) and to make patches against.
Migrate CVS source repository to SVN
------------------------------------
Key: BPEL-307
URL: https://jira.jboss.org/jira/browse/BPEL-307
Project: jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled
environtments where outside access is only possible through a HTTP proxy the CVS
repository is inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
--
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
5:02 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-307) Migrate CVS source repository to SVN
[
https://jira.jboss.org/jira/browse/BPEL-307?page=com.atlassian.jira.plugi...
]
Alejandro Guizar updated BPEL-307:
----------------------------------
Fix Version/s: jBPM BPEL 1.1.1
Description:
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled environtments
where outside access is only possible through a HTTP proxy the CVS repository is
inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
was:
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled environtments
where outside access is only possible through a HTTP proxy the CVS repository is
inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
Migration to SVN was already done in 1.1.1. Instructions for building from source are
available at http://www.jboss.org/community/wiki/BuildjBPMBPELfromsource
Migrate CVS source repository to SVN
------------------------------------
Key: BPEL-307
URL: https://jira.jboss.org/jira/browse/BPEL-307
Project: jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
Fix For: jBPM BPEL 1.1.1
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled
environtments where outside access is only possible through a HTTP proxy the CVS
repository is inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
--
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
noon
New subject: [JBoss JIRA] Commented: (BPEL-307) Migrate CVS source repository to SVN
[
https://jira.jboss.org/jira/browse/BPEL-307?page=com.atlassian.jira.plugi...
]
Aleksander Adamowski commented on BPEL-307:
-------------------------------------------
Just for the record, as Alejandro responded in BPEL-313, the most recent sources for
jBPM-BPEL are located at http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/bpel-1.2/ .
Alejandro, please, update the official information on
http://jboss.org/jbossjbpm/bpel_sources/ - it still points to the CVS, which is empty now.
Also, place a link there to the building instructions on the wiki. This information needs
to be fresh if contributors are to work on BPEL sources.
Migrate CVS source repository to SVN
------------------------------------
Key: BPEL-307
URL: https://jira.jboss.org/jira/browse/BPEL-307
Project: jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
Fix For: jBPM BPEL 1.1.1
The jBPM-BPEL sources are hard to find because, unlike almost all other JBoss projects
(including jBPM), they are not hosted in SVN on the main JBoss server
(http://svn.jboss.org/repos/).
The page http://jboss.org/jbossjbpm/bpel_sources/ gives info about how to check out the
sources from CVS.
However, this requires outgoing access to port 2401 and from some firewalled
environtments where outside access is only possible through a HTTP proxy the CVS
repository is inaccessible. Also, CVS is a version control system vastly inferior to SVN.
Therefore, JBoss jBPM-BPEL source repository should be migrated to SVN.
--
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
6134
days inactive
6222
days old
3 comments
2 participants
participants (2)
-
Alejandro Guizar (JIRA) -
Aleksander Adamowski (JIRA)