January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13439) http://download.jboss.org/jbosstools/examples/ is out of date / missing content

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-13439: -------------------------------------- Affected examples: SOA: http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa... Teiid: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer... > http://download.jboss.org/jbosstools/examples/ is out of date / missing content > ------------------------------------------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) http://download.jboss.org/jbosstools/examples/ is out of date / missing content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13439: ------------------------------------ http://download.jboss.org/jbosstools/examples/README.html updated. Scroll to bottom of http://download.jboss.org/jbosstools/examples/ to see new content. > http://download.jboss.org/jbosstools/examples/ is out of date / missing content > ------------------------------------------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) http://download.jboss.org/jbosstools/examples/ is out of date / missing content

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13439: ---------------------------------- Summary: http://download.jboss.org/jbosstools/examples/ is out of date / missing content Key: JBIDE-13439 URL: https://issues.jboss.org/browse/JBIDE-13439 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Problem: a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. >> http://memegenerator.net/instance/33999035 << Solution: a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- 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, 2 months

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: --------------------------------------------- See https://community.jboss.org/wiki/MavenGettingStarted-Developers and https://community.jboss.org/wiki/MavenDeployingARelease Explore that and we can sync up if we are missing something. i.e. these releases should not have dependencies to other -snapshot releases or repositories. > 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 > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e

by Manosh C (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ] Manosh C updated JBIDE-13438: ----------------------------- Attachment: testparent.zip Attaching sample maven projects > jboss-packaging-maven-plugin jboss-esb + m2e > -------------------------------------------- > > Key: JBIDE-13438 > URL: https://issues.jboss.org/browse/JBIDE-13438 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: esb > Reporter: Manosh C > Assignee: Brian Fitzpatrick > Attachments: testparent.zip > > > Hi, > > Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now > > 1. Turn on facet nature and enable JBOSS ESB nature. > 2. Then it get recognized as a deployable artifact on JBoss server. > 3. Manually add all dependencies in "Deployment and Assembly section". > > What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported? > > Thank you in advance. > Manosh -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e

by Manosh C (JIRA)

Manosh C created JBIDE-13438: -------------------------------- Summary: jboss-packaging-maven-plugin jboss-esb + m2e Key: JBIDE-13438 URL: https://issues.jboss.org/browse/JBIDE-13438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Manosh C Assignee: Brian Fitzpatrick Hi, Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now 1. Turn on facet nature and enable JBOSS ESB nature. 2. Then it get recognized as a deployable artifact on JBoss server. 3. Manually add all dependencies in "Deployment and Assembly section". What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported? Thank you in advance. Manosh -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13437 at 1/28/13 3:57 PM: ------------------------------------------------------------- Assign to Bob to review - a similar fix is in order for the 4.1 (Kepler) stream, though I would upversion those to 1.2.100 or 1.3.0 instead. was (Author: nickboldt): Assign to Bob to review. > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > > JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT > [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found > {code} > Solution: remove the feature (and ask upstream why it vanished). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13437: ------------------------------------ Assign to Bob to review. > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > > JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT > [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found > {code} > Solution: remove the feature (and ask upstream why it vanished). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13437: ------------------------------- Assignee: Robert (Bob) Brodt (was: Nick Boldt) > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > > JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT > [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found > {code} > Solution: remove the feature (and ask upstream why it vanished). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13437: ------------------------------- Description: JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found {code} Solution: remove the feature (and ask upstream why it vanished). was: BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl... Solution: remove the feature (and ask upstream why it vanished). > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.0.Alpha1-SOA > > > JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT > [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found > {code} > Solution: remove the feature (and ask upstream why it vanished). -- 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, 2 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 January 2013