[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8735) Savara parent pom maintenance
Gary Brown (JIRA)
jira-events at lists.jboss.org
Fri Apr 15 14:14:33 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595937#comment-12595937 ]
Gary Brown commented on JBIDE-8735:
-----------------------------------
Just to clarify, the version of Savara used in JBT 3.3 should be the newer 2.x version which is hosted on github, and uses:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>org.jboss.tools.parent.pom</artifactId>
<version>0.0.2-SNAPSHOT</version>
</parent>
The location of the project is: https://github.com/savara/savara-tools-eclipse
However the original issue was raised in respect of the hudson job: jbosstools-savara-1.2_trunk
This job uses the older 1.x version of Savara hosted on svn: https://svn.jboss.org/repos/savara
> Savara parent pom maintenance
> -----------------------------
>
> Key: JBIDE-8735
> URL: https://issues.jboss.org/browse/JBIDE-8735
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Savara
> Affects Versions: 3.3.0.M1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 3.3.0.M1
>
>
> Savara needs to use the JBT parent pom v0.0.2, so that it can benefit from the new profiles.
> > > > [WARNING] The requested profile
> > > > "jbosstools-nightly-staging-composite" could not be activated
> > > > because it does not exist.
> > > > [WARNING] The requested profile "unified.site" could not be
> > > > activated because it does not exist.
> > > > [WARNING] The requested profile "local.site" could not be activated
> > > > because it does not exist.
> > > > [WARNING] The requested profile "local.composite" could not be
> > > > activated because it does not exist.
> >
> > Note too that there's a site ref that's 404'd:
> >
> > > > [WARNING] No repository found at
> > http://download.jboss.org/jbosstools/builds/staging/pi4soa/all/repo/.
> >
> > This should perhaps be [0] instead?
> >
> > [0]
> > http://download.jboss.org/jbosstools/builds/staging/jbosstools-pi4soa-3.1_stable_branch/all/repo/
> >
> > And as well, you're referencing an outdated dependency site [1]:
> >
> > [1] http://download.eclipse.org/releases/helios
> >
> > That should be Indigo (Eclipse 3.7, WTP 3.3), not Helios (Eclipse 3.6,
> > WTP 3.2), and should be the JBT composite dependencies mirror site
> > [2],
> > [3], not the pure eclipse.org site:
> >
> > [2] http://download.jboss.org/jbosstools/updates/indigo/
> > [3] http://download.jboss.org/jbosstools/updates/helios/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list