March 2013 - jbosstools-issues - Jboss List Archives

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13408: ---------------------------------------- This is still SNAPSHOTs, and parent pom still reference last release. We'll send a mail when parent pom will be changed to use the new SNAPSHOT of TP with a sum up of applied and upcoming changes. > 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: Mickael Istria > 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11065: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-sites/pull/39 First pull request https://github.com/jbosstools/jbosstools-build-sites/pull/39 removes redundant steps from build.xml. > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-3628: -------------------------------------------- Ah didnt realize the data on this- thanks Rob ;) Thus I went and looked in our 7 alpha what the state is: max@slowbeard: $ find . -maxdepth 1 -type d | grep *jboss* /Applications/jbdevstudio7alpha1/studio/plugins grep: org.jboss.ide.eclipse.archives.core_3.4.100.Alpha1-v20130217-1728-B11: Is a directory grep: org.jboss.ide.eclipse.freemarker_1.3.0.Final-v20130207-2332-B83: Is a directory grep: org.jboss.tools.common.gef_3.5.0.Alpha1-v20130216-0701-B10: Is a directory grep: org.jboss.tools.common.model.ui_3.5.0.Alpha1-v20130216-0701-B10: Is a directory grep: org.jboss.tools.common.model_3.5.0.Alpha1-v20130216-0701-B10: Is a directory grep: org.jboss.tools.common.projecttemplates_3.5.0.Alpha1-v20130216-0701-B10: Is a directory grep: org.jboss.tools.forge.runtime.ext_1.2.0.Alpha1-v20130216-0716-B10: Is a directory grep: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130216-0716-B10: Is a directory grep: org.jboss.tools.hibernate.ui_3.7.0.Alpha1-v20130216-0715-B7: Is a directory grep: org.jboss.tools.hibernate4_0_3.7.0.Alpha1-v20130216-0715-B7: Is a directory grep: org.jboss.tools.jsf.vpe.ajax4jsf_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.facelets_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.jbpm_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.jsf_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.jstl_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.myfaces_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.richfaces_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jsf.vpe.seam_3.5.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.jst.web.kb_3.5.0.Alpha1-v20130211-2005-B3: Is a directory grep: org.jboss.tools.struts.vpe.struts_3.4.0.Alpha1-v20130214-1356-B6: Is a directory grep: org.jboss.tools.vpe.docbook_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.html_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.jsp_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.resref_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.spring_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.ui.palette_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe.xulrunner_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.vpe_3.5.0.Alpha1-v20130218-1313-B9: Is a directory grep: org.jboss.tools.xulrunner.initializer_3.5.0.Alpha1-v20130218-1313-B9: Is a directory Out of these I believe the following has no reason to be exploded: org.jboss.ide.eclipse.* org.jboss.tools.common* org.jboss.tools.jsf.vpe* org.jboss.tools.struts.* org.jboss.tools.vpe* The xulrunner, hibernate and forge are dirs because of the jar library they contain (would have to be unzipped constantly) > Plugins should be .jar's not directories for efficiency sake > ------------------------------------------------------------ > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.1.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. TBD -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2486: ------------------------------------------- does the google plugins not work on kepler? > Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central > ----------------------------------------------------------------- > > Key: JBDS-2486 > URL: https://issues.jboss.org/browse/JBDS-2486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 7.0.0.Alpha2 > > > New 3.2.0 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-... > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/ > Note that at least one IU had been renamed: > OLD: com.google.gwt.eclipse.sdkbundle.e42.feature > NEW: com.google.gwt.eclipse.sdkbundle.feature -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13338) BrowserSim: integrate weinre functionality to BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13338?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov resolved JBIDE-13338. -------------------------------------------- Resolution: Done Functionality is implemented, will be available in alpha2. > BrowserSim: integrate weinre functionality to BrowserSim > -------------------------------------------------------- > > Key: JBIDE-13338 > URL: https://issues.jboss.org/browse/JBIDE-13338 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: example.png, weinre.bmml, weinre.png > > > It will be good to have debug capabilities in browserSim. Weinre can provide it. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13338) BrowserSim: integrate weinre functionality to BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13338?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-13338: ------------------------------------------------ Oh, sorry, my fault. I forgot to change resolution when resolve issue here. > BrowserSim: integrate weinre functionality to BrowserSim > -------------------------------------------------------- > > Key: JBIDE-13338 > URL: https://issues.jboss.org/browse/JBIDE-13338 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: example.png, weinre.bmml, weinre.png > > > It will be good to have debug capabilities in browserSim. Weinre can provide it. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13338) BrowserSim: integrate weinre functionality to BrowserSim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13338?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13338: ---------------------------------------- Labels: new_and_noteworthy (was: ) > BrowserSim: integrate weinre functionality to BrowserSim > -------------------------------------------------------- > > Key: JBIDE-13338 > URL: https://issues.jboss.org/browse/JBIDE-13338 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > Attachments: example.png, weinre.bmml, weinre.png > > > It will be good to have debug capabilities in browserSim. Weinre can provide it. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13766) org.jboss.tools.maven.profiles.ui doesn't export all packages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13766?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13766: --------------------------------------------- okey - but why does arquillian tooling have to know about maven profiles ? arquillian tooling should not care about maven. > org.jboss.tools.maven.profiles.ui doesn't export all packages > ------------------------------------------------------------- > > Key: JBIDE-13766 > URL: https://issues.jboss.org/browse/JBIDE-13766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > Some classes from those packages are required by the arquillian feature. -- 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

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13408: --------------------------------------------- A) if we are having changes to target platform every week something is very wrong :) B) he can easily use a specific target platform locally - no need to push that into every other build. C) we don't want to add in things that are obviously wrong to do - i.e. adding jmock and other testing libs to the target platform isn't something that should just be done within few hours; nor is removing jetty and adding a new one, nor is adding/updating zest.... That said i'm fine providing snapshots builds with changes, but just send out the email when the suggested TP changes and which changes are coming - don't move the used TPC by the build up to this immediately. > 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: Mickael Istria > 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

13 years

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12973: ---------------------------------------- > the last build didn't publish anything to http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ because there were no changes in git. You can ignore the git change for a single build: When you hit the "Run" button of you job, you see a configuration page. On this page, there is a "skipRevisionCheckWhenPublishing" checkbox, just tick it if you want to force publishing. > 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-tools, 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013