[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13307 at 3/24/13 4:22 PM:
-------------------------------------------------------------
I have removed all the buildflow.\{1,2,3,4,5,6\} jobs in favour of the all-in-one buildflow job . Also created a new one for the _41 branch.
Resolving. If you want to tackle this problem another way, please open a new JIRA.
was (Author: nickboldt):
I have removed all the buildflow.{1,2,3,4,5,6} jobs in favour of the all-in-one buildflow job . Also created a new one for the _41 branch.
Resolving. If you want to tackle this problem another way, please open a new JIRA.
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
> Key: JBIDE-13307
> URL: https://issues.jboss.org/browse/JBIDE-13307
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.
--
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
13 years
[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13307 at 3/24/13 4:23 PM:
-------------------------------------------------------------
I have removed all the buildflow.\{1,2,3,4,5,6\} jobs in favour of the all-in-one buildflow job . Also created a new one for the _41 branch, which is currently disabled until we branch for Alpha2x.
Resolving. If you want to tackle this problem another way, please open a new JIRA.
was (Author: nickboldt):
I have removed all the buildflow.\{1,2,3,4,5,6\} jobs in favour of the all-in-one buildflow job . Also created a new one for the _41 branch.
Resolving. If you want to tackle this problem another way, please open a new JIRA.
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
> Key: JBIDE-13307
> URL: https://issues.jboss.org/browse/JBIDE-13307
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.
--
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
13 years
[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13307 at 3/24/13 4:22 PM:
-------------------------------------------------------------
I have removed all the buildflow.{1,2,3,4,5,6} jobs in favour of the all-in-one buildflow job . Also created a new one for the _41 branch.
Resolving. If you want to tackle this problem another way, please open a new JIRA.
was (Author: nickboldt):
Resolving. If you want to tackle this problem another way, please open a new JIRA.
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
> Key: JBIDE-13307
> URL: https://issues.jboss.org/browse/JBIDE-13307
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.
--
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
13 years
[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13307 at 3/24/13 4:09 PM:
-------------------------------------------------------------
Builds 9 and 10 were also blue, now that we're ignoring failures just to ensure everything builds on the weekend (and if anything is new, it will publish the changes).
However, it should be noted that the time to run a full stack varies from under 6hrs to 18hrs!
{code}
#9 7 hr 53 min dev05-rhel5-x86_64
#8 18 hr dev05-rhel5-x86_64
#5, #6, and #7 all failed
#4 5 hr 21 min dev05-rhel5-x86_64
{code}
We could still move to the other approach of "all sources in one workspace, then build it all at once" but for now I'm satisfied w/ the output we get for the BuildFlow job.
!http://snag.gy/GY019.jpg!
was (Author: nickboldt):
Builds 9 and 10 were also blue, now that we're ignoring failures just to ensure everything builds on the weekend (and if anything is new, it will publish the changes).
However, it should be noted that the time to run a full stack varies from under 6hrs to 18hrs!
{code}
#9 7 hr 53 min dev05-rhel5-x86_64
#8 18 hr dev05-rhel5-x86_64
#5, #6, and #7 all failed
#4 5 hr 21 min dev05-rhel5-x86_64
{code}
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
> Key: JBIDE-13307
> URL: https://issues.jboss.org/browse/JBIDE-13307
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.
--
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
13 years
[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13307:
------------------------------------
Builds 9 and 10 were also blue, now that we're ignoring failures just to ensure everything builds on the weekend (and if anything is new, it will publish the changes).
However, it should be noted that the time to run a full stack varies from under 6hrs to 18hrs!
{code}
#9 7 hr 53 min dev05-rhel5-x86_64
#8 18 hr dev05-rhel5-x86_64
#5, #6, and #7 all failed
#4 5 hr 21 min dev05-rhel5-x86_64
{code}
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
> Key: JBIDE-13307
> URL: https://issues.jboss.org/browse/JBIDE-13307
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.
--
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
13 years
[JBoss JIRA] (JBIDE-13845) Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13845?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13845:
------------------------------------
Same job, different failure:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fjbosstools-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/116/console}
FrThe installable unit org.eclipse.swtbot.eclipse.test.junit4.feature.group has not been found.
Application failed, log file locatamework arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/releaion: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/640333b9/eclipse/configuration/13641ses/latest/,file:////mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/640333b9/repository -32144555.log
installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group
Command-line arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/releases/latest/,file:////m... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
!ENTRY org.eclipse.equinox.p2.director.app 4 0 2013-03-24 09:35:54.705
!MESSAGE The installable unit org.eclipse.swtbot.eclipse.test.junit4.feature.group has not been found.
Build step 'Execute Groovy script' marked build as failure
{code}
> Branch install-grinder for Juno (using org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5 and org.junit4 4.8) and Kepler (org.eclipse.swtbot.eclipse.test.junit.feature.group 2.1 and org.junit 4.11)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13845
> URL: https://issues.jboss.org/browse/JBIDE-13845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> As noted in JBIDE-13843, Kepler M6 no longer includes the org.junit4_4.8 bundle; instead it includes org.junit_4.11.
> So, install-grinder fails to set up the install base with this error due to the missing IU:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M6,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/102/console}
> Framework arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group
> Command-line arguments: -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... -installIU org.jboss.tools.tests.installation -installIU org.eclipse.swtbot.eclipse.test.junit4.feature.group -consolelog
> !ENTRY org.eclipse.equinox.p2.director 4 1 2013-03-23 02:15:09.053
> !MESSAGE Cannot complete the install because one or more required items could not be found.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
> !MESSAGE Software bCannot complete the install because one or more required items could not be found.
> Software being installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
> Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0eing installed: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.sw.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2013-03-23 02:15:09.054
> !MESSAGE Missing requirement: SWTBot JUnit 4.x Headless launchers for Eclipse (incubation) 2.0.5.20111003_1754-3676ac8-dev-e36 (org.eclipse.swtbot.eclipse.test.junit4.feature.group 2.0.5.20111003_1754-3676ac8-dev-e36) requires 'org.junit4 0.0.0' but it could not be found
> ires 'org.junit4 0.0.0' but it could not be found
> {code}
> However, since the Juno tests still depend on SWTBot 2.0.5 and Juno (in which org.junit4 CAN be found) we need to create a jbosstools-4.0.x branch and configure all the 4.0.x jobs that depend on install-grinder so that they will use this new org.junit4_4.8 / SWTBot 2.0.5 compatible branch, while master moves ahead with SWTBot 2.1 and org.junit_4.11.
--
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
13 years
[JBoss JIRA] (TOOLSDOC-302) nightly doc build fails to resolve emf.ecore 2.3.0 as it's not available in JBoss nexus (but is in Maven Central)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-302?page=com.atlassian.jira.plug... ]
Nick Boldt updated TOOLSDOC-302:
--------------------------------
Description:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-docs-nightly/932/console}
[INFO] All Userguides index-(en-US) ...................... SUCCESS [0.077s]
[INFO] All_Userguides .................................... FAILURE [32.397s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:10.890s
[INFO] Finished at: Sat Mar 23 12:06:57 EDT 2013
[INFO] Final Memory: 13M/89M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.3.4:resources (default-resources) on project Getting_Started_Guide-en-US:
Unexpected problem: Unable to resolve artifact [org.eclipse.emf:ecore:jar:null]: Could not transfer artifact org.eclipse.emf:ecore:jar:[2.3.0,2.4.0)
from/to jboss-releases (http://repository.jboss.org/maven2): IllegalArgumentException
[ERROR] org.eclipse.emf:ecore:jar:null
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] jboss-releases (http://repository.jboss.org/maven2, releases=true, snapshots=false),
[ERROR] jboss-snapshots (http://snapshots.jboss.org/maven2, releases=false, snapshots=true),
[ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
[ERROR] Path to dependency:
[ERROR] 1) org.jboss.tools:Getting_Started_Guide-en-US:jdocbook:1.0
[ERROR] 2) org.eclipse.wst.css:core:jar:1.1.101-v200705302225
[ERROR] 3) org.eclipse.wst.xml:core:jar:1.1.201-v200709201331
[ERROR] 4) org.eclipse.wst:validation:jar:1.1.102-v200709122200
[ERROR] 5) org.eclipse.wst.common:frameworks:jar:1.1.102-v200706071630: Illegal character in path at index 57:
http://repository.jboss.org/maven2/org/eclipse/emf/ecore/[2.3.0,2.4.0)/ec...
{code}
While the jar definitely does not exist under here (only poms are available for the 2.3.0 version):
http://repository.jboss.org/maven2/org/eclipse/emf/ecore/
I did find the required jar here:
http://search.maven.org/remotecontent?filepath=org/eclipse/emf/ecore/2.3....
Maybe if you use snapshots=true:
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=*true*) {code}
instead of
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) {code}
you'll be able to resolve the artifact?
was:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-docs-nightly/932/console}
[INFO] All Userguides index-(en-US) ...................... SUCCESS [0.077s]
[INFO] All_Userguides .................................... FAILURE [32.397s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:10.890s
[INFO] Finished at: Sat Mar 23 12:06:57 EDT 2013
[INFO] Final Memory: 13M/89M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.3.4:resources (default-resources) on project Getting_Started_Guide-en-US: Unexpected problem: Unable to resolve artifact [org.eclipse.emf:ecore:jar:null]: Could not transfer artifact org.eclipse.emf:ecore:jar:[2.3.0,2.4.0) from/to jboss-releases (http://repository.jboss.org/maven2): IllegalArgumentException
[ERROR] org.eclipse.emf:ecore:jar:null
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] jboss-releases (http://repository.jboss.org/maven2, releases=true, snapshots=false),
[ERROR] jboss-snapshots (http://snapshots.jboss.org/maven2, releases=false, snapshots=true),
[ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
[ERROR] Path to dependency:
[ERROR] 1) org.jboss.tools:Getting_Started_Guide-en-US:jdocbook:1.0
[ERROR] 2) org.eclipse.wst.css:core:jar:1.1.101-v200705302225
[ERROR] 3) org.eclipse.wst.xml:core:jar:1.1.201-v200709201331
[ERROR] 4) org.eclipse.wst:validation:jar:1.1.102-v200709122200
[ERROR] 5) org.eclipse.wst.common:frameworks:jar:1.1.102-v200706071630: Illegal character in path at index 57: http://repository.jboss.org/maven2/org/eclipse/emf/ecore/[2.3.0,2.4.0)/ec...
{code}
Found the required jar here:
http://search.maven.org/remotecontent?filepath=org/eclipse/emf/ecore/2.3....
Maybe if you use snapshots=true:
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=*true*) {code}
instead of
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) {code}
you'll be able to resolve the artifact?
> nightly doc build fails to resolve emf.ecore 2.3.0 as it's not available in JBoss nexus (but is in Maven Central)
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-302
> URL: https://issues.jboss.org/browse/TOOLSDOC-302
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: General documentation issues
> Affects Versions: 4.1.0
> Reporter: Nick Boldt
> Assignee: Michelle Murray
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-docs-nightly/932/console}
> [INFO] All Userguides index-(en-US) ...................... SUCCESS [0.077s]
> [INFO] All_Userguides .................................... FAILURE [32.397s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:10.890s
> [INFO] Finished at: Sat Mar 23 12:06:57 EDT 2013
> [INFO] Final Memory: 13M/89M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.3.4:resources (default-resources) on project Getting_Started_Guide-en-US:
> Unexpected problem: Unable to resolve artifact [org.eclipse.emf:ecore:jar:null]: Could not transfer artifact org.eclipse.emf:ecore:jar:[2.3.0,2.4.0)
> from/to jboss-releases (http://repository.jboss.org/maven2): IllegalArgumentException
> [ERROR] org.eclipse.emf:ecore:jar:null
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] jboss-releases (http://repository.jboss.org/maven2, releases=true, snapshots=false),
> [ERROR] jboss-snapshots (http://snapshots.jboss.org/maven2, releases=false, snapshots=true),
> [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [ERROR] Path to dependency:
> [ERROR] 1) org.jboss.tools:Getting_Started_Guide-en-US:jdocbook:1.0
> [ERROR] 2) org.eclipse.wst.css:core:jar:1.1.101-v200705302225
> [ERROR] 3) org.eclipse.wst.xml:core:jar:1.1.201-v200709201331
> [ERROR] 4) org.eclipse.wst:validation:jar:1.1.102-v200709122200
> [ERROR] 5) org.eclipse.wst.common:frameworks:jar:1.1.102-v200706071630: Illegal character in path at index 57:
> http://repository.jboss.org/maven2/org/eclipse/emf/ecore/[2.3.0,2.4.0)/ec...
> {code}
> While the jar definitely does not exist under here (only poms are available for the 2.3.0 version):
> http://repository.jboss.org/maven2/org/eclipse/emf/ecore/
> I did find the required jar here:
> http://search.maven.org/remotecontent?filepath=org/eclipse/emf/ecore/2.3....
> Maybe if you use snapshots=true:
> {code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=*true*) {code}
> instead of
> {code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) {code}
> you'll be able to resolve the artifact?
--
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
13 years
[JBoss JIRA] (TOOLSDOC-302) nightly doc build fails to resolve emf.ecore 2.3.0 as it's not available in JBoss nexus (but is in Maven Central)
by Nick Boldt (JIRA)
Nick Boldt created TOOLSDOC-302:
-----------------------------------
Summary: nightly doc build fails to resolve emf.ecore 2.3.0 as it's not available in JBoss nexus (but is in Maven Central)
Key: TOOLSDOC-302
URL: https://issues.jboss.org/browse/TOOLSDOC-302
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: General documentation issues
Affects Versions: 4.1.0
Reporter: Nick Boldt
Assignee: Michelle Murray
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-docs-nightly/932/console}
[INFO] All Userguides index-(en-US) ...................... SUCCESS [0.077s]
[INFO] All_Userguides .................................... FAILURE [32.397s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:10.890s
[INFO] Finished at: Sat Mar 23 12:06:57 EDT 2013
[INFO] Final Memory: 13M/89M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.3.4:resources (default-resources) on project Getting_Started_Guide-en-US: Unexpected problem: Unable to resolve artifact [org.eclipse.emf:ecore:jar:null]: Could not transfer artifact org.eclipse.emf:ecore:jar:[2.3.0,2.4.0) from/to jboss-releases (http://repository.jboss.org/maven2): IllegalArgumentException
[ERROR] org.eclipse.emf:ecore:jar:null
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] jboss-releases (http://repository.jboss.org/maven2, releases=true, snapshots=false),
[ERROR] jboss-snapshots (http://snapshots.jboss.org/maven2, releases=false, snapshots=true),
[ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
[ERROR] Path to dependency:
[ERROR] 1) org.jboss.tools:Getting_Started_Guide-en-US:jdocbook:1.0
[ERROR] 2) org.eclipse.wst.css:core:jar:1.1.101-v200705302225
[ERROR] 3) org.eclipse.wst.xml:core:jar:1.1.201-v200709201331
[ERROR] 4) org.eclipse.wst:validation:jar:1.1.102-v200709122200
[ERROR] 5) org.eclipse.wst.common:frameworks:jar:1.1.102-v200706071630: Illegal character in path at index 57: http://repository.jboss.org/maven2/org/eclipse/emf/ecore/[2.3.0,2.4.0)/ec...
{code}
Found the required jar here:
http://search.maven.org/remotecontent?filepath=org/eclipse/emf/ecore/2.3....
Maybe if you use snapshots=true:
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=*true*) {code}
instead of
{code} central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false) {code}
you'll be able to resolve the artifact?
--
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
13 years