May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-12121: ------------------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) Fred - can you provide API pointers? > The openshift profile is added to newly created maven projects, regardless of their packaging type > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-12121 > URL: https://issues.jboss.org/browse/JBIDE-12121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.x > > Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png > > > I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog) > This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project : > {code:xml} > <profiles> > <profile> >  >  >  >  > <id>openshift</id> > <build> > <finalName>hello</finalName> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.1.1</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </build> > </profile> > {code} > Actually, it should : > - check the packaging type of *all* the generated projects > - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-ear-plugin</artifactId> > <version>2.7</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profiles> > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.2</version> > <configuration> > <outputDirectory>deployments</outputDirectory> >  > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > The finalName is irrelevant to openshift, only the warName counts. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2537) JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2537?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2537: ------------------------------------- Should I just add JDK check in installer and warn about JDK requirement for AS? > JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough) > ---------------------------------------------------------------------------------- > > Key: JBDS-2537 > URL: https://issues.jboss.org/browse/JBDS-2537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Rob Stryker > Priority: Blocker > Fix For: 7.0.0.Beta2 > > > Help the users that are not sure how to get JDK. Add JRE vs JDK detector at AS launch - JDK is required, getting this installed and configured inside of JBDS/Eclipse is a challenge for the newbie. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs

by Kris Borchers (JIRA)

[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ] Kris Borchers commented on JBDS-2577: ------------------------------------- Modernizr is not meant to be used to swap between min/non-min JS. It is used to load completely different resources based on feature support detection in the browser. Most JS devs I know use one of two methods to switch. The first, which is less popular among serious devs, is to just switch manually when you deploy your changes into production. I do not recommend this approach. The second is that devs use some sort of build tool to concat/minify their JS into one or a couple of files at deployment. Tools like Yeoman/Grunt do this for you. That way during dev, your files are all non-minified and once you deploy your application, all files are combined and minified and the files that reference them are automatically updated to point to the new minified versions. The other option is to use a source map. I have been doing that occasionally lately as well. That provides, in browsers that support them, a way to use your minified files during dev, but there is a map that points to the non-minified version and can actually take you to the appropriate sections of the non-minified code when an error or break-point is reached in the minified version. > JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs > ----------------------------------------------------------------------- > > Key: JBDS-2577 > URL: https://issues.jboss.org/browse/JBDS-2577 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 7.0.0.Beta2 > > > Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?). > Examples of JS libs: jQuery, jQuery Mobile -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2530) JBDS70_0610: [Commit] (?) (P1) Visual Page Editor :: Preview tab

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2530?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2530: ------------------------------------- I remember we ended up not doing this and invest this time in browserSim features. > JBDS70_0610: [Commit] (?) (P1) Visual Page Editor :: Preview tab > ---------------------------------------------------------------- > > Key: JBDS-2530 > URL: https://issues.jboss.org/browse/JBDS-2530 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Yahor Radtsevich > Priority: Critical > Fix For: 7.0.0.Beta1 > > > Remove Split Visual / Source tab and Preview tab for HTML5 pages -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2537) JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2537?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2537: -------------------------------- Comment: was deleted (was: Related issue linked) > JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough) > ---------------------------------------------------------------------------------- > > Key: JBDS-2537 > URL: https://issues.jboss.org/browse/JBDS-2537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Rob Stryker > Priority: Blocker > Fix For: 7.0.0.Beta2 > > > Help the users that are not sure how to get JDK. Add JRE vs JDK detector at AS launch - JDK is required, getting this installed and configured inside of JBDS/Eclipse is a challenge for the newbie. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2513) Error: Could not create the Java Virtual Machine

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2513?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2513: -------------------------------- Environment: Windows 7 64-bit, 32-bit JVM > Error: Could not create the Java Virtual Machine > ------------------------------------------------ > > Key: JBDS-2513 > URL: https://issues.jboss.org/browse/JBDS-2513 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Environment: Windows 7 64-bit, 32-bit JVM > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.0.0.Beta1 > > Attachments: 2012-11-30_1425.png, 2012-11-30_1425_001.png, Installer_JVM_Settings.png > > > Running the installer with a JRE can create an improper installation. See screenshots -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2568) JBDS70_1313: [Partial] (Docs) (P2) Document the existing plug-in features

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2568?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2568: --------------------------------------- Of course Max, but it wont be Beta1 as you originally put the fix version. > JBDS70_1313: [Partial] (Docs) (P2) Document the existing plug-in features > ------------------------------------------------------------------------- > > Key: JBDS-2568 > URL: https://issues.jboss.org/browse/JBDS-2568 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: documentation, Requirements > Reporter: Jiri Pallich > Assignee: Michelle Murray > Fix For: 7.0.0.GA > > > Document more of the existing plug-in features, time will limit the extent to which this will be completed. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2541) JBDS70_0324: [Commit] (Dev) (P2) Installer :: Support for Bring Your Own Eclipse (BYOE)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2541?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2541: ------------------------------------- I would drop it, because there is no pretty way to check if selected eclipse is compatible with JBDS, all I can do for now is try to install and show error if something is not worked out. > JBDS70_0324: [Commit] (Dev) (P2) Installer :: Support for Bring Your Own Eclipse (BYOE) > --------------------------------------------------------------------------------------- > > Key: JBDS-2541 > URL: https://issues.jboss.org/browse/JBDS-2541 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Denis Golovin > Fix For: 7.0.0.Beta1 > > > JBDS BYOE Installer still includes bundled Eclipse, but now prompts user to point at an existing Eclipse on their machine if they prefer; will need to include mechanism to verify user's target Eclipse is compatible and provide feedback in case it is not. > Note: This was deferred JBDS60_1020 / https://issues.jboss.org/browse/JBDS-2323 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13349: ---------------------------------- Fix Version/s: 4.1.0.Beta1 > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Fix For: 4.1.0.Beta1 > > Attachments: Screenshot-2.png > > > See attached screenshot -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-13349. ----------------------------------- Resolution: Done > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Fix For: 4.1.0.Beta1 > > Attachments: Screenshot-2.png > > > See attached screenshot -- 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

12 years, 11 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 May 2013