January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-13263: ----------------------------------- Assignee: Max Rydahl Andersen (was: Rob Stryker) PR needs approvals. sigh. > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.0.1.Final > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13263: ------------------------------------- API additions and conversions during the early phase of 4.0.0 (alpha / beta) led to this regression which went uncaught. In attempts to unify in a solid straight API methods to get a deploy folder regardless of whether the server is in local or remote / rse mode led to the creation of the publish m ethod and it's getDefaultDeployFolder. The listeners in charge of adding deployment scanners were previously using an api which returned the server's core deploy folder (standalone/deployments or server/default/deploy) and were counting this as the "insideServer" location. When the apis were enhanced, the new api was returning the current deploy folder (metadata or server or custom) rather than what was previously ONLY the server location. When the metadata location is checked, it matches the insideServer, and so is ignored as a duplicate. The insideServer location is assumed to never need to be added to a deployment scanner, since the server will add it by itself. The regression from JBIDE-12899 in fact delt with this issue, as JBIDE-12899 was causing the default deploy location to be added twice, which was wrong. While the issue was fixed for as7 to prevent the duplicate additions, the subclass was not verified. The subclass, which was not suffering from duplicate additions, now lost it's metadata deployment scanner in the process. > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.0.1.Final > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13263: ------------------------------------- This is also replicatable from as7 if you set the default deploy folder to be the .metadata. > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.0.1.Final > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13263: ------------------------------------- replicated hte issue. This is a regression from https://issues.jboss.org/browse/JBIDE-12899. > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.0.1.Final > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12137) openshift server adapter should show progress of git push while running not in the end

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12137?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12137 at 1/17/13 11:02 AM: -------------------------------------------------------------------- I filed bugzillas to Eclipse: * EGit: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398387 * JGit: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398404 was (Author: adietish): I filed a bugzilla to Eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398387 > openshift server adapter should show progress of git push while running not in the end > -------------------------------------------------------------------------------------- > > Key: JBIDE-12137 > URL: https://issues.jboss.org/browse/JBIDE-12137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: openshift-6.ogv > > > Please bring back that the progress monitor shows the git progress instead of just showing console output in the end -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13139) Improve libs import for EAP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13139?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13139: --------------------------------------------- this does not use the module system to find which jars are needed/relevant nor is it possible to tweak per project it seems ? > Improve libs import for EAP 6 > ----------------------------- > > Key: JBIDE-13139 > URL: https://issues.jboss.org/browse/JBIDE-13139 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 3.3.0.Final > Environment: JBDS 4.x > EAP 6/AS 7 > Reporter: William Siqueira > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept. > The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent. > What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13139) Improve libs import for EAP 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13139?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13139: ------------------------------------- This feature already exists for all server types in jbosstools. You can do teh following: 1) window -> preferences 2) Server -> Runtime Environment -> Default Classpath 3) Select your server type (eap6) 4) Note the list of filesets with an includes and excludes pattern. 5) If you want, click "add" and set a base directory, includes and excludes patterns 6) Click "Apply" to save the settings. That's it! Let me know if this works for you. > Improve libs import for EAP 6 > ----------------------------- > > Key: JBIDE-13139 > URL: https://issues.jboss.org/browse/JBIDE-13139 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 3.3.0.Final > Environment: JBDS 4.x > EAP 6/AS 7 > Reporter: William Siqueira > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept. > The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent. > What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13329 at 1/17/13 10:11 AM: ------------------------------------------------------------------ Tentative target platforms are respectively on the 4.2.0 and 4.2.1 branches of the target-platform repo: https://github.com/mickaelistria/jbosstools-target-platforms . Previous versions were tagged. Builds are running to publish those tentative TP: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... When this build are OK, we'll discuss on whether to use those new platforms in our various JBT/JBDS streams. was (Author: mickael_istria): Tentative target platforms are respectively on the 4.2.0 and 4.2.1 branches of the target-platform repo: https://github.com/mickaelistria/jbosstools-target-platforms . Previous versions were tagged. Builds are running to publish those tentative TP: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... When this build are OK, we'll discuss on whether to use those new platforms in our various JBT/JBDS streams. > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13329: ---------------------------------------- Tentative target platforms are respectively on the 4.2.0 and 4.2.1 branches of the target-platform repo: https://github.com/mickaelistria/jbosstools-target-platforms . Previous versions were tagged. Builds are running to publish those tentative TP: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... When this build are OK, we'll discuss on whether to use those new platforms in our various JBT/JBDS streams. > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12137) openshift server adapter should show progress of git push while running not in the end

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12137?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12137 at 1/17/13 9:52 AM: ------------------------------------------------------------------- I filed a bugzilla to Eclipse bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398387 was (Author: adietish): I filed a bugzilla to Eclipse bugzilla > openshift server adapter should show progress of git push while running not in the end > -------------------------------------------------------------------------------------- > > Key: JBIDE-12137 > URL: https://issues.jboss.org/browse/JBIDE-12137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: openshift-6.ogv > > > Please bring back that the progress monitor shows the git progress instead of just showing console output in the end -- 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, 5 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