[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:03 PM:
-----------------------------------------------------------
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 \
-DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 \
-DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ \
-DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml \
-DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio \
-data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 \
-vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
was (Author: nickboldt):
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:04 PM:
-----------------------------------------------------------
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 \
-DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository \
-DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml \
-DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
{code}
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site.
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/discovery-site/
{code}
was (Author: nickboldt):
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site.
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/discovery-site/
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:03 PM:
-----------------------------------------------------------
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
was (Author: nickboldt):
PR 104: fixes the readme (simpler)
PR 105: fixes readme and verifies that Fuse can be installed using this override.
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 4:07 PM:
-----------------------------------------------------------
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site.
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/discovery-site/
{code}
was (Author: nickboldt):
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch 2 local nanohttpd servers [1] to host both the directory.xml / discovery plugin, and the Discovery composite site. Put each on a different port. _In future, we ought to simplify this so that the output of the build is a single folder, which can be more easily hosted._
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/plugins
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/discovery-site
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8081
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-159) JBoss Central discovery installer fails - JBDSIS 7.0.1
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-159:
--------------------------------
Summary: JBoss Central discovery installer fails - JBDSIS 7.0.1
Key: JBTIS-159
URL: https://issues.jboss.org/browse/JBTIS-159
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.1-JBDS
Reporter: Paul Leacu
Assignee: Len DiMaggio
Need to test more than just the p2 installer. The Mylyn Discovery JBoss Central installer should give you the same results.
i.e. (JBTIS - community)
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/integration/integration-stack/4.1.2/jbosstools-integration-stack-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/integration/integration-stack/4.1.2/
for JBDSIS (devstudio) - substitute: https://devstudio.jboss.com/updates/7.0-development/integration-stack/
JBoss Central>Software/Update
--
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
12 years, 7 months