[JBoss JIRA] (JBDS-2082) Error (ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2) when beta2 is closed
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2082:
----------------------------------
Summary: Error (ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2) when beta2 is closed
Key: JBDS-2082
URL: https://issues.jboss.org/browse/JBDS-2082
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: maven
Affects Versions: 5.0.0.Beta2
Environment: Version: 5.0.0.Beta2
Build id: v20120328-1758-H123-Beta2
Build date: 20120328-1758
Reporter: Len DiMaggio
Assignee: Snjezana Peco
Fix For: 5.0.0.Beta3
When JBDS 5.0.beta2 is closed, this error is written to stdout:
12:25:54.899 [Worker-11] ERROR o.e.m.c.i.i.nexus.NexusIndexManager - Unable to update index for central|http://repo1.maven.org/maven2
org.apache.lucene.index.CorruptIndexException: Unknown format version: -9
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:225) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.lucene.index.DirectoryIndexReader$1.doBody(DirectoryIndexReader.java:95) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:653) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.lucene.index.DirectoryIndexReader.open(DirectoryIndexReader.java:115) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.lucene.index.IndexReader.open(IndexReader.java:316) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.lucene.index.IndexReader.open(IndexReader.java:227) ~[lucene-core-2.4.1.jar:2.4.1 750176 - 2009-03-04 21:56:52]
at org.apache.maven.index.updater.DefaultIndexUpdater.copyUpdatedDocuments(DefaultIndexUpdater.java:352) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexArchive(DefaultIndexUpdater.java:288) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:218) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:75) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:645) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:844) ~[indexer-core-3.1.0.jar:3.1.0]
at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:156) ~[indexer-core-3.1.0.jar:3.1.0]
at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1137) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na]
at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1081) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na]
at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager$1.run(NexusIndexManager.java:658) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na]
at org.eclipse.m2e.core.internal.index.nexus.IndexUpdaterJob.run(IndexUpdaterJob.java:71) [org.eclipse.m2e.core_1.0.200.20111228-1245.jar:na]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.101.v20120113-1953.jar:na]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JBIDE-11248) Invalid web.xml warning for welcome-file and error-page
by Cody Lerum (JIRA)
Cody Lerum created JBIDE-11248:
----------------------------------
Summary: Invalid web.xml warning for welcome-file and error-page
Key: JBIDE-11248
URL: https://issues.jboss.org/browse/JBIDE-11248
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M5
Environment: Nightly Build as of 3/8/2012
Reporter: Cody Lerum
web.xml shows warning "file name references to login.jsp that does not exist in web content"
for
{code}
<welcome-file-list>
<welcome-file>login.jsf</welcome-file>
</welcome-file-list>
{code}
and "location references to /error/403.jsp that does not exist in web content"
for
{code}
<error-page>
<error-code>403</error-code>
<location>/error/403.jsf</location>
</error-page>
{code}
This just changed in a recent nightly and the actual pages are .xhtml not jsp
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JBIDE-11990) When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
by Martin Malina (JIRA)
Martin Malina created JBIDE-11990:
-------------------------------------
Summary: When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
Key: JBIDE-11990
URL: https://issues.jboss.org/browse/JBIDE-11990
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: JBT 3.3 nightly 2012-05-24
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this is what happens:
1. The process keeps running on the remote host
2. The server is in Starting state until it reaches time out
3. This is where remote and local servers differ, but both behave wrongly
3.a - remote server: When time out is reached, server stops, but the process keeps running - you have to kill it manually
3.b - local server: When time out is reached, server tries to stop, but fails doing so. So you have to force stop and then it stops and the process is killed.
The the bigger problem is with remote servers - you have no way of stopping the server other than sshing to the server and killing the process.
In the case of local server, it is not so bad, but still after the time out the tools should be able to stop the server on first attempt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (JBIDE-12033) New Seam Project Wizard - when AS7 runtime is set, seam config is not set properly after changing to EAP5.1.2 runtime
by Martin Malina (JIRA)
Martin Malina created JBIDE-12033:
-------------------------------------
Summary: New Seam Project Wizard - when AS7 runtime is set, seam config is not set properly after changing to EAP5.1.2 runtime
Key: JBIDE-12033
URL: https://issues.jboss.org/browse/JBIDE-12033
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
Reporter: Martin Malina
Assignee: Alexey Kazakov
Fix For: 3.3.1
I guess this is not really so urgent, so targeting for 3.3.1.
While verifying JBIDE-11815, I noticed the following:
When you open the New Seam Project Wizard and select AS7/EAP6 runtime, both Dynamic web module and Configuration are set properly, to 3.0 and Dynamic Web Project with Seam 2.3, respectively.
But when you then change the runtime to EAP 5.1.2 the web module version is not changed (it stays empty) and the Configuration is set to <custom>. Even if set the web module to 2.5, Configuration is not set to Seam 2.2.
I would expect that after changing runtime to EAP 5.1, both web module version and configuration would be changed accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months