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

[Paul Leacu (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780936#comment-12780936 ] 

Paul Leacu commented on JBTIS-69:
---------------------------------


   mvn -U clean deploy from Jenkins target-platform job - 4.0.1.Final

14:42:10 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project target-platform: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.integration-stack:target-platform:pom:4.0.1.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Access denied to: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.0.1.Final/target-platform-4.0.1.Final.pom, ReasonPhrase:Forbidden. -> [Help 1]
14:42:10 [ERROR] 
14:42:10 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
14:42:10 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
14:42:10 [ERROR] 
14:42:10 [ERROR] For more information about the errors and possible solutions, please read the following articles:
14:42:10 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
14:42:10 Build step 'Invoke top-level Maven targets' marked build as failure

                
> 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