[jbosstools-issues] [JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars

Mickael Istria (JIRA) jira-events at lists.jboss.org
Mon Jul 29 11:20:26 EDT 2013


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

Mickael Istria edited comment on JBIDE-15301 at 7/29/13 11:19 AM:
------------------------------------------------------------------

[~phantomjinx]: it seems to me that the addition of these jars comes from the changes you suggested as part of JBTIS-102 .

We cannot allow Locus to contain a SNAPSHOT repository such as the one added here: https://github.com/jbosstools/jbosstools-locus/blob/1.0.0.x/site/pom.xml#L213
And in general, we cannot allow redhat specific builds.

Can Teiid depend on the community release artifacts instead?
                
      was (Author: mickael_istria):
    [~phantomjinx]: it seems to me that the addition of these jars comes from the changes you suggested as part of JBTIS-102 .

We cannot allow Locus to contain a SNAPSHOT repository such as the one added here: https://issues.jboss.org/browse/JBIDE-15301

And in general, we cannot allow redhat specific builds.


Can Teiid depend on the community release artifacts instead?
                  
> Locus 1.0.0.Final contains some unwanted jars
> ---------------------------------------------
>
>                 Key: JBIDE-15301
>                 URL: https://issues.jboss.org/browse/JBIDE-15301
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: locus
>    Affects Versions: 1.0.0-LOCUS
>            Reporter: Mickael Istria
>            Assignee: Paul Richardson
>            Priority: Critical
>             Fix For: 1.0.1-LOCUS
>
>
> Locus contains some jars that are against Locus rules because:
> * They are SNAPSHOTs
> * They are -redhat- build.
> Instead, it should be public releases only.

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


More information about the jbosstools-issues mailing list