Hi guys,
it seems that importing some cloud JIRA issues into a JIRA server is
quite a burden. The process is mainly manual, with a lot of steps to
follow (see
https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server).
At this point, we have a choice to make. We can
Hi Shawn,
we might have to import the accelerator project too. It's implicitely
called in the ApacheDsDataProvider class :
System.setProperty(
StandaloneLdapApiService.EXTENDED_OPERATIONS_LIST,
org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory,
It does sound reasonable. And given that you two know about all the issues
in the Cloud JIRA you can point creators of issues in the new JIRAs to the
equivalent so that content can be references.
Depending of course on how long the Cloud JIRA will exists.
Regards,
Pierre Smits
*ORRTIZ.COM
[
https://issues.apache.org/jira/browse/DIRSERVER-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181288#comment-14181288
]
Paul Simpkins commented on DIRSERVER-2009:
--
Hi there,
I have been able to
On 10/23/2014 03:25 AM, Emmanuel Lécharny wrote:
Hi Shawn,
we might have to import the accelerator project too. It's implicitely
called in the ApacheDsDataProvider class :
It's also used in the AcceleratorDAO class :
what's your take on that ?
I'm not opposed but don't believe it is
On 10/23/2014 03:35 AM, Pierre Smits wrote:
It does sound reasonable. And given that you two know about all the issues in
the Cloud JIRA you can point creators of issues in the new JIRAs to the
equivalent so that content can be references.
Depending of course on how long the Cloud JIRA
Le 23/10/14 15:44, Shawn McKinney a écrit :
On 10/23/2014 03:25 AM, Emmanuel Lécharny wrote:
Hi Shawn,
we might have to import the accelerator project too. It's implicitely
called in the ApacheDsDataProvider class :
It's also used in the AcceleratorDAO class :
what's your take on that ?
Le 23/10/14 15:55, Shawn McKinney a écrit :
On 10/23/2014 03:35 AM, Pierre Smits wrote:
It does sound reasonable. And given that you two know about all the issues
in the Cloud JIRA you can point creators of issues in the new JIRAs to the
equivalent so that content can be references.
Le 23/10/14 15:55, Shawn McKinney a écrit :
On 10/23/2014 03:35 AM, Pierre Smits wrote:
It does sound reasonable. And given that you two know about all the issues
in the Cloud JIRA you can point creators of issues in the new JIRAs to the
equivalent so that content can be references.
On 10/23/2014 01:46 PM, Emmanuel Lécharny wrote:
Infra suggest that we upload the existing issues into a text file, that
is stored on our web site. This could be a good way to mitigate with the
current problem.
wdyt ?
That would be fine.
On 10/23/2014 01:47 PM, Emmanuel Lécharny wrote:
I'm also thinking that we need to reflect the project past life on the
fortress front page. We would need a big of history there... Shawn ?
Good idea. How about a link on the fortress page to the project history?
Le 23/10/14 21:17, Shawn McKinney a écrit :
On 10/23/2014 01:46 PM, Emmanuel Lécharny wrote:
Infra suggest that we upload the existing issues into a text file, that
is stored on our web site. This could be a good way to mitigate with the
current problem.
wdyt ?
That would be fine.
Ok,
Emmanuel Lecharny created FC-1:
--
Summary: Complete teh removal of the UnboundId library
Key: FC-1
URL: https://issues.apache.org/jira/browse/FC-1
Project: FORTRESS-CORE
Issue Type: Task
13 matches
Mail list logo
