[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>
> <!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
> <!-- Use this profile for any OpenShift specific customization your app will need. -->
> <!-- By default that is to put the resulting archive into the deployments folder. -->
> <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
> <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>
> <!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
> <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
[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