[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-15398:
-----------------------------------------------
After the fix, the clean/build of the entire wildfly workspace completes in 5 minutes.
Fred, will you please try the pull request in your environment?
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15482:
------------------------------------
Publishing w/ the jbosstools-promote job (or your own version of promote.sh) will work the same way but you'll have to put in the SPECIFIC build ID for the bits to copy.
Thus instead of *builds/staging/RedDeer_master/all/repo/* you would use *builds/staging/CI/RedDeer_master/<some_timestamp_and_build_ID>/all/repo/*
Or you can keep using the old system if you use the jbosstools-4.1.0.Final tag [1] instead of the master branch [2] of the script in your build job when initially publishing to /staging/.
[1] https://raw.github.com/jbosstools/jbosstools-build-ci/jbosstools-4.1.0.Fi...
[2] https://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publ...
Currently master and 4.1.0.Final tag are the same, but once I apply https://github.com/jbosstools/jbosstools-build-ci/pull/63 master will begin to push to multiple timestamped folders instead of the simpler staging and staging.previous pair of folders.
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate
by Juergen Zimmermann (JIRA)
Juergen Zimmermann created JBIDE-15488:
------------------------------------------
Summary: Web Service Tester doesn't work with https and self-signed certificate
Key: JBIDE-15488
URL: https://issues.jboss.org/browse/JBIDE-15488
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.0.Final
Reporter: Juergen Zimmermann
If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests):
{code}
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
{code}
--
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-171) Don't override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-171:
-----------------------------
Summary: Don't override other connectors in discovery.xml (was: dont override other connectors in discovery.xml)
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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-171) dont override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-171 at 9/12/13 10:47 AM:
------------------------------------------------------------
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always slash-escape your curly braces ( *\{* ) if you don't want JIRA to think they're the start of a macro. :D )
was (Author: nickboldt):
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always slash-escape your curly braces (\{) if you don't want JIRA to think it's a macro. :D )
> dont override other connectors in discovery.xml
> -----------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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-171) dont override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-171:
----------------------------------
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always \-escape your curly braces if you don't want JIRA to think it's a macro. :D )
> dont override other connectors in discovery.xml
> -----------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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-171) dont override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-171 at 9/12/13 10:46 AM:
------------------------------------------------------------
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always \\-escape your curly braces (\{) if you don't want JIRA to think it's a macro. :D )
was (Author: nickboldt):
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always \-escape your curly braces if you don't want JIRA to think it's a macro. :D )
> dont override other connectors in discovery.xml
> -----------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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-171) dont override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-171 at 9/12/13 10:47 AM:
------------------------------------------------------------
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always slash-escape your curly braces (\{) if you don't want JIRA to think it's a macro. :D )
was (Author: nickboldt):
[~maxandersen] The test site for JBDS IS 7.0.0.Beta1 is a composite directory.xml which includes both JBDS and JBDS IS plugins. The site is a composite one, which includes JBDS, JBDS TP, JBDS IS, and JBDS IS TP. So... you should be able to resolve ALL the connectors from JBDS and JBDS IS in the same Central view, and install any or all of them.
If you can't then something it seriously wrong in the state of Denmark. Please provide steps to reproduce your problem.
(And always \\-escape your curly braces (\{) if you don't want JIRA to think it's a macro. :D )
> dont override other connectors in discovery.xml
> -----------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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-171) dont override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-171:
-----------------------------
Description:
Currently this is in discovery plugin:
siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
And instructions to test it says:
-vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
I suggest you use your own specific site url instead, something like:
siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
Then the base connectors will still work.
We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
in stack:
siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
was:
Currently this is in discovery plugin:
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
And instructions to test it says:
-vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
I suggest you use your own specific site url instead, something like:
siteUrl="${jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
Then the base connectors will still work.
We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
in core: siteUrl="${jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
in stack:
siteUrl="${jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> dont override other connectors in discovery.xml
> -----------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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] (JBIDE-15487) Export Native Platform Project is not working
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15487?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-15487:
------------------------------------
Assignee: Gorkem Ercan
Do you also select a platform to export between step 2 & 3? Also anything on the logs?
> Export Native Platform Project is not working
> ---------------------------------------------
>
> Key: JBIDE-15487
> URL: https://issues.jboss.org/browse/JBIDE-15487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Alpha1
> Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.Alpha1
>
>
> 1. Create new Mobile Hybrid Project.
> 2. Select it and choose Export > Mobile > Export Native Platform Project
> 3. Click Next
> ERROR: Nothing happens
> 4. Click Next Again
> ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform"
--
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