January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13460: ---------------------------------- Summary: test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project) Key: JBIDE-13460 URL: https://issues.jboss.org/browse/JBIDE-13460 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, Seam 2 Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 4.1.0.Alpha1 {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/} Test Result 2 failures (-7) 2,118 tests (-171) Took 53 min. add description All Failed Tests Test Name Duration Age >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4 >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25 {code} Note that we've had considerably more tests complete in the past: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure) https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13459) 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13459: ---------------------------------- Summary: 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform Key: JBIDE-13459 URL: https://issues.jboss.org/browse/JBIDE-13459 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 4.1.0.Alpha1 {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/165/testReport/} Failing for 6 builds (age = 6): Test Name Duration Age >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[60] 3.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[61] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[62] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[63] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[64] 2.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[65] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[66] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[67] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[68] 2.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[69] 2.9 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[70] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[71] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[72] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[73] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[74] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[75] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[76] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[77] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[78] 2.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[79] 2.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[80] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[81] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[82] 2.3 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[83] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[84] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[85] 2.9 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[86] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[87] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[88] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[89] 2.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[60] 3.4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[61] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[62] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[63] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[64] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[65] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[66] 4.1 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[67] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[68] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[69] 4.7 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[70] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[71] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[72] 4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[73] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[74] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[75] 4.1 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[76] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[77] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[78] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[79] 4 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[80] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[81] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[82] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[83] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[84] 3.5 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[85] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[86] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[87] 3.6 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[88] 4.2 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[89] 3.7 sec 6 >>> org.jboss.tools.as.test.core.parametized.server.XPathModelTest.serverTestImpl[0] 15 ms 6 >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 2 ms 6 >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 1 ms 6 >>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[11] 20 ms 6 {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-12973: ---------------------------------- Assignee: Martin Malina (was: Nick Boldt) Job simply copies from staging/{JOB_NAME} to a new location. It doesn't rebuild, refactor, or relabel. It will however *replace* an existing build folder w/ new content, so you can overwrite your 0.2.0.Final folder when you respin. I'm not 100% sure whether it merges in or wipes clean before republishing, but it doesn't really matter because when you're satisfied w/ your builds enough to call it Final, that CI-built nightly can simply be pushed to /stable/ instead of /development/ or /integration/ and we can manually delete the old cruft. If you prefer to have uniquely names folders, consider using BUILD_NUMBER in the target folder... eg., 0.2.0.CI-${BUILD_NUMBER} > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13408: ------------------------------------ OK, from what I've read there are a number of things we need to do (and a number of possible URLs to try when deploying): a) add license and other metadata to the target platform poms: https://community.jboss.org/wiki/MavenProjectConfigurationRequirements - see *POM template* b) hope that Jenkins can push there w/o me having to hardcode my jboss.org username/password into the settings.xml file - https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Deploy to JBoss Repository* c) add staging URL for public JBoss nexus to settings.xml used by Jenkins (per https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Configuring Maven to use the JBoss Repository*) * http://repository.jboss.org/nexus/content/groups/public/ instead of * https://repository.jboss.org/nexus/content/repositories/releases/ d) alternatively, can also try deploying like this: {code} -DrepositoryId=jboss-releases-repository -Durl=https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/ {code} or using https://repository.jboss.org/nexus/content/groups/staging/ > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13408 at 1/31/13 3:10 PM: ------------------------------------------------------------- OK, from what I've read there are a number of things we need to do (and a number of possible URLs to try when deploying): a) add license and other metadata to the target platform poms: https://community.jboss.org/wiki/MavenProjectConfigurationRequirements - see *POM template* b) hope that Jenkins can push there w/o me having to hardcode my jboss.org username/password into the settings.xml file - https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Deploy to JBoss Repository* c) add staging URL for public JBoss nexus to settings.xml used by Jenkins (per https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Configuring Maven to use the JBoss Repository*) * http://repository.jboss.org/nexus/content/groups/public/ instead of * https://repository.jboss.org/nexus/content/repositories/releases/ d) alternatively, can also try deploying like this (per https://community.jboss.org/wiki/MavenDeployingARelease - see *Deploying a non Maven Project*): {code} -DrepositoryId=jboss-releases-repository -Durl=https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/ {code} or using https://repository.jboss.org/nexus/content/groups/staging/ was (Author: nickboldt): OK, from what I've read there are a number of things we need to do (and a number of possible URLs to try when deploying): a) add license and other metadata to the target platform poms: https://community.jboss.org/wiki/MavenProjectConfigurationRequirements - see *POM template* b) hope that Jenkins can push there w/o me having to hardcode my jboss.org username/password into the settings.xml file - https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Deploy to JBoss Repository* c) add staging URL for public JBoss nexus to settings.xml used by Jenkins (per https://community.jboss.org/wiki/MavenGettingStarted-Developers - see *Configuring Maven to use the JBoss Repository*) * http://repository.jboss.org/nexus/content/groups/public/ instead of * https://repository.jboss.org/nexus/content/repositories/releases/ d) alternatively, can also try deploying like this: {code} -DrepositoryId=jboss-releases-repository -Durl=https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/ {code} or using https://repository.jboss.org/nexus/content/groups/staging/ > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13454) Provide different palettes for pages in JSF and non-JSF projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13454?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13454: ----------------------------------- Description: If we open a file from the project with JSF nature then we should show the old palette. Otherwise we should show the new one. It's actually the same view (General->Palette) but different content. We are going to implement a "mobile" palette for non-jsf projects. > Provide different palettes for pages in JSF and non-JSF projects > ---------------------------------------------------------------- > > Key: JBIDE-13454 > URL: https://issues.jboss.org/browse/JBIDE-13454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.0.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.Alpha1 > > > If we open a file from the project with JSF nature then we should show the old palette. > Otherwise we should show the new one. > It's actually the same view (General->Palette) but different content. > We are going to implement a "mobile" palette for non-jsf projects. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13408: ------------------------------- Priority: Blocker (was: Major) > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13413: ---------------------------------------- Thanks, Yahor. > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > Attachments: CSS-Preview.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, withwithoutpreview.bmml, withwithoutpreview.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-14) generate index page for JBTIS aggregate site, and discard extra-repos.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-14?page=com.atlassian.jira.plugin.s... ] Nick Boldt reassigned JBTIS-14: ------------------------------- Assignee: Paul Leacu Paul, here's a PR for what we talked about today - generating an index page for your aggregate site. > generate index page for JBTIS aggregate site, and discard extra-repos.xml > ------------------------------------------------------------------------- > > Key: JBTIS-14 > URL: https://issues.jboss.org/browse/JBTIS-14 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution, releng > Reporter: Nick Boldt > Assignee: Paul Leacu > > generate index page for JBTIS aggregate site, and discard extra-repos.xml -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-14) generate index page for JBTIS aggregate site, and discard extra-repos.xml

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-14: ------------------------------- Summary: generate index page for JBTIS aggregate site, and discard extra-repos.xml Key: JBTIS-14 URL: https://issues.jboss.org/browse/JBTIS-14 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: distribution, releng Reporter: Nick Boldt generate index page for JBTIS aggregate site, and discard extra-repos.xml -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013