Le 31 oct. 2014 à 09:34, Vineet Reynolds Pereira
<vpereira(a)redhat.com> a écrit :
----- Original Message -----
> From: "Max Rydahl Andersen" <max.andersen(a)redhat.com
<mailto:max.andersen@redhat.com>>
> To: "Rafael Benevides" <benevides(a)redhat.com
<mailto:benevides@redhat.com>>
> Cc: jbossdeveloper(a)lists.jboss.org <mailto:jbossdeveloper@lists.jboss.org>,
"Alexandre Porcelli" <alexandre.porcelli(a)gmail.com
<mailto:alexandre.porcelli@gmail.com>>, "Tomas Repel"
> <trepel(a)redhat.com <mailto:trepel@redhat.com>>, "Nikoleta
Ziakova" <nziakova(a)redhat.com <mailto:nziakova@redhat.com>>
> Sent: Friday, October 31, 2014 6:53:43 PM
> Subject: Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
>
> On 31 Oct 2014, at 13:58, Rafael Benevides wrote:
>
>> I know which dependencies were causing the build to fail and where to
>> find them, but it seems that Alexandre wanted to show users how to run
>> a
>> project as easy as clone, build and run.
>>
>> If I'm not wrong, this discussion started with similar issues in this
>> Arun Gupta Twitter thread:
>>
https://twitter.com/arungupta/status/502854638832730112
>
> so this is a different question.
>
> Question is if we should add the techpreview/all to
> quickstarts/examples.
>
> Not about earlyaccess.
>
> And afaik we already did this for quickstarts with a clear warning,
> right ?
AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied
instead:
https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final...
<
https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final...
But, that would deflect the original question on whether we should add it to POM.
Honestly, I dont mind adding it, with the warning that for a real-world project, the repo
should instead be in the settings.xml.
+1
In JBT/JBDS, if you ctrl+space in the <repositories> section of a pom.xml, you’ll
see templates to add JBoss/Red Hat repo definitions. This is what we add then :
<!-- You should seriously consider using a repository manager or declare
repositories in your settings.xml.
See
http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-p...
-->
<repository>
<!-- The JBoss Public repository is a composite repository of several major
repositories.
See
http://community.jboss.org/wiki/MavenGettingStarted-Users -->
<id>jboss-public-repository</id>
<
url>http://repository.jboss.org/nexus/content/groups/public</url>
<releases>
<enabled>true</enabled>
</releases>
<!-- You can disable snapshot resolution to speed up your builds -->
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
>
> Thus if ticketmonster does not have that in there I would say it would
> make sense to add it
> with similar warning/text as the quickstarts.
>
> /max
>
>>
>> As I also told Alexandre that we were having this discussion, I
>> invited
>> him to give his feedback on this Thread so he can provide more
>> details.
>>
>> Alexandre,
>>
>> Do you mind to share your restrictions and perceptions about the build
>> process ?
>>
>> On 10/31/14 06:47, Marek Novotny wrote:
>>>>> What restrictions does he have ?
>>>>>
>>>>> And I guess the issue here is ticketmonster master needs the
>>>>> earlyaccess bits ?
>>>>>
>>>>> I think ticketmonster master could add the earlyaccess to its pom
>>>>> but
>>>>> then just make sure once it is releaesed it gets removed which
>>>>> should
>>>>> be fine since then it should be using any earlyaccess bundles,
>>>>> right ?
>>> Not really, ticket-monster master branch doesn't exist. The closest
>>> to
>>> master is 2.6.0.Final -
>>>
https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final -
>>> which is the tight to WFK 2.6.0.GA and all GAVs should be resolvable
>>>
fromhttp://maven.repository.redhat.com/techpreview/all/
>>>
>>> I think that Rafael knows that 2.7.x-develop is unstable and includes
>>> internal product GAVs which are not in all or earlyaccess.
>>>
>>> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work
>>> just with online redhat repository
>>>
http://maven.repository.redhat.com/techpreview/all/. If not please
>>> advice him to send errors to Vineet or me.
>>>
>>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
> /max
>
http://about.me/maxandersen
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper(a)lists.jboss.org <mailto:jbossdeveloper@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
<
https://lists.jboss.org/mailman/listinfo/jbossdeveloper>