[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13599 at 3/13/13 1:34 PM:
-------------------------------------------------------------
Does not appear to be working.
Steps to repro:
1. Build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. Apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. Build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5. Install JBDS you just built.
6. Edit its jbdevstudio.ini file, setting these -D flags:
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/
{code}
7. Launch JBDS:
{code}
./jbdevstudio -consolelog -debug
{code}
8. Open the Software/Updates tab in Central. For all the entries with
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core/}
you will see no connectors listed. Only Android and JRebel will be shown.
was (Author: nickboldt):
Does not appear to be working.
Steps to repro:
1. build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13599:
-------------------------------
Attachment: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
Does not appear to be working.
Steps to repro:
1. build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2497:
--------------------------------------
pack200 profile was removed from CI job and will be re-enabled once we migrate to Tycho 0.17.
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years
[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-2497:
---------------------------------
Fix Version/s: 7.0.x
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 7.0.x
>
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years
[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-2497:
---------------------------------
Component/s: Build
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 7.0.x
>
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years
[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2497:
--------------------------------------
So this is pending on release of Tycho 0.17, good news.
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years
[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2497:
-----------------------------
Assignee: Mickael Istria
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years