Bug 965591
Summary: | [JBT]Fails to import jbossews apps to the workspace with error "couldn't import maven project null " shown caused by the imported name "jbossews-example" | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Online | Reporter: | joycezhang <jinzhang> | ||||
Component: | Containers | Assignee: | Dan McPherson <dmcphers> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 2.x | CC: | adietish, dmcphers, xtian | ||||
Target Milestone: | --- | Keywords: | FutureFeature | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-06-11 04:07:36 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
joycezhang
2013-05-21 11:50:48 UTC
Created attachment 751077 [details]
couldn't import maven project error
Copied one comment from https://issues.jboss.org/browse/JBIDE-14546: If you create a jbossas-7 application you get a project with an artifactId (in the pom.xml) which matches the OpenShift application name: Create a jbossas-7 application called as76 and get: <groupId>as76</groupId> <artifactId>as76</artifactId> If you create a jbossews-2.0 application you get a constant artifactId that does NOT match the OpenShift application name: Create a jbossews-2.0 application called ews123123 and get: <groupId>com.openshift.example.jbossews</groupId> <artifactId>jbossews-example</artifactId> Thus a user wont be able to create and import 2 different jbossews applications. It looks like as if this was fixed. I cannot reproduce it any more when creating jbossews-1 and jbossews-2 applications. In both cases the artifact id in the maven pom is not constant any more, it's set to match the application name. This bug is not fixed on INT(devenv_3281), the artifiactID is still "jbossews-example" as below # cat pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.openshift.example.jbossews</groupId> <artifactId>jbossews-example</artifactId> <packaging>war</packaging> <version>1.0</version> <name>jbossews-example</name> <repositories> <repository> <id>eap</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/a7cf11845211777d706fa88f1e235865efa139f1 Bug 965591 Verified this bug on devenv_3283, the artifiactID is changed as app name for jbossews-1.0/2.0 app as below: # cat pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>ews2</groupId> <artifactId>ews2</artifactId> <packaging>war</packaging> <version>1.0</version> <name>ews2</name> <repositories> <repository> <id>eap</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> |