[JBoss JIRA] Created: (JBIDE-7565) Problems publishing and accessing parent pom + target platforms
by Nick Boldt (JIRA)
Problems publishing and accessing parent pom + target platforms
---------------------------------------------------------------
Key: JBIDE-7565
URL: https://jira.jboss.org/browse/JBIDE-7565
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.2.0.CR1
Thought I had this solved, but on further testing, I've found a problem.
This file is 404'd:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
However, the one I actually published is fine:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
So, when I try to retrieve the pom from the repo, I get this error:
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/resolver-status.properties
[DEBUG] Could not find metadata org.jboss.tools:org.jboss.tools.target.platform:0.0.1-SNAPSHOT/maven-metadata.xml in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/)
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repository.jboss.org/nexus/content/groups/public/
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o...
[DEBUG] Reading resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[DEBUG] Writing resolution tracking file /home/nboldt/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.1-SNAPSHOT/org.jboss.tools.target.platform-0.0.1-SNAPSHOT-unified.target.lastUpdated
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools:org.jboss.tools.target.platform:target:unified:0.0.1-SNAPSHOT
How can I force the resolution process to look at
https://repository.jboss.org/nexus/content/repositories/snapshots instead of http://repository.jboss.org/nexus/content/groups ?
Or, how can I force the missing/empty file to contain the correct versioning information so that maven can find the artifact?
I also tried to switch from
<uniqueVersion>true</uniqueVersion>
to
<uniqueVersion>false</uniqueVersion>
but the published artifacts still have the uniqueVersion suffixes.
----------
Steps to reproduce:
# remove your existing local .m2 cache
if [[ -d ~/.m2 ]]; then mv ~/.m2 ~/.m2___GOOD; fi
# check out build folder
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/
# check out tests folder
cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/tests/
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
Workaround:
However, if the parent pom is built locally, then the tests can be built too, w/o a problem (because the parent pom + target platform artifacts now exist locally in my ~/.m2 folder):
# build parent pom + target platform
cd /tmp/build; mvn3 clean install -f parent/pom.xml
# build tests
cd /tmp/tests; mvn3 clean install -X -e -fae -U -B
----------
Here's how I'm building + publishing the artifacts, fwiw:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-7551) Instance View: Table Sorting should have 3 states and indicate sorting with arrows
by Andre Dietisheim (JIRA)
Instance View: Table Sorting should have 3 states and indicate sorting with arrows
----------------------------------------------------------------------------------
Key: JBIDE-7551
URL: https://jira.jboss.org/browse/JBIDE-7551
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
How to reproduce:
1) make sure you have instance view opened and a few instances listed
2) click on a column
Result:
the column gets sorted, but there's no icon that shows the sort direction. Furthermore there are only 2 states: sorting ascending or descending
Expected result:
The column gets sorted and an icon shows what direction (ascending/descending) is activated. Furthermore you should be able to toggle between ascending/descending/not sorted by clicking consecutively on the same column
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-7924) Allow user to create a web service in custom source root
by Lukas Jungmann (JIRA)
Allow user to create a web service in custom source root
--------------------------------------------------------
Key: JBIDE-7924
URL: https://issues.jboss.org/browse/JBIDE-7924
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 3.2.0.Beta2
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-create or have a web project with two or more java source roots, say src (default) and src2 (custom)
-create some @WebService class in the src2 source root
-create a Bottom-up web service from the class created in previous step
=> generated classes are in src (default) java source root but I'd expect them in src2 (custom) source root since the class I used is there or I should have an option to choose where to put generated classes
for Top-down ws there's no way to say where to put generated stuff
If I choose to use Axis, I'm given an option to specify target source folder, if I use JBossWS I'm not given any option
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-4971) Deploying BIRT aaplication to JBoss AS 5.x
by Snjezana Peco (JIRA)
Deploying BIRT aaplication to JBoss AS 5.x
------------------------------------------
Key: JBIDE-4971
URL: https://jira.jboss.org/jira/browse/JBIDE-4971
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt, JBossAS
Affects Versions: 3.1.0.M3
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Steps to reproduce
- download testbirt.zip project from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples... (56MB)
- configure Seam 2.2.0 and a JBoss Runtime
- deploy to JBoss AS server
- call the "Test Birt" link
JBoss AS 4.2.3
- works correctly
JBoss AS 5.1.0 GA
- doesn't work due to the problem described on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898
JBoss EAP 5.0
You will often get warnings (eap5log1.txt)
When calling the "Test Birt" action, you will get either eap5log2.txt or eap5log3.txt.
The problem isn't always reproducible. Sometimes it doesn't happen, but rarely.
The problem happens due to the way in which JBoss AS 5 initializes the application. BIRT uses org.eclipse.birt.report.listener.ViewerServletContextListener to initialize the BIRT engine (OSGi) when starting the application. If this listener is commented/removed, the problem won't happen. If the BIRT engine hasn't been already initialized, it will be initialized when starting a BIRT servlet so that this listener isn't obliged. Maybe this is even better because the BIRT engine is initialized only when it is called. For now, we can use this as a workaround. However, it seems that there is a problem when the JBoss AS server initializes the application.
Another problem is that JBoss AS aggressively logs a warning about missing classes in BIRT internal jars (WEB-INF/platform/plugins/*.jar) when adding a new *xhtml file to the application. This can be solved by adding a line to <JBOSSAS_HOME/server/default/conf/bootstrap/profile.xml:
...
<bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes">
<constructor>
<parameter>
<set>
<value>.war</value>
</set>
</parameter>
<parameter>
<set>
<value>WEB-INF/classes</value>
<value>WEB-INF/lib</value>
<value>WEB-INF/platform</value> <!-- BIRT workaround -->
</set>
</parameter>
</constructor>
</bean>
...
The workaround isn't applicable to JBoss AS 5.1.0.GA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months