January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19056: --------------------------------------------- Just replicated it on openshift too. {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.openshift.egit.core: Version have moved backwards for (org.jboss.tools.openshift.egit.core/2.6.1.Alpha1-v20150129-1651). Baseline has 2.6.100.Alpha1-v20150129-1643) with delta: 0.0.-99 -> [Help 1]{code} It definitely is looking on *local* filesystem and not *only* in the baseline. -1 for pushing this in until fixed. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19116: --------------------------------------------- I think as long as we don't have a better setup and using itests more broadly we continue run the full test suite to not miss them. But yes, we should look into not have them run every time. don't we already have a jira for that ? > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19056: ------------------------------------- {code} {code}INFO] --- repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) @ server.all --- [DEBUG] Configuring mojo org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines from plugin realm ClassRealm[plugin>org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT, parent: sun.misc.Launcher$AppClassLoader@5c647e05] [DEBUG] Configuring mojo 'org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines' with basic configurator --> [DEBUG] (f) baselines = [http://download.jboss.org/jbosstools/updates/stable/luna] [DEBUG] (f) project = MavenProject: org.jboss.tools:server.all:4.2.1-SNAPSHOT @ /home/rob/code/jbtools/github/jbosstools-server/pom.xml [DEBUG] -- end configuration -- > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19056: -------------------------------- Attachment: build.out > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19115: -------------------------------------- I guess marketplace means central in this context? > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-19115: ------------------------------------- If we are talking about Marketplace entries, then yes, we want the FH capabilities as part of the Hybrid Mobile Tools installation/option. > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19043) Error publishing jar inside utility project inside ear project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19043?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19043: ------------------------------------- yeah the idea is to : - create utility project *embedded* - create utility project *utility* - add *embedded* to *utility* deployment assembly (change to deploy-path="/jars/" in org.eclipse.wst.common.component, UI doesn't allow it) - create webapp - add *utility* to webapp deployment assembly - deploy. webapp. You should find /jars/embedded.jar within utility.jar, within webapp's WEB-INF/lib > Error publishing jar inside utility project inside ear project > -------------------------------------------------------------- > > Key: JBIDE-19043 > URL: https://issues.jboss.org/browse/JBIDE-19043 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.3.Beta1, 4.3.0.Beta1 > > > While verifying JBIDE-18862 I wanted to have some really big file to deploy so that I could see is an existing *.dodeploy marker is removed before the copying begins. > So I created an ear project with a nested dynamic web project and utility project. Inside this utility project's src dir I copied JBDS installer jar. Then I tried to deploy the ear to a WildFly 8.2 server (both stopped and running). > It seemed to work, the utility jar had 574 MB. But the tooling showed me this error: > Publishing to wildfly has encountered a problem: > {code} > Error renaming /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/tmp/tmp582268190747176162.jar to /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {code} > It's true that this was on a different FS, but both the tmp and deploy dirs were one FS, so that should be fine. > And just to be sure, I tried the same on the same FS and the error was the same: > {code} > Error renaming /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/tmp/tmp7876542570838575938.jar to /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19056: --------------------------------------------- [~rob.stryker] there should not be any 3.6.0.Alpha1 in the baseline since the baseline should be set to be stable/luna. That is definitely wrong. I agree with your concern. Can you run `mvn -X verify -DskipTests` where it failed and check that the baseline it actually uses. Should have something like this: {code} [INFO] --- repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) @ plugins --- [DEBUG] Configuring mojo org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines from plugin realm ClassRealm[plugin>org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT, parent: sun.misc.Launcher$AppClassLoader@23137792] [DEBUG] Configuring mojo 'org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines' with basic configurator --> [DEBUG] (f) baselines = [http://download.jboss.org/jbosstools/updates/stable/luna] [DEBUG] (f) project = MavenProject: org.jboss.tools.openshift:plugins:2.6.100-SNAPSHOT @ /Users/max/code/jbosstools/jbosstools-openshift/plugins/pom.xml [DEBUG] -- end configuration -- {code} Notice the (f) baselines If it does not fail for you try build master first then branch since it looks like some p2 lookup gets mixed up with master content. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19115: -------------------------------------- I imagine, we want it to be installed as "JBoss Hybrid Mobile Tools + CordovaSim". > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Gorkem Ercan edited comment on JBIDE-19115 at 1/29/15 11:28 AM: ---------------------------------------------------------------- I imagine, we want it to be installed as part of "JBoss Hybrid Mobile Tools + CordovaSim". was (Author: gercan): I imagine, we want it to be installed as "JBoss Hybrid Mobile Tools + CordovaSim". > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 January 2015