[jbosstools-issues] [JBoss JIRA] (JBTIS-69) Refactor TP POM for nexus deployment consistency

[Paul Leacu (JIRA)]

Paul Leacu created JBTIS-69:
-------------------------------

             Summary: Refactor TP POM for nexus deployment consistency
                 Key: JBTIS-69
                 URL: https://issues.jboss.org/browse/JBTIS-69
             Project: JBoss Tools Integration Stack
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: target-platform
    Affects Versions: 4.0.0, 4.1.0
            Reporter: Paul Leacu
            Assignee: Paul Leacu
             Fix For: 4.1.0


Depends on the GAV of the thing you deployed.

I might consider refactoring your pom so that it ends up in this folder,
for consistency:

https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/targetplatforms/

As you can see, we have 2 TPs for each (unified, multiple) of
jbdevstudio and jbosstools. You could have jbds-is and jbt-is, or
perhaps jbdevstudio-integration and jbosstools-integration.

The way the path is produced comes from the pom:

https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.30.5.Alpha3/jbdevstudio-multiple-4.30.5.Alpha3.pom

<groupId>org.jboss.tools.targetplatforms</groupId> (from parent)
<artifactId>jbdevstudio-multiple</artifactId>
<version>4.30.5.Alpha3</version> (from parent)

--
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