[JBoss JIRA] (JBIDE-14534) Errors in Spring project archetypes
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14534?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-14534:
----------------------------------
Description:
There are 2 errors in Spring Project archetype:
{code}
Description Resource Path Location Type
cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
{code}
[0] https://bugzilla.redhat.com/show_bug.cgi?id=996680
[1] https://issues.jboss.org/browse/WFLY-943
was:
There are 2 errors in Spring Project archetype:
{code}
Description Resource Path Location Type
cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
{code}
> Errors in Spring project archetypes
> -----------------------------------
>
> Key: JBIDE-14534
> URL: https://issues.jboss.org/browse/JBIDE-14534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.1.x
>
>
> There are 2 errors in Spring Project archetype:
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> {code}
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=996680
> [1] https://issues.jboss.org/browse/WFLY-943
--
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
12 years, 8 months
[JBoss JIRA] (JBTIS-140) target-platform Jenkins build fails w/ Could not resolve artifact for Tycho's OSGi runtime: Could not transfer artifact org.eclipse.tycho:tycho-bundles-external:zip:0.17.0
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-140:
--------------------------------
Summary: target-platform Jenkins build fails w/ Could not resolve artifact for Tycho's OSGi runtime: Could not transfer artifact org.eclipse.tycho:tycho-bundles-external:zip:0.17.0
Key: JBTIS-140
URL: https://issues.jboss.org/browse/JBTIS-140
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: target-platform
Affects Versions: 4.1.1
Reporter: Paul Leacu
Assignee: Paul Leacu
12:43:44 [INFO] BUILD FAILURE
12:43:44 [INFO] ------------------------------------------------------------------------
12:43:44 [INFO] Total time: 10:37.284s
12:43:44 [INFO] Finished at: Tue Aug 13 12:43:44 EDT 2013
12:43:44 [INFO] Final Memory: 10M/49M
12:43:44 [INFO] ------------------------------------------------------------------------
12:43:44 [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.0.1-SNAPSHOT:mirror-target-to-repo (default) on project target-platform: Internal error: org.apache.maven.MavenExecutionException: Could not resolve artifact for Tycho's OSGi runtime: Could not transfer artifact org.eclipse.tycho:tycho-bundles-external:zip:0.17.0 from/to central (http://repo.maven.apache.org/maven2): GET request of: org/eclipse/tycho/tycho-bundles-external/0.17.0/tycho-bundles-external-0.17.0.zip from central failed
12:43:44 [ERROR] org.eclipse.tycho:tycho-bundles-external:zip:0.17.0
12:43:44 [ERROR]
12:43:44 [ERROR] from the specified remote repositories:
12:43:44 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
12:43:44 [ERROR] jboss-ip-repository (file:///qa/services/hudson/hudson_workspace/workspace/JBTIS-target-platform/soa-6.0.0-alpha-maven-repository/, releases=true, snapshots=false),
12:43:44 [ERROR] jboss-eap-repository (file:///qa/services/hudson/hudson_workspace/workspace/JBTIS-target-platform/jboss-eap-6.1.0.GA-maven-repository/, releases=true, snapshots=false),
12:43:44 [ERROR] jboss-community-repository (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=false),
12:43:44 [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false): Connection reset
12:43:44 [ERROR] -> [Help 1]
12:43:44 [ERROR]
12:43:44 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
12:43:44 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
12:43:44 [ERROR]
12:43:44 [ERROR] For more information about the errors and possible solutions, please read the following articles:
12:43:44 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
12:43:44 Build step 'Invoke top-level Maven targets' marked build as failure
12:43:44 Archiving artifacts
12:43:44 Notifying upstream projects of job completion
12:43:44 Finished: FAILURE
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2359) Spring example generates warnings
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBDS-2359?page=com.atlassian.jira.plugin.... ]
Pete Muir commented on JBDS-2359:
---------------------------------
How do we fix the examples so that the warning goes away?
> Spring example generates warnings
> ---------------------------------
>
> Key: JBDS-2359
> URL: https://issues.jboss.org/browse/JBDS-2359
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Marius Bogoevici
> Fix For: 6.0.0.CR1
>
>
> The Spring example generates this warning:
> No connection specified for project. No database-specific validation will be performed.
> jboss-springmvc-webapp
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-15335) Consider removing update site zips from jboss.org/tools
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15335?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15335:
---------------------------------------------
if you are talking about restructuring our download pages - then thats something [~xcoulon] been talking about today.
btw. any idea why 4.1 is twice as big as 4.0 in download size ?
About target download zip - they can download eclipse zip and get most of these bits.
About hibernatetools.zip - probably possible to phase it out, but thats an simpler thing than "remove all" :)
> Consider removing update site zips from jboss.org/tools
> -------------------------------------------------------
>
> Key: JBIDE-15335
> URL: https://issues.jboss.org/browse/JBIDE-15335
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.0.1.Final, 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Based on anecdotal evidence, it would appear that JBT 4.x is downloaded MANY MORE TIMES from Eclipse Marketplace than from jboss.org/tools:
> As of 2013-08-12 12:48pm:
> * Download stats from http://jboss.org/tools/download/stable/4_1 : 378 + 140 = *518 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.1.0 from Eclipse Marketplace for 2013/08: *3,678 installs* ({color:red}*7.1x*{color} as many)
> * Download stats from http://jboss.org/tools/download/stable/4_0 : 2441 + 899 = *3,340 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.0.1 from Eclipse Marketplace for 2013/04 - 2013/08: 11280 + 10421 + 9552 + 6246 + 1635 = *39,134 installs* ({color:red}*11.7x*{color} as many)
> So, is it time to stop providing a zip of the JBT update site? Seems like very few users want JBT delivered via zip.
> Note too that the stats collected above include a partial month (August 2013) during which many people are on vacation. To get a real sense of the download rates we ought to check these numbers again in September and October.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-15335) Consider removing update site zips from jboss.org/tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15335?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15335 at 8/13/13 10:58 AM:
--------------------------------------------------------------
OK, I'll allow that the zips are useful for archiving old releases.
The purpose of this JIRA is to look at ways to simplify and streamline what we offer, based on *what our users actually use*. Sure, a _few people_ download the zips for offline install, but look at the frequency of those compared to those that use the online update sites.
Consider too that to use the zip you need to be online because not all the deps are included in the zip, unless you *ALSO download the 766M target platform zip*.
-----
Do we still need the Hibernate Tools zip [1], given that its content is ALSO provided in the site AND the site zip, and therefore is installable 3 other ways:
* Marketplace from http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site from http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site zip from http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/jb...
[1] http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/hi...
I would argue no, since for JBT 4.0, it's only gotten 900 downloads in 4 months, compared to 39,134 installs from Eclipse Marketplace in the same period. That's {color:red}*43x*{color} as many!
was (Author: nickboldt):
OK, I'll allow that the zips are useful for archiving old releases.
The purpose of this JIRA is to look at ways to simplify and streamline what we offer, based on *what our users actually use*. Sure, a _few people_ download the zips for offline install, but look at the frequency of those compared to those that use the online update sites.
Consider too that to use the zip you need to be online because not all the deps are included in the zip, unless you *ALSO download the 766M target platform zip*.
-----
Do we still need the Hibernate Tools zip [1], given that its content is ALSO provided in the site AND the site zip, and therefore is installable 3 other ways:
* Marketplace from http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site from http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site zip from http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/jb...
[1] http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/hi...
I would argue no, since for JBT 4.0, it's only gotten 900 downloads in 4 months, compared to 39,134 installs from Eclipse Marketplace in the same period. That's {color:red}*43x{color}* as many!
> Consider removing update site zips from jboss.org/tools
> -------------------------------------------------------
>
> Key: JBIDE-15335
> URL: https://issues.jboss.org/browse/JBIDE-15335
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.0.1.Final, 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Based on anecdotal evidence, it would appear that JBT 4.x is downloaded MANY MORE TIMES from Eclipse Marketplace than from jboss.org/tools:
> As of 2013-08-12 12:48pm:
> * Download stats from http://jboss.org/tools/download/stable/4_1 : 378 + 140 = *518 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.1.0 from Eclipse Marketplace for 2013/08: *3,678 installs* ({color:red}*7.1x*{color} as many)
> * Download stats from http://jboss.org/tools/download/stable/4_0 : 2441 + 899 = *3,340 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.0.1 from Eclipse Marketplace for 2013/04 - 2013/08: 11280 + 10421 + 9552 + 6246 + 1635 = *39,134 installs* ({color:red}*11.7x*{color} as many)
> So, is it time to stop providing a zip of the JBT update site? Seems like very few users want JBT delivered via zip.
> Note too that the stats collected above include a partial month (August 2013) during which many people are on vacation. To get a real sense of the download rates we ought to check these numbers again in September and October.
--
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
12 years, 8 months