December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18899: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18899: ------------------------------- Fix Version/s: 4.2.x > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18876: ------------------------------------ Assigning to Denis to suggest an alternative to the process described by Mickael. > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18876: ---------------------------------- Assignee: Denis Golovin > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18876: ------------------------------- Fix Version/s: 4.3.0.Alpha1 > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3265) Unable to create bottom up web service from EJB project

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3265?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3265: ----------------------------- Fix Version/s: 8.0.2.GA > Unable to create bottom up web service from EJB project > ------------------------------------------------------- > > Key: JBDS-3265 > URL: https://issues.jboss.org/browse/JBDS-3265 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration, webservices > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Fix For: 8.0.2.GA > > > This was created from community post [1]. I reproduced the issue locally using JBDS 8.0.0.GA. > I have an EJB project (EJB-A) and Dynamic Web Project (Web-A). > EJB-A is on the project classpath for Web-A. When trying to create the WSDL from the EJB I get the error > Error: Could not load class [ejbwstest.AccountServiceBean]. Did you specify a valid --classpath? > [1] https://developer.jboss.org/thread/250797 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3265) Unable to create bottom up web service from EJB project

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3265?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3265: ----------------------------- CDW pm_ack: ? (was: +) > Unable to create bottom up web service from EJB project > ------------------------------------------------------- > > Key: JBDS-3265 > URL: https://issues.jboss.org/browse/JBDS-3265 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration, webservices > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Fix For: 8.0.2.GA > > > This was created from community post [1]. I reproduced the issue locally using JBDS 8.0.0.GA. > I have an EJB project (EJB-A) and Dynamic Web Project (Web-A). > EJB-A is on the project classpath for Web-A. When trying to create the WSDL from the EJB I get the error > Error: Could not load class [ejbwstest.AccountServiceBean]. Did you specify a valid --classpath? > [1] https://developer.jboss.org/thread/250797 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3265) Unable to create bottom up web service from EJB project

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3265?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3265: ----------------------------- Target Release: 8.0.2.GA (was: 8.0.1.GA) > Unable to create bottom up web service from EJB project > ------------------------------------------------------- > > Key: JBDS-3265 > URL: https://issues.jboss.org/browse/JBDS-3265 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration, webservices > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Fix For: 8.0.2.GA > > > This was created from community post [1]. I reproduced the issue locally using JBDS 8.0.0.GA. > I have an EJB project (EJB-A) and Dynamic Web Project (Web-A). > EJB-A is on the project classpath for Web-A. When trying to create the WSDL from the EJB I get the error > Error: Could not load class [ejbwstest.AccountServiceBean]. Did you specify a valid --classpath? > [1] https://developer.jboss.org/thread/250797 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18872: ------------------------------- Fix Version/s: 4.2.2.Final > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Fix For: 4.2.2.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18872: ---------------------------------- Assignee: Xavier Coulon > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.2.2.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

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 December 2014