[jbosstools-issues] [JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-24129 at 3/27/17 12:12 PM:
--------------------------------------------------------------

Since the parent pom [1] profile *download-devstudio* points at devstudioRepository = https://devstudio.redhat.com/10.0/snapshots/updates/ to perform repository resolution, you may encounter situations where the test is running and the upstream site CHANGES during the test.

[1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L23

For example, the error you're seeing talks about 

{code}org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]'{code}

But in the site the current version is newer:

{code}org.jboss.ide.eclipse.as.feature.feature.group	3.2.4.v20170324-1941{code}

So... do you need to depend on the latest STAGING site for stability? Or just trigger the job to run again, if it fails?



was (Author: nickboldt):
Since the parent pom profile *download-devstudio* points at devstudioRepository = https://devstudio.redhat.com/10.0/snapshots/updates/ to perform repository resolution, you may encounter situations where the test is running and the upstream site CHANGES during the test.

For example, the error you're seeing talks about 

{code}org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]'{code}

But in the site the current version is newer:

{code}org.jboss.ide.eclipse.as.feature.feature.group	3.2.4.v20170324-1941{code}

So... do you need to depend on the latest STAGING site for stability? Or just trigger the job to run again, if it fails?


> download-devstudio profile breaks component builds
> --------------------------------------------------
>
>                 Key: JBIDE-24129
>                 URL: https://issues.jboss.org/browse/JBIDE-24129
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.4.AM2
>            Reporter: Pavol Srna
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 4.4.4.AM2
>
>
> We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently.
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR]   Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935
> [ERROR]   Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found
> [ERROR]   Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935]
> [ERROR] 
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)