[jbosstools-issues] [JBoss JIRA] (JBIDE-13042) fix bootstrap profiles so they use ../jbosstools-<component> convention instead of ../<component>

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13042:
------------------------------------

Not urgent for 4.0.0; bumped to 4.1.0.
                
> fix bootstrap profiles so they use ../jbosstools-<component> convention instead of ../<component>
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13042
>                 URL: https://issues.jboss.org/browse/JBIDE-13042
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Max Rydahl Andersen
>             Fix For: 4.1.0.Alpha1
>
>
> With the changes in JBIDE-12993, my assumed paths when checking out projects are no longer correct, and therefore the bootstrap profiles in the root poms are no longer working.
> Since I don't have global write perms, this either requires that someone with God access fix them all across the board, or I submit 19 PRs.
> Here's a sample of the changes needed, which will also need to be folded into JBIDE-12993 so that the recursion step (reading the root pom to decide if any child projects are needed) works w/ the new on-disk structure:
> {code}
> diff --git a/pom.xml b/pom.xml
> index 45cfe11..c5b946b 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -23,7 +23,7 @@
>                 <profile>
>                         <id>bootstrap</id>
>                         <modules>
> -                               <module>../portlet</module>
> +                               <module>../jbosstools-portlet</module>
>                         </modules>
>                 </profile>
>         </profiles>
> {code}

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