-
1. Re: [forge-dev] JDK 7 still being used for compilation. We are still looking into the issue.
ivan_stefanov Oct 7, 2013 6:15 PM (in response to lincolnthree)Hi folks,
Isn't it enough to change back to JBoss parent version 10? Or we want to
stick to version 11? Maybe it's about time to go to Java 7!
BTW, I cannot build Forge, because Maven can't find the Furnace artifacts
in any repository. Did you remove them by chance?
Cheers,
Ivan
On Sat, Oct 5, 2013 at 1:23 AM, Lincoln Baxter, III <lincolnbaxter@gmail.com
wrote:
In the mean time, please try to use JDK7 We'll be compatible with 6
again soon.
--
Lincoln Baxter, III
"Simpler is better."
_______________________________________________
forge-dev mailing list
https://lists.jboss.org/mailman/listinfo/forge-dev
-
att1.html.zip 808 bytes
-
-
2. Re: [forge-dev] JDK 7 still being used for compilation. We are still looking into the issue.
ivan_stefanov Oct 8, 2013 4:36 PM (in response to ivan_stefanov)Hi again,
I checked the effective pom of the Forge projects. It seems that the
projects are looking
for org.jboss.forge.furnace:furnace-maven-plugin:jar:2.0.0-SNAPSHOT at
http://repo1.maven.org/maven2. But there are only 2.0.0.Alpha releases
there (no snapshot).
Should we add the JBoss snapshot repository (
https://repository.jboss.org/nexus/content/repositories/snapshots)? I
noticed that it contains the snapshot releases.
Cheers,
Ivan
On Tue, Oct 8, 2013 at 1:15 AM, Ivan St. Ivanov <ivan.st.ivanov@gmail.com>wrote:
Hi folks,
Isn't it enough to change back to JBoss parent version 10? Or we want to
stick to version 11? Maybe it's about time to go to Java 7!
BTW, I cannot build Forge, because Maven can't find the Furnace artifacts
in any repository. Did you remove them by chance?
Cheers,
Ivan
>
On Sat, Oct 5, 2013 at 1:23 AM, Lincoln Baxter, III <
lincolnbaxter@gmail.com> wrote:
>> In the mean time, please try to use JDK7 We'll be compatible with 6
>> again soon.
>>
>> --
>> Lincoln Baxter, III
>> "Simpler is better."
>>
>> _______________________________________________
>> forge-dev mailing list
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
-
att1.html.zip 1.1 KB
-
-
3. Re: [forge-dev] JDK 7 still being used for compilation. We are still looking into the issue.
gastaldi Oct 8, 2013 4:52 PM (in response to ivan_stefanov)Hi Ivan,
Yes, you must add that to your settings.xml.
Best regards,
George
Em 08/10/2013, às 17:36, "Ivan St. Ivanov" <ivan.st.ivanov@gmail.com> escreveu:
Hi again,
I checked the effective pom of the Forge projects. It seems that the projects are looking for org.jboss.forge.furnace:furnace-maven-plugin:jar:2.0.0-SNAPSHOT at http://repo1.maven.org/maven2. But there are only 2.0.0.Alpha releases there (no snapshot).
Should we add the JBoss snapshot repository (https://repository.jboss.org/nexus/content/repositories/snapshots)? I noticed that it contains the snapshot releases.
Cheers,
Ivan
>> On Tue, Oct 8, 2013 at 1:15 AM, Ivan St. Ivanov <ivan.st.ivanov@gmail.com> wrote:
>> Hi folks,
>>
>> Isn't it enough to change back to JBoss parent version 10? Or we want to stick to version 11? Maybe it's about time to go to Java 7!
>>
>> BTW, I cannot build Forge, because Maven can't find the Furnace artifacts in any repository. Did you remove them by chance?
>>
>> Cheers,
>> Ivan
>>
>>
>>> On Sat, Oct 5, 2013 at 1:23 AM, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:
>>> In the mean time, please try to use JDK7 We'll be compatible with 6 again soon.
>>>
>>> --
>>> Lincoln Baxter, III
>>> "Simpler is better."
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
_______________________________________________
forge-dev mailing list
-
att1.html.zip 1.3 KB
-
-
4. Re: [forge-dev] JDK 7 still being used for compilation. We are still looking into the issue.
ivan_stefanov Oct 9, 2013 4:05 AM (in response to gastaldi)Hi George,
Thanks! That seemed to fix the issue. However, it was possible so far to
build forge without special prepared setttings.xml. Now we have to do that
(BTW, it is not documented). I wonder though, should we? There are two ways
to avoid touching settings.xml:
1) Adding the snapshot results to the central maven repository
2) Adding the jboss snapshot repository to our parent pom.xml
BTW, for those interested, here is what I added to my settings.xml:
wrote:
Hi Ivan,
Yes, you must add that to your settings.xml.
Best regards,
George
Em 08/10/2013, às 17:36, "Ivan St. Ivanov" <ivan.st.ivanov@gmail.com>
escreveu:
Hi again,
I checked the effective pom of the Forge projects. It seems that the
projects are looking
for org.jboss.forge.furnace:furnace-maven-plugin:jar:2.0.0-SNAPSHOT at
http://repo1.maven.org/maven2. But there are only 2.0.0.Alpha releases
there (no snapshot).
Should we add the JBoss snapshot repository (
https://repository.jboss.org/nexus/content/repositories/snapshots)? I
noticed that it contains the snapshot releases.
Cheers,
Ivan
>
On Tue, Oct 8, 2013 at 1:15 AM, Ivan St. Ivanov <ivan.st.ivanov@gmail.com>wrote:
>> Hi folks,
>>
>> Isn't it enough to change back to JBoss parent version 10? Or we want to
>> stick to version 11? Maybe it's about time to go to Java 7!
>>
>> BTW, I cannot build Forge, because Maven can't find the Furnace artifacts
>> in any repository. Did you remove them by chance?
>>
>> Cheers,
>> Ivan
>>
>>
>> On Sat, Oct 5, 2013 at 1:23 AM, Lincoln Baxter, III <
>> lincolnbaxter@gmail.com> wrote:
>>
>>> In the mean time, please try to use JDK7 We'll be compatible with 6
>>> again soon.
>>>
>>> --
>>> Lincoln Baxter, III
>>> "Simpler is better."
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>
>>
_______________________________________________
forge-dev mailing list
https://lists.jboss.org/mailman/listinfo/forge-dev
>
_______________________________________________
forge-dev mailing list
https://lists.jboss.org/mailman/listinfo/forge-dev
-
att1.html.zip 1.8 KB
-