[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12121:
-------------------------------------
Assignee: (was: Andre Dietisheim)
Estimated Difficulty: Medium
> Application wizard: 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
> Labels: application_wizard
> Fix For: 4.2.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, 4 months
[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12121:
-------------------------------------
Labels: application_wizard (was: )
> Application wizard: 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: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.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, 4 months
[JBoss JIRA] (JBIDE-12080) Explorer: provide initial instruction when there are no connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12080?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12080:
-------------------------------------
Assignee: (was: Xavier Coulon)
Estimated Difficulty: Low
> Explorer: provide initial instruction when there are no connections
> -------------------------------------------------------------------
>
> Key: JBIDE-12080
> URL: https://issues.jboss.org/browse/JBIDE-12080
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
> Attachments: openshift.png, servers.png
>
>
> OpenShift Explorer could provide basic instruction about how to create a new connection (where to click) like in Servers view:
> !servers.png|thumbnail!
> copied from duplicate JBIDE-14587:
> {quote}
> My 1st reflex is, when the view is empty, is to right-click to bring up the OpenShift Management UI. But nothing happens. I need to remember I need to click on the top right button to log-in (which doesn't stand out much on the window background).
> So. I'd welcome a "Connect to OpenShift" menu showing up on right-click, when OpenShift Explorer is empty. That menu doesn't need to appear if already connected.
> {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
12 years, 4 months
[JBoss JIRA] (JBIDE-12080) Explorer: provide initial instruction when there are no connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12080?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12080:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Explorer: provide initial instruction when there are no connections
> -------------------------------------------------------------------
>
> Key: JBIDE-12080
> URL: https://issues.jboss.org/browse/JBIDE-12080
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: explorer
> Fix For: LATER
>
> Attachments: openshift.png, servers.png
>
>
> OpenShift Explorer could provide basic instruction about how to create a new connection (where to click) like in Servers view:
> !servers.png|thumbnail!
> copied from duplicate JBIDE-14587:
> {quote}
> My 1st reflex is, when the view is empty, is to right-click to bring up the OpenShift Management UI. But nothing happens. I need to remember I need to click on the top right button to log-in (which doesn't stand out much on the window background).
> So. I'd welcome a "Connect to OpenShift" menu showing up on right-click, when OpenShift Explorer is empty. That menu doesn't need to appear if already connected.
> {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
12 years, 4 months